-
Notifications
You must be signed in to change notification settings - Fork 83
Open
0 / 10 of 1 issue completedDescription
We'd like to no longer run a MediaWiki instance for each event, because:
- Maintaining a separate MediaWiki instance for each historic event adds maintenance overhead and uses up server resources. There's still no viable static export method.
- Keeping the wiki online is a constant struggle in the age of impolite scrapers, and MediaWiki makes it more difficult because we can't make resource-intensive features like page history login-only.
- We've already moved village registration/management to the main website. It's confusing to have two different places to put info.
- We don't need the complexity of MediaWiki (anything that uses Semantic MediaWiki is probably better living on the main website in a more structured way).
- In general, we should be able to provide a simpler user experience by keeping everything on the main website, behind a single login.
The CCC has done a similar thing with their hub system and it works quite well.
Looking at the wiki from 2024, we need:
- Some capability for user-editable village pages. Sub-pages might be nice but probably aren't needed.
- A global namespace for stuff like lift sharing and camping gear exchange.
Sub-issues
Metadata
Metadata
Assignees
Labels
No labels