Skip to content

Commit 9e07fa4

Browse files
Initial pass at content
1 parent 0cbb403 commit 9e07fa4

File tree

3 files changed

+100
-49
lines changed

3 files changed

+100
-49
lines changed

sites/main-site/src/content/events/2026/hackathon-march-2026/index.mdx

Lines changed: 48 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ endTime: "17:00+02:00"
99
start: 2026-03-11T00:00:00+00:00
1010
end: 2026-03-13T00:00:00+00:00
1111
locations:
12-
- name: Online
12+
- name: In person and online
1313
importTypeform: true
1414
hackathonProjectListModals: hackathon-march-2026
1515
markdownPlugin: checklist
@@ -24,19 +24,63 @@ import LocalDateTime from "@components/event/LocalDateTime.svelte";
2424

2525
# Welcome
2626

27-
Join us online **March 11-13, 2026**, for the nf-core hackathon! 🗓️
27+
Join us in person or online **March 11-13, 2026**, for the nf-core hackathon! 🗓️
2828

2929
:::info{title="Key dates"}
3030

31-
- **November 2025**: Project proposals open
32-
- **February 1st 2026**: Registration opens
31+
- **February 2nd 2025**: Project proposals open
32+
- **February 9th 2026**: Registration opens
3333
- **March 11th - 13th 2026**: Hackathon
3434

3535
:::
3636

3737
To get a feel for how the event will work, check out the similar style hackathons
3838
that we held in [2024](/events/2024/hackathon-march-2024) and [2025](/events/2025/hackathon-march-2025).
3939

40+
## Hybrid format: In-person hubs and online participation
41+
42+
This hackathon will follow a **hybrid format** with in-person local hubs and online participation.
43+
Based on feedback from previous events, we're making some changes to improve the experience for everyone:
44+
45+
:::warning{title="Important: Choosing your project"}
46+
47+
Collaboration across different sites and time zones can be challenging, and we want to make sure everyone has a great experience.
48+
To ensure the best experience, we're making recommendations to **limit split projects** across multiple locations.
49+
50+
**When choosing a project:**
51+
52+
- Each project will have a primary location (a specific hub or "online")
53+
- Project leaders will be present and attentive at their specified location throughout the hackathon, in person or online
54+
- If you attend a specific hub, we strongly recommend choosing a project based at the site you'll be attending
55+
56+
If you're attending online, we suggest you join projects marked as "online" or consider projects at hubs in your time zone.
57+
58+
:::
59+
60+
### Strengthening online presence
61+
62+
We're aiming to improve the online experience:
63+
64+
- More core team members, maintainers, and other community leaders will provide online coverage throughout the event
65+
- Continued attention and presence to ensure it doesn't feel empty when people join
66+
- Improved online platform and communication tools (more details coming soon)
67+
68+
### In-person local hubs
69+
70+
We encourage ambassadors and community members to organize in-person local hubs.
71+
Seqera will support local hubs with sponsorship as in previous years.
72+
These hubs are invaluable for community building and collaborative work.
73+
74+
:::tip{title="Tips for cross-site collaboration"}
75+
76+
If you still want to collaborate across sites, here are some recommendations:
77+
78+
- Spanning time zones makes it easier (e.g., projects with morning/evening overlap)
79+
- Booking a dedicated room at your local site might be needed for video calls
80+
- Having more than one person doing the same project at your site is highly recommended
81+
82+
:::
83+
4084
:::tip{.fa-globe title="Time zones"}
4185

4286
The hackathon runs from March 11-13, wherever you are.
@@ -86,13 +130,6 @@ You need to add a new markdown file to the
86130

87131
See existing files for examples, if you're unsure about anything please ask in Slack or in the pull-request.
88132

89-
## Join a project
90-
91-
Joining a project is as simple as turning up and getting in touch with the group.
92-
If you don't know where to find them, ping the project lead on slack.
93-
94-
You can move freely between projects throughout the event.
95-
96133
## List of projects
97134

98135
<HackathonModalProjectList eventPath="hackathon-march-2026" />
Lines changed: 52 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,52 @@
1+
---
2+
title: Docs V2
3+
category: community
4+
slack: https://nfcore.slack.com/archives/C06RR8F5L3E
5+
# intro_video: ""
6+
image: "/assets/images/events/2026/hackathon-march/development-guides.jpg"
7+
image_alt: Documentation, documentation everywhere
8+
leaders:
9+
christopher-hakkaart:
10+
name: Chris Hakkaart
11+
slack: https://nfcore.slack.com/team/U024MM1DRKL
12+
---
13+
14+
Contribute to the final push for releasing V2 of the nf-core documentation with quality control, link fixes, and content refinement.
15+
16+
## Goal
17+
18+
Work towards completing the final quality control phase of the nf-core documentation v2 release, fixing links, filling content gaps, and helping the documentation meet our new standards.
19+
20+
:::note{title="Sneak peak"}
21+
Check out the [docs-v2 deploy preview](https://nf-core-docs-v2.netlify.app/).
22+
:::
23+
24+
## Description
25+
26+
James and Chris have almost completed the migration of existing documentation into the new styled documentation set.
27+
Content has been migrated with the newly developed style guide applied and restructured to make finding information more intuitive.
28+
29+
This project focuses on the critical quality control phase:
30+
31+
- Fixing broken or outdated links throughout the documentation
32+
- Identifying and filling content gaps discovered during migration
33+
- Reviewing migrated content for clarity and consistency
34+
- Validating that the new structure works effectively
35+
- Polishing documentation to meet the new quality standards
36+
- Creating new content where opportunities are identified
37+
38+
With the rapid initial migration complete, we need careful review and refinement to help make the v2 documentation launch as successful as possible and improve the user experience.
39+
40+
:::note{title="Great first issues"}
41+
This project is suitable for newcomers to nf-core and open source contributions. We expect to have many "great first issues" available to help you get started.
42+
:::
43+
44+
## Tasks
45+
46+
- Review sections for broken links and fix them
47+
- Identify and document content gaps
48+
- Review migrated content for quality and consistency
49+
- Test navigation and documentation structure
50+
- Create new content to fill identified gaps
51+
- Validate examples and code snippets
52+
- Ensure style guide compliance across pages

sites/main-site/src/content/hackathon-projects/hackathon-march-2026/new-development-guide.mdx

Lines changed: 0 additions & 38 deletions
This file was deleted.

0 commit comments

Comments
 (0)