djangocon
diff --git a/‎.github/workflows/deploy-to-ghpages.yml
Lines changed: 0 additions & 1 deletion b/‎.github/workflows/deploy-to-ghpages.yml
Lines changed: 0 additions & 1 deletion
diff --git a/‎.gitignore
Lines changed: 5 additions & 1 deletion b/‎.gitignore
Lines changed: 5 additions & 1 deletion
diff --git a/‎CNAME
Lines changed: 1 addition & 1 deletion b/‎CNAME
Lines changed: 1 addition & 1 deletion
diff --git a/‎CODE_OF_CONDUCT.md
Lines changed: 120 additions & 0 deletions b/‎CODE_OF_CONDUCT.md
Lines changed: 120 additions & 0 deletions
diff --git a/‎README.md
Lines changed: 44 additions & 3 deletions b/‎README.md
Lines changed: 44 additions & 3 deletions
diff --git a/‎ROBOTS.txt
Lines changed: 4 additions & 0 deletions b/‎ROBOTS.txt
Lines changed: 4 additions & 0 deletions
diff --git a/‎eleventy.config.js
Lines changed: 38 additions & 66 deletions b/‎eleventy.config.js
Lines changed: 38 additions & 66 deletions
@@ -4,7 +4,6 @@ on:
   push:
     branches:
       - main
-  pull_request:
 
 jobs:
   deploy:
 
@@ -130,4 +130,8 @@ dist
 .pnp.*
 
 # System fiels
