add speaker guidelines page.

devcon/CLAUDE.md

@@ -60,7 +60,11 @@ Recoil for global state (`src/state/main.ts`). React Context for Web3Modal/AppKi
 
 ### Internationalization
 
-Locales: `default`, `en`, `es`. Middleware handles i18n routing.
+Locales: `default`, `en`, `hi`, `mr` (next.config.js). Middleware handles i18n routing.
+
+- Intl strings live in `content/<locale>/intl/*.json`, imported and registered per-namespace in `src/utils/intl.ts`. `getMessages(locale)` deep-merges the locale bundle **on top of `en`**, so missing hi/mr files or keys automatically fall back to English.
+- **Only author content in `content/en/`.** Never hand-create or hand-edit `hi`/`mr` files: a GitHub Action (`.github/workflows/devcon-translate.yml`, root repo) runs on every push to `main` touching `devcon/content/en/**` and machine-translates changed files to Hindi and Marathi via `pnpm translate-content`, committing the results. Hand-made hi/mr files get overwritten by it, and until then they *override* the en fallback (risking stale copy).
+- `content/.manifest.json` tracks source-file hashes so only changed en files are re-translated; don't edit it manually.
 
 ## Code Style
 

devcon/content/en/intl/application_guidelines.json

@@ -0,0 +1,47 @@
+{
+  "hero_title": "Application guidelines",
+  "page_title": "Speaker Application Guidelines",
+  "page_description": "Everything speakers need to know to apply for Devcon 8 India — code of conduct, session lengths, programming values, the review process, and how decisions are made.",
+  "heading": "Devcon 8 India:\nSpeaker application guidelines",
+  "apply_cta": "Apply to speak",
+  "contact_heading": "Got a question or concern?",
+  "contact_prefix": "Reach out to ",
+  "contact_email": "speak@devcon.org",
+  "sections": {
+    "important_information": {
+      "nav": "Important information",
+      "title": "Important information",
+      "body": "- This year we'll be accepting fewer talks compared to Devcon 7. That said, there are more ways to participate, including discussion corners and [Community Hubs](https://forum.devcon.org/t/rfp-13-devcon-8-india-community-hubs/8657).\n- Submit your proposal only once, no need to duplicate it among all tracks/format. You can add more context in the Notes section of your proposal.\n- Each application will be reviewed by a committee of experts. Their decision is final. There is no appeal process.\n- The review committee may suggest converting your session to a different format (for example, a Talk to a Lightning Talk or vice versa) if it better fits the program. We will always reach out before making any changes.\n- All speakers and panelists listed in your proposal must be confirmed at the time of submission. Do not include tentative or unconfirmed participants.\n- All accepted speakers will receive a free ticket to attend Devcon. If you already purchased a ticket by the time you receive your confirmation, [contact us](mailto:support@devcon.org) to arrange a refund.\n- Review the [Talks Wishlists](https://ef-events.notion.site/devcon-8-talks-wishlist) for ideas of topics per track."
+    },
+    "code_of_conduct": {
+      "nav": "Speakers code of conduct",
+      "title": "Speakers code of conduct, tldr;",
+      "body": "Please read the general [code of conduct](https://devcon.org/en/code-of-conduct/) and especially the \"Topics to Avoid\" aka:\n\n- **Promotional or purely \"commercial\" talks will not be accepted. All talks must be educational.** Devcon is not a place to shill your solution, it is about sharing knowledge."
+    },
+    "session_lengths": {
+      "nav": "Session lengths",
+      "title": "Session lengths",
+      "body": "**Session lengths depend on the type of session:**\n\n- Lightning Talks (5 minutes + 2 minutes for Q&A)\n- Talks (20 minutes + 5 minutes for Q&A)\n- Mixed Formats (25 minutes)\n- Workshops (60 minutes)\n\n**Note:** The organizers may suggest adjustments to your session length based on content and program needs."
+    },
+    "programming_values": {
+      "nav": "Programming values",
+      "title": "Devcon programming values",
+      "body": "Devcon takes a holistic approach and aims to engage all attendees.\n\nThose who want to learn will find the type of content best-suited to them whether it be talks, workshops or free-form discussions. Below are some values that guide Devcon's programming:\n\n1. **Collaboration and coordination** — Cross pollination and alignment on ideas and (remote) people\n2. **Education and inspiration** — Provide educational & inspirational content, including newcomers\n3. **Get inspired by and inspire adjacent communities** — Learn from FOSS best practices, inspire others to follow our standards\n4. **Challenge our understanding of Ethereum as it is** — Bring novel perspectives & approaches, update on state-of-the-art research"
+    },
+    "review_process": {
+      "nav": "Review process",
+      "title": "Review process",
+      "body": "- Each track has its own reviewing committee, consisting of a track lead and a diverse set of reviewers.\n- Each application will be reviewed by multiple members of the review team (2 minimum).\n- Talks will be selected on aggregate scores from the review criteria."
+    },
+    "review_criteria": {
+      "nav": "Review criteria",
+      "title": "Review criteria",
+      "body": "When assessing submissions, Reviewers will keep the **Devcon Programming Values** in mind, and consider the following review criteria:\n\n- **Is the submission information accurate and in the right track?** Is the submission in the right track, with the correct tags?\n- **Is the submission focused on sharing knowledge?** All submissions must have the intended purpose of sharing knowledge (experience, learnings, development, research, or a specific problem they are hoping to solve.) **Note:** Reviewers will not accept an application that is devoted to promoting a company or project. If applicants would like to shill a project this is not the place.\n- **Is the submission innovative and/or novel?** All talks and submissions should be geared to present new ideas to drive the ecosystem forward, not repeat presentations that have been given several times before.\n- **Is the submission constructive?** Does the submission aim to solve a problem or contribute to the ecosystem in some way? Is it providing insight or solutions to a challenge faced by many?\n- **Is the speaker qualified?** Does the speaker have sufficient knowledge and experience to present on this topic?\n- **Is the speaker relevant to the session?**"
+    },
+    "decision": {
+      "nav": "Decision",
+      "title": "Decision",
+      "body": "**The speaker application process is very competitive** and unfortunately, this may mean that quality talks are not selected due to time and space constraints.\n\n- By the end of August, first decisions will be made. **Expect all decisions to be final by the end of September.**\n- You will be notified of the status of your application once all applications have been carefully reviewed by our committee of experts.\n- Reviewers' decisions are final, and there is no appeal process, but there are lots of ways to [contribute to Devcon](/about#get-involved) if your application is not accepted.\n- All accepted speakers will receive a free ticket to attend Devcon. If you already purchased a ticket by the time you receive your confirmation, [contact us](mailto:support@devcon.org) to arrange a refund."
+    }
+  }
+}