The official website for ATProto Science - fostering an ecosystem for science on ATProto.
npm installnpx eleventy --serveThe site will be available at http://localhost:8080
npx eleventyThis site uses Eleventy with the GOV.UK Eleventy Plugin for styling.
The site automatically generates collection pages for:
- Events -
content/events/event-*.md - Projects -
content/projects/project-*.md - News -
content/news/news-*.md
Events are automatically collected and displayed on the /events page. To create a new event:
File naming convention: event-{shortname}.md
Example: content/events/event-atmosphere2026.md
---
layout: sub-navigation
title: 2026 March - ATmosphereConf 2026
description: Your event description for meta tags and listings
date: 2026-03-26
image:
src: /events/images/event-atmosphere2026.jpg
alt: Event image description
opengraphImage: true
author:
- name: ATproto.science
url: '/'
tags:
- ATproto
eleventyComputed:
aside:
title: Get Ticket
content: |
[Get Ticket](https://example.com/tickets)
---Write your event content in Markdown below the frontmatter:
## Key Info
> [!IMPORTANT]
> 10am, March 26th–6pm, March 29th, 2026
> [Venue Name, Address](https://maps.app.goo.gl/example)
Event description and details here...
## Speakers
List speakers or use placeholder:
> [!IMPORTANT]
> Coming Soon
## Schedule
Add schedule or use placeholder:
> [!IMPORTANT]
> Coming Soon
## FAQ
<details>
<summary>Question here?</summary>
Answer here.
</details>Store event-specific images in content/events/images/
Example: content/events/images/event-atmosphere2026.jpg
Events are automatically sorted by date (most recent first) on the events index page.
- Use the
datefield for proper sorting - Keep filenames short and descriptive
- Use
event-prefix for automatic collection - Store images in
content/events/images/for organization - Use collapsible
<details>sections for FAQs
Coming soon...
Coming soon...
Custom styles are defined in content/assets/styles.scss and compiled automatically by Eleventy.
The site uses GOV.UK Design System with custom brand colors:
- Brand color:
#8822aa - Link color:
#660088 - Link hover:
#440066
The site generates static files in the _site directory which can be deployed to any static hosting service.
The site can be deployed in two different scenarios, controlled by the pathPrefix setting in eleventy.config.js:
Serving on a Root Domain (e.g., https://atproto.science)
When deploying to a root domain, use:
const pathPrefix = '/' // For production on atproto.scienceThis is the current configuration. All assets and links will be served from the root of the domain.
Serving on a Path (e.g., https://atproto-science.github.io/at-science-homepage/)
When deploying to GitHub Pages or any other service where the site is served from a subdirectory, uncomment and use:
const pathPrefix = '/at-science-homepage/' // For GitHub Pages deploymentReplace /at-science-homepage/ with your specific path. This ensures all assets and internal links include the correct path prefix.
Note: Local development always uses / regardless of the production configuration.
For questions or contributions, reach out at [email protected]