-.DS_Store
+.DS_Store
+
+# python virtualenv
+.venv/
+__pycache__/
@@ -1 +1 @@
-durham.djangocon.us
+2024.djangocon.us
@@ -0,0 +1,120 @@
+# Code of Conduct
+
+DjangoCon US is dedicated to providing a fun harassment-free conference experience for everyone, regardless of gender, gender identity, sexual orientation, disability, physical appearance, body size, race, or religion.
+
+Be kind to others. Do not insult or put down other attendees. Behave professionally.
+
+Remember that harassment and sexist, racist, or exclusionary jokes are not appropriate for DjangoCon US.
+
+Attendees violating these rules may be asked to leave the conference without a refund at the sole discretion of the conference organizers.
+
+Thank you for helping make this a welcoming, friendly event for all.
+
+## Full Code of Conduct
+
+_To make clear what is expected, all delegates/attendees, speakers,
+exhibitors, organizers and volunteers at any DjangoCon US event are required
+to conform to the following Code of Conduct. Organizers will enforce this code
+throughout the event._
+
+### What the conference is
+
+DjangoCon US is a community conference intended for networking and
+collaboration in the developer community.
+
+We value the participation of each member of the Django community and want all
+attendees to have an enjoyable and fulfilling experience. Accordingly, all
+attendees are expected to show respect and courtesy to other attendees
+throughout the conference, at all conference events, and in all conference
+online spaces (such as Slack), whether officially sponsored by DjangoCon US or
+not.
+
+### Be Kind To Others
+
+Do not insult or put down other attendees. Behave professionally. Remember
+that harassment and sexist, racist, or exclusionary jokes are not appropriate
+for DjangoCon US. Attendees violating these rules may be asked to leave the
+conference without a refund at the sole discretion of the conference
+organizers.
+
+### Be Respectful
+
+Not all of us will agree all the time, but disagreement is no excuse for poor
+behavior and poor manners. We do not tolerate harassment of conference
+participants in any form.
+
+Harassment includes: offensive verbal comments related to gender, gender
+identity, sexual orientation, disability, physical appearance, body size,
+race, religion; sexual images in public spaces; deliberate intimidation,
+stalking, or following; harassing photography or recording; sustained
+disruption of talks or other events; inappropriate physical contact; and
+unwelcome sexual attention.
+
+## Choose Your Words
+
+Be careful in the words that you choose. Remember that sexist, racist, and
+other exclusionary jokes can be offensive to those around you. Excessive
+swearing and offensive jokes are not appropriate for DjangoCon US. We are all
+adults, capable of having adult conversations. Preface your presentation with
+appropriate Trigger/Content Warnings, if necessary.
+
+All communication should be appropriate for a professional audience including
+people of many different backgrounds. Sexual language and imagery is not
+appropriate for any conference venue, including talks.
+
+Participants asked to stop any harassing behavior are expected to comply
+immediately.
+
+Exhibitors in the expo hall, sponsor or vendor booths, or similar activities
+are also subject to the anti-harassment policy. In particular, exhibitors
+should not use sexualized images, activities, or other material. Booth staff
+(including volunteers) should not use sexualized clothing/uniforms/costumes,
+or otherwise create a sexualized environment.
+
+## Examples of Inappropriate Behavior
+
+- Harassment of any participants in any form
+- Deliberate intimidation, stalking, or following
+- Logging or taking screenshots of online activity for harassment purposes
+- Publishing others’ private information, such as a physical or electronic address, without explicit permission
+- Violent threats or language directed against another person
+- Incitement of violence or harassment towards any individual, including encouraging a person to commit suicide or to engage in self-harm
+- Creating additional online accounts in order to harass another person or circumvent a ban
+- Sexual language and imagery in online communities or in any conference venue, including talks
+- Insults, put downs, or jokes that are based upon stereotypes, that are exclusionary, or that hold others up for ridicule
+- Excessive swearing
+- Unwelcome sexual attention or advances
+- Unwelcome physical contact, including simulated physical contact (eg, textual descriptions like “hug” or “backrub”) without consent or after a request to stop
+- Pattern of inappropriate social contact, such as requesting/assuming inappropriate levels of intimacy with others
+- Sustained disruption of online community discussions, in-person presentations, or other in-person events
+- Continued one-on-one communication after requests to cease
+- Other conduct that is inappropriate for a professional audience including people of many different backgrounds
+
+This list is not an exhaustive list of all inappropriate behavior that is unacceptable at DjangoCon US. Community members asked to stop any inappropriate behavior are expected to comply immediately.
+
+## Photography
+
+In order to make DjangoCon US 2023 a great experience for everyone, do not
+photograph, video, or audio record anyone at DjangoCon without their express
+permission, sought in advance. If someone does not want to be photographed,
+video or audio recorded, please respect their wishes.
+
+Crowd shots are permitted, but when only the faces of a few people are
+visible, permission should be sought from all of those individuals.
+
+_If a participant engages in behavior that violates this code of conduct, the
+conference organizers may take any action they deem appropriate, including
+warning the offender or expulsion from the conference with no refund._
+
+## License
+
+This Code of Conduct was forked from the example policy from the [Geek
+Feminism wiki](http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Policy), created by the Ada Initiative and other volunteers, which
+is under a Creative Commons Zero license.
+
+This Code of Conduct also incorporates portions from PyCon's Code of Conduct, which is licensed under the [Creative Commons Attribution-ShareAlike 3.0 Unported License](https://creativecommons.org/licenses/by-sa/3.0/).
+
+Conference Code of Conduct by
+[2024.djangocon.us/conduct/](https://2024.djangocon.us/conduct/) is licensed under a
+[Creative Commons Attribution 3.0 Unported
+License](http://creativecommons.org/licenses/by/3.0/).
@@ -8,7 +8,7 @@ This project requires Node v20 or greater.
 
 ## Building & Development
 
-This project uses Liquid for templating. As such, you may wish to install syntax highlighting for Liquid in your text editor.
+This project uses Liquid for templating (except dates, see below). As such, you may wish to install syntax highlighting for Liquid in your text editor.
 
 * VS Code: [Liquid Language Support](https://marketplace.visualstudio.com/items?itemName=neilding.language-liquid)
 * [Liquid documentation](https://liquidjs.com/)
@@ -19,6 +19,47 @@ Build and watch for local changes by running:
 
 This opens a local server at `http://localhost:8080/` and watches for changes to the source files.
 
-# To Dos
+## Conference Phases
 
-1. Replace autoprefixer and cssnano with lightningcss
+The conference can be in 3 separate phases, controlled under `site.json`:
+
+* `landing`: The conference site consists of a landing page.
+* `active`: The conference site is live and registration may occur.
+* `archived`: The conference is over.
+
+This impacts the rendering of the homepage and display of content in various locations.
+
+Reference:
+
+* `src/index.html`
+* `src/_includes/home/`
+
+## Date Formatting
+
+Dates are formatted with [date-fns](https://date-fns.org/), due to some wonkiness with Eleventy's date formatting. You can use the `formatDateTime` shortcode in your templates to format dates. Note, that this will take into consideration the timezone defined in `site.json`, under `timezone`. Example:
+
+```liquid
+{{ post.data.published_datetime | formatDateTime: "MMMM d, yyyy" }}
+```
+
+## Social Media Images
+
+1. Presenter images are created at `/presenters/{{ slug }}/`
+2. Session images are created at `/{{ talks,tutorials }}/{{ slug }}/social/`
+
+## Considerations when updating content
+
+1. When adding images, if they are below the "fold", consider adding a `loading="lazy"` attribute to the image tag.
+2. When adding images, consider adding an `alt` attribute to the image tag.
+3. Keep copy short and to the point. The site is most likely scanned, not read.
+4. Make sure to keep the styleguide up-to-date with any new components or styles.
+
+## Styleguide
+
+The styleguide lives at `/styleguide/` (respectively `styleguide.html`). The guide is built from content within `src/_content/styleguide/`. Each HTML page represents a section. Sections can be ordered with `order`. Each section can have a `description`.
+
+When using code samples, be sure to use `{% capture code %}` to capture sample and pass it to the `code-snippet.html` include like so:
+
+```liquid
+{% include "code-snippet.html", code:code, lang:'html' %}
+```
@@ -0,0 +1,4 @@
+Sitemap: /sitemap.xml
+
+User-agent: *
+Disallow:
@@ -1,62 +1,22 @@
 const path = require('path');
 
 const Image = require('@11ty/eleventy-img');
-const markdownIt = require("markdown-it");
 
-module.exports = (config) => {
-  /*
-    Setup collections
-    https://www.11ty.dev/docs/collections/
-  */
-  config.addCollection("posts", function(collectionApi) {
-    return collectionApi.getFilteredByGlob("src/_content/posts/*.md");
-  });
-
-  config.addCollection("places", function(collectionApi) {
-    return collectionApi.getFilteredByGlob("src/_content/places/*.md");
-  });
+const setupCollections = require('./lib/collections');
+const setupSessions = require('./lib/sessions');
+const setupFeed = require('./lib/feed');
+const markdown = require('./lib/markdown');
 
-  config.addCollection("presenters", function(collectionApi) {
-    return collectionApi.getFilteredByGlob("src/_content/presenters/*.md");
-  });
+const { formatInTimeZone } = require('date-fns-tz');
 
-  config.addCollection("organizers", function(collectionApi) {
-    return collectionApi.getFilteredByGlob("src/_content/organizers/*.md").filter(item => !item.data.hidden);
-  });
+// Read timezone from site.json
+const siteConfig = require('./src/_data/site.json');
+const timezone = siteConfig.timezone || 'UTC'; // Default to 'UTC' if not specified
 
-  config.addCollection("sponsorsByLevel", function(collectionApi) {
-    const sponsors = collectionApi.getFilteredByGlob("src/_content/sponsors/*.md");
-    const visibleSponsors = sponsors.filter(sponsor => !sponsor.data.hidden);
-    const levelOrder = [
-      "Diamond",
-      "Platnum",
-      "Gold",
-      "Silver",
-      "Bronze",
-      "Coffee",
-      "Opportunity Grant",
-      "Community",
-    ];
-
-    const sponsorsByLevel = visibleSponsors.reduce((acc, sponsor) => {
-      const level = sponsor.data.level;
-      if (!acc[level]) {
-        acc[level] = [];
-      }
-      acc[level].push(sponsor);
-      return acc;
-    }, {});
-
-    // Sort levels based on predefined order
-    const sortedSponsorsByLevel = {};
-    levelOrder.forEach(level => {
-      if (sponsorsByLevel[level]) {
-        sortedSponsorsByLevel[level] = sponsorsByLevel[level];
-      }
-    });
-
-    return sortedSponsorsByLevel;
-  });
+module.exports = (config) => {
+  setupCollections(config);
+  setupSessions(config);
+  setupFeed(config);
 
   /*
     Setup passthrough file copy
@@ -66,10 +26,12 @@ module.exports = (config) => {
   config.addPassthroughCopy("src/assets/js/");
   config.addPassthroughCopy("src/assets/favicons/");
   config.addPassthroughCopy({
-    "src/_content/sponsors/*.{png,jpg,jpeg,svg}": "sponsors/",
-    "src/_content/places/*.{png,jpg,jpeg,webp}": "venue/",
+    "src/_content/sponsors/*.{png,jpg,jpeg,webp,svg}": "sponsors/",
+    "src/_content/places/*.{png,jpg,jpeg,webp,svg}": "venue/",
   });
   config.addPassthroughCopy("CNAME");
+  config.addPassthroughCopy("ROBOTS.txt");
+
 
   /*
     Setup watch targets
@@ -80,18 +42,16 @@ module.exports = (config) => {
   /*
     Shortcodes
   */
-  config.addLiquidShortcode("year", () => `${new Date().getFullYear()}`);
-
   // TODO: Accept widths or support different widths
   config.addLiquidShortcode("image", async function(
     src,
     outputDir,
     urlPath,
-    alt,
+    alt = "",
     sizes,
     classes = "") {
       let metadata = await Image(src, {
-        widths: [300, 600],
+        widths: [180, 300, 600],
         formats: ["webp"],
         outputDir,
         urlPath,
@@ -114,19 +74,30 @@ module.exports = (config) => {
     return Image.generateHTML(metadata, imageAttributes);
   });
 
+  config.addPairedShortcode("markdown", function(content = "") {
+    return markdown.render(content);
+  });
+
   /*
     Filters
   */
   config.addFilter("markdown", function(content = "") {
-    let markdown = markdownIt({
-      html: true,
-      breaks: true,
-      linkify: true
-    });
-
     return markdown.render(content);
   });
 
+  config.addFilter("formatDateTime", function(date, format) {
+    return formatInTimeZone(date, timezone, format);
+  });
+
+  config.addFilter("find", function find(collection = [], slug = "") {
+    return collection.find(item => item.fileSlug === slug);
+  });
+
+  /* TODO: Make generic */
+  config.addFilter("talksByPresenter", function talksByPresenter(collection = [], slug = "") {
+    return collection.filter(item => item.data.presenter_slugs.includes(slug));
+  });
+
   /*
     Misc configuration
   */
@@ -135,6 +106,8 @@ module.exports = (config) => {
     excerpt_separator: "<!-- excerpt -->"
   });
 
+  config.setLibrary("md", markdown);
+
   return {
     dir: {
       input: "src",
@@ -144,7 +117,6 @@ module.exports = (config) => {
 
     // Use Liquid for templating
     // https://www.11ty.dev/docs/languages/liquid/
-    htmlTemplateEngine: "liquid",
-    markdownTemplateEngine: "liquid"
+    htmlTemplateEngine: "liquid"
   }
 };
Original file line number	Diff line number	Diff line change
`@@ -1 +1 @@`
`1`		`-durham.djangocon.us`
	`1`	`+2024.djangocon.us`