Skip to content

Multi year strategy #5

@leehack

Description

@leehack

I'm not sure what's the best way but It would be great how we are going to manage this website next year.
Are we going to create a new repo for the new one?
Can we make it address multi year like below?
http://devfest.gdgmontreal.com <-- current year always
http://devfest.gdgmontreal.com/{year} <-- so next year, this site will be /2024 while the root will be 2025.

So, this year, we can make /2024 as the path but make 2024 default.

What do you think? @Solankimimoh

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions