new release

.env.example

@@ -0,0 +1 @@
+PUBLIC_GA_ID=

.github/workflows/ci.yml

@@ -2,7 +2,7 @@ name: CI
 
 on:
   pull_request:
-    branches: [main]
+    branches: [main, develop]
 
 jobs:
   build:

.github/workflows/deploy.yml

@@ -2,7 +2,7 @@ name: Deploy to GitHub Pages
 
 on:
   push:
-    branches: [ main ]
+    branches: [main]
   workflow_dispatch:
 
 permissions:
@@ -11,7 +11,7 @@ permissions:
   id-token: write
 
 concurrency:
-  group: "pages"
+  group: 'pages'
   cancel-in-progress: false
 
 jobs:
@@ -20,18 +20,18 @@ jobs:
     steps:
       - name: Checkout
         uses: actions/checkout@v4
-      
+
       - name: Setup Node
         uses: actions/setup-node@v4
         with:
           node-version-file: '.nvmrc'
-      
+
       - name: Install dependencies
         run: npm install
-      
+
       - name: Build with Astro
         run: npm run build
-      
+
       - name: Upload artifact
         if: github.event_name != 'pull_request'
         uses: actions/upload-pages-artifact@v3

.gitignore

@@ -13,4 +13,6 @@ dist/
 .DS_Store
 
 # vscode settings
-.vscode/
+.vscode/
+
+*.local

AGENTS.md

