Add speaker guidelines

.eleventy.js

@@ -5,7 +5,7 @@ const pluginRss = require("@11ty/eleventy-plugin-rss");
 const isProd = process.env.ELEVENTY_ENV === "prod";
 const outDir = "public";
 
-module.exports = function (eleventyConfig) {
+module.exports = async function (eleventyConfig) {
 	// PLUGINS
 	eleventyConfig.addPlugin(pluginRss);
 
@@ -17,6 +17,10 @@ module.exports = function (eleventyConfig) {
 		return markdown.render(value);
 	});
 
+    // Get ID for h1 to h6 headings
+    const { IdAttributePlugin } = await import("@11ty/eleventy");
+    eleventyConfig.addPlugin(IdAttributePlugin);
+
 	eleventyConfig.addFilter("dateInfo", function (dateStr) {
 		// Get day of month
 		const dayOfMonth = parseInt(dateStr.split("-")[2]);

src/_layouts/page.njk

@@ -1,10 +1,48 @@
 ---
 layout: base.njk
 ---
+
 <style>
-  h1, h2, h3, h4 {
-    font-size: 1.25rem;
-    font-weight: bold;
+  .page-content ol,
+  .page-content ul,
+  .page-content ol li,
+  .page-content ul li {
+     margin-left: 1.125rem;
+   }
+
+  .page-content ol li { list-style: decimal; }
+  .page-content ul li { list-style: disc; }
+
+  /* Remove extra margin of nesting */
+  .page-content li > ol > li,
+  .page-content li > ul > li {
+     margin-left: 0;
+   }
+
+  .page-content h1, h2 {
+     margin-top: 1.5rem;
+  }
+
+  .page-content h3, h4 {
+     margin-top: 1.125rem;
+  }
+
+  /* Desktop: h1 starts at text-5xl (3rem) */
+  .page-content h1 { font-size: 3rem; }   /* text-5xl */
+  .page-content h2 { font-size: 2.25rem; }/* text-4xl */
+  .page-content h3 { font-size: 1.5rem; } /* text-2xl */
+  .page-content h4 { font-size: 1.25rem; }/* text-xl */
+
+  @media (max-width: 768px) {
+    /* Phones: h1 starts at text-3xl (1.875rem) */
+    .page-content h1 { font-size: 1.875rem; }/* text-3xl */
+    .page-content h2 { font-size: 1.5rem; }  /* text-2xl */
+    .page-content h3 { font-size: 1.25rem; } /* text-xl */
+    .page-content h4 { font-size: 1rem; }    /* text-base */
+  }
+
+  hr {
+    margin-bottom: 1.125rem;
   }
 </style>
 
@@ -46,7 +84,7 @@ layout: base.njk
 <div class="main-container pt-16 md:pt-48 bg-lavender w-full h-auto px-[6%]">
     <div class="pb-40 md:pb-60 lg:pb-[20%] w-full text-justify lg:w-[70%]">
         <div class="mt-24 md:-mt-32 lg:-mt-20 text-md lg:text-xl font-light">
-            <div class="font-light text-black text-lg">
+            <div class="font-light text-black text-lg page-content">
               {{ content | safe }}
             </div>
         </div>

src/attend/health-and-safety.md

@@ -12,15 +12,15 @@ COVID-19
 
 PyCon India is an international event, and we have attendees traveling from all around the globe. The world is still under the grasp on the COVID-19 pandemic, and from the lessons from the past conference around the globe, we know that conferences are a place where there is a high-change of communicating the disease. We love that people bring their unique perspectives -- but they also bring their local germs and Covid strains. We want PyCon India to be an event that everyone feels safe attending - therefore we are putting out this document for the attendees to follow during their time at PyCon India.
 
-## Vaccination
+### Vaccination
 
 We strongly recommend to take the latest vaccination boosters, and all attendees should be vaccinated. Please keep the your vaccine certificate handy incase asked for during the conference by the organizers. We also suggest you to monitor [WHO travel advice](https://www.who.int/emergencies/diseases/novel-coronavirus-2019/travel-advice) or the local COVID-19 travel advisory.
 
-## Masks during conference
+### Masks during conference
 
 We highly recommend you to wear mask during the conference. This would help you to stay safe while attending the talks, workshops, and Dev Sprint. It's also recommended to wear them at the venue. Masks must be worn over the nose and mouth and must be made of a tight-knit, non-permeable material. N95 or equivalent masks such as KN95 or K95 are recommended.
 
-## Rapid COVID-19 tests
+### Rapid COVID-19 tests
 
 We encourage PyCon India attendees to use at-home, antigen, or rapid tests before arriving and during the event. If you feel sick, exhibit COVID-19 symptoms, or test positive for COVID-19 before or during the conference, you should not attend the event.
 

src/program/speaker-guidelines.md

@@ -0,0 +1,163 @@
+---
+title: Speaker Guidelines
+description: |
+    Thank you for contributing to PyCon India 2025! Whether you're leading a panel, presenting a poster, or hosting an Open Space, your participation helps make the conference vibrant and community-driven. 
+    Please review the guidelines below based on your session type.
+layout: page.njk
+---
+
+## Talks and workshops
+
+Following are the guidelines each speaker must follow. These are there to ensure the event is neutral and more in the spirit of open source.
+
+1. Each slide must not have a logo or equivalent that represents a company/organization.  
+   *You may have a company logo where you introduce yourself, but speaker details should be more prominent.*
+2. No product or hiring pitches are to be done during the session.
+3. If any external images or resources are used, credits or links to the source must be mentioned on the slide or at the end.  
+4. If your session is about a commercial/non-open source product, a major part of your session must be about the technical implementation details of it.  
+   *This is to ensure that your session doesn’t become a product marketing session and that attendees benefit from your learning.*
+5. Your talk and slides must follow the [PyCon India Code of Conduct](https://in.pycon.org/2025/coc/policy/).
+
+*Note that some of these might not apply to the sponsored sessions.*
+
+### Tips
+Here are some of the best practices that would help you make your sessions better.
+
+1. Have an introduction slide where you talk about yourself.  
+   *This helps the attendees get to know you, why you are talking about the topic, and also helps them answer “Why should they listen to you?”.*
+2. Add interactive elements to your talk, this can be as simple as asking a show of hands or a quick quiz.
+3. Keep your demos recorded & make slides available offline.  
+   *This can save you at times when things just break, you don’t have Internet connection and so on.*
+4. Bring your own laptop along with **any adapters** required for presenting via an HDMI connection.
+5. Add slide numbers, this helps attendees to take notes during the session.
+6. A must-read: [Accessible Speaking Best Practices](https://www.deque.com/blog/accessible-speaking-best-practices/) this also has actionable steps.
+   1. Ensure the font size is large enough so that it is visible to the attendees from the back.
+   2. Consider using a light theme for slides, as the contrast and visibility of the light themes is more in general.
+   3. If you are showing code live, close all sidebars, extra tabs etc. to make it distraction free.
+
+---
+
+## Panel Discussions
+
+**Duration**: 30 minutes (including Q&A)
+**Format**: Group discussion with 3-4 panelists and a moderator
+
+### Responsibilities
+
+**Moderators**:
+
+* Coordinate with panelists in advance.  
+* Prepare a clear agenda and set of discussion questions.  
+* Ensure balanced participation and respectful dialogue.  
+* Facilitate audience Q&A.  
+* Consider setting the questions in a way to ensure the panel discussion caters to all levels of audience.  
+* Conclude the discussion with takeaways or highlights. 
+
+**Panelists**:
+
+* Keep remarks concise to allow time for others.  
+* Respect diverse viewpoints and foster inclusive discussion.
+
+### Tips
+
+* Focus on discussion, not presentations.
+* Encourage audience interaction—pose questions, use polls, or open the floor.
+* Avoid self-promotion; prioritize community insights and shared learning.
+
+---
+
+## Poster Presentations
+
+**Duration**: 1-2 hours (during dedicated poster session)  
+**Format**: Visual display + informal, one-on-one or small-group discussions
+
+### Guidelines
+
+* Design a clear, readable poster (recommended size: A0 or 36"x48").  
+* Include: title, names, affiliations, problem statement, approach, results, visuals, and contact info.  
+* Be present at your poster during the scheduled session to discuss your work.  
+* Provide a QR code linking to your code, paper, or project website (optional but encouraged).
+
+### Tips
+
+* Use visuals over text. Keep explanations simple and engaging.  
+* Prepare a 1-2 minute “elevator pitch” for passersby.
+
+---
+
+## Lightning Talks
+
+**Duration**: 5 minutes maximum (strictly enforced)  
+**Format**: Fast-paced, single-speaker presentation
+
+### Guidelines
+
+* Arrive 10 minutes early with your presentation on a USB drive or cloud link.  
+* Stick to the time limit—there will be no extensions.  
+* Use no more than 3–5 slides.
+
+### Tips
+
+* Focus on one idea: a project, tip, or call to action.  
+* Be energetic and engaging—lightning talks are crowd favorites!
+
+{% aside %}
+Note: Talks exceeding 5 minutes will be politely cut off.
+{% endaside %}
+
+---
+
+## Open Spaces
+
+**Duration**: 30–60 minutes (flexible)  
+**Format**: Self-organized, participant-driven discussion or activity
+
+### Guidelines (Facilitator/Host)
+
+* Define a clear purpose or goal for the session (e.g., “Brainstorming Python in Education”).  
+* Create a welcoming space for all attendees to participate.  
+* Manage time and wrap up with key takeaways (if applicable).
+
+### Tips
+
+* Have a round of introductions as it gives a chance to everyone to speak up and works as an ice-breaker.
+* As the room is shared, respect time limits and clean up afterward.  
+
+{% aside %}
+Remember: Open Spaces are community-powered. Come ready to share, listen, and collaborate.
+{% endaside %}
+
+---
+
+## Dev Sprint
+
+**Duration**: Full-day  
+**Format**: Collaborative coding and onboarding
+
+### Guidelines
+
+* Represent your open source project or community initiative.  
+* Prepare beginner-friendly issues (labeled “good first issue”).  
+* Provide clear setup instructions and documentation.  
+* Be approachable and welcoming to newcomers of all skill levels.
+
+{% aside %}
+Goal: Help others contribute meaningfully and grow your community.
+{% endaside %}
+
+---
+
+## General Guidelines for All Speakers & Hosts
+
+* **Code of Conduct**: All sessions must adhere to the [PyCon India Code of Conduct](https://in.pycon.org/2025/code-of-conduct).  
+* **Accessibility**: Use clear language and describe visuals.
+* **Recording & Consent**: Sessions may be recorded. Inform participants if you plan to record your Open Space or Dev Sprint activity.  
+* **Arrival Time**: Arrive at least 10–15 minutes before your session starts.  
+* **Contact**: Reach out to the help desk or volunteer coordinator for any support.
+
+---
+
+Thank you for sharing your knowledge and passion with the Python community!
+We can’t wait to learn from you at PyCon India 2025.
+
+For questions, email: cfp@in.pycon.org