@@ -0,0 +1,191 @@
+# AGENTS.md
+
+This document provides a detailed guide for agents interacting with this codebase, which is built on the Astro framework. Follow these standards to ensure consistency and maintainability. For further details on Astro, refer to the [official documentation](https://docs.astro.build/).
+
+---
+
+## 1. Build, Lint, and Test Commands
+
+### Build Commands
+
+- **Development Server**:
+
+  ```bash
+  pnpm dev
+  ```
+
+  Use this command to spin up a development server. It includes live-reloading.
+
+- **Build for Production**:
+
+  ```bash
+  pnpm build
+  ```
+
+  This compiles the codebase into optimized production-ready files under the `dist/` directory.
+
+- **Preview Production Build**:
+  ```bash
+  pnpm preview
+  ```
+  This command serves the production build locally for testing.
+
+### Linting and Formatting
+
+- **Run Prettier**:
+  ```bash
+  pnpm format
+  ```
+  This formats all code under the `src` folder according to the Prettier settings.
+
+### Testing Commands
+
+(Note: No testing framework is currently integrated. Update this section if added.)
+
+To simulate the test command:
+
+```bash
+pnpm test
+```
+
+Currently, this outputs `Error: no test specified`.
+
+For individual test setups, the framework used (e.g. Jest, Vitest) will define the process.
+
+---
+
+## 2. Code Style Guidelines
+
+### General Formatting Rules
+
+This codebase uses **Prettier** for consistent formatting. Key settings include:
+
+- **Tab Width**: 2 spaces
+- **Line Width**: 110 characters max
+- **Semicolons**: Disabled
+- **Quotes**: Single quotes preferred (`'example'`, not `"example"`)
+- **Plugins**: Uses `prettier-plugin-astro` for `.astro` files.
+
+Run the formatter before committing code:
+
+```bash
+pnpm format
+```
+
+### Import Conventions
+
+1. Place **external imports** above internal ones:
+
+```typescript
+import { useState } from 'react'
+import utils from '@/lib/utils'
+```
+
+2. **Do not use wildcard imports** (e.g., `import * as fs`).
+3. Maintain alphabetical order where possible.
+
+### Code Organization
+
+1. Use TypeScript for all new files (`.ts`, `.tsx`).
+2. Follow the directory structure:
+   - Components in `src/components`
+   - Pages in `src/pages`
+   - Utilities in `src/lib`
+
+### Naming Conventions
+
+#### Files/Folders
+
+- Use `kebab-case` for filenames (`example-file.ts`).
+- Directories reflect their contents (`components`, `utils`).
+
+#### Variables and Functions
+
+Use `camelCase` for variables and methods:
+
+```javascript
+const fetchData = () => {}
+```
+
+#### Types
+
+- Interface names should use `PascalCase`:
+
+```typescript
+interface User {
+  id: string
+  name: string
+}
+```
+
+### Error Handling
+
+1. Always check for edge cases in asynchronous operations:
+
+```typescript
+try {
+  const response = await fetch('/api/data')
+  const data = response.json()
+} catch (error) {
+  console.error('Error fetching data:', error)
+}
+```
+
+2. Avoid silent failures. Log or handle errors appropriately.
+
+---
+
+## 3. Guidelines for Agents
+
+Agents (like Copilot) must adhere to these coding standards to ensure consistency.
+
+1. **Pre-Execution**
+   - Ensure Prettier is configured. Adjust any settings, such as overriding `tabWidth` or `printWidth`, to align with this repository.
+   - Validate TypeScript definitions before proceeding.
+
+2. **During Execution**
+   - When generating test files, suggest using Jest or Vitest (if no tests are found).
+   - For updates, refactor to use modular imports and maintain concise separation of logic.
+   - **Follow SEO and i18n guidelines** defined in section 4 when creating or modifying pages.
+
+3. **Post-Execution**
+   - Always include a test or linting step before suggesting commits.
+   - Suggest meaningful commit messages, such as:
+     ```bash
+     chore: format code with Prettier
+     ```
+
+---
+
+## 4. SEO and Page Creation Guidelines
+
+Agents must ensure all new pages are optimized for search engines and follow the project's internationalization (i18n) structure.
+
+### Multi-language Pages
+- All new pages must be placed in `src/pages/[lang]/`.
+- Use `getStaticPaths()` to support all configured locales (`es`, `en`, `ca`).
+- Example structure:
+  ```typescript
+  export function getStaticPaths() {
+    return [{ params: { lang: 'es' } }, { params: { lang: 'en' } }, { params: { lang: 'ca' } }]
+  }
+  ```
+
+### Layout and Metadata
+- Every page **must** use the `Layout` component from `src/layouts/Layout.astro`.
+- Pass a unique and descriptive `title` and `description` (150-160 characters) to the `Layout` component.
+- The `Layout` component automatically handles canonical URLs, social media tags (OG/Twitter), and `hreflang` tags.
+
+### Semantic HTML and Accessibility
+- **H1 Tags**: Use exactly one `<h1>` per page.
+- **Headings**: Maintain a logical hierarchy (`h2`, `h3`, etc.).
+- **Images**: All `<img>` tags must include a descriptive `alt` attribute.
+- **Links**: Use descriptive text for links. Avoid generic phrases like "click here".
+
+### Analytics and Monitoring
+- Use the `PUBLIC_GA_ID` environment variable for Google Analytics.
+- Do not hardcode tracking IDs.
+
+---
+
+Adhering to these standards will ensure contributions are cohesive, minimizing review cycles and enhancing overall productivity.

README.md

@@ -33,3 +33,40 @@ pnpm build
 pnpm preview
 ```
 
+## SEO & New Pages
+
+To maintain good SEO and consistency as the project grows, follow these guidelines when adding new pages:
+
+### 1. Creating Multi-language Pages
+New pages should be created in `src/pages/[lang]/` using `getStaticPaths`.
+- Ensure you use the `<Layout>` component.
+- Always provide a unique `title` and `description` to the Layout.
+
+Example:
+```astro
+---
+import Layout from '../../layouts/Layout.astro'
+// ...
+---
+<Layout title="Your Page Title" description="Concise description (150-160 chars)">
+  <!-- Content -->
+</Layout>
+```
+
+### 2. SEO Best Practices
+- **Semantic HTML**: Use only one `<h1>` per page. Follow a logical heading hierarchy (`<h2>`, `<h3>`).
+- **Image Alt Tags**: All `<img>` tags MUST have descriptive `alt` attributes.
+- **Internal Linking**: Use descriptive link text (avoid "click here").
+
+### 3. Analytics
+- Set the `PUBLIC_GA_ID` environment variable in your `.env` file to enable Google Analytics.
+  ```text
+  PUBLIC_GA_ID=G-XXXXXXXXXX
+  ```
+
+### 4. Structured Data
+- The main event structured data (JSON-LD) is globally included in `Layout.astro`.
+- For specific pages (like "Sponsors" or "Talks"), consider adding additional [schema.org](https://schema.org) types locally if necessary.
+
+### 5. Sitemap
+- The sitemap is automatically generated on every build. No manual action is required.

astro.config.mjs

@@ -1,9 +1,11 @@
 import { defineConfig } from 'astro/config'
 import tailwindcss from '@tailwindcss/vite'
+import sitemap from '@astrojs/sitemap'
 
 export default defineConfig({
   site: 'https://2026.es.pycon.org',
   base: '/',
+  integrations: [sitemap()],
   vite: {
     plugins: [tailwindcss()],
   },
@@ -12,7 +14,7 @@ export default defineConfig({
     locales: ['es', 'en', 'ca'],
     routing: {
       prefixDefaultLocale: true,
-      redirectToDefaultLocale: false
+      redirectToDefaultLocale: false,
     },
   },
 })

package.json

@@ -15,6 +15,7 @@
   "license": "ISC",
   "packageManager": "pnpm@10.10.0",
   "dependencies": {
+    "@astrojs/sitemap": "^3.7.1",
     "@fontsource-variable/jetbrains-mono": "^5.2.8",
     "@fontsource-variable/outfit": "^5.2.8",
     "@tailwindcss/vite": "^4.1.18",