Migration spike : simpler stack with an eventual redesign as the cherry on top#384
Open
sidd190 wants to merge 4 commits into
Open
Migration spike : simpler stack with an eventual redesign as the cherry on top#384sidd190 wants to merge 4 commits into
sidd190 wants to merge 4 commits into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This is a draft migration spike for moving Forklore from the current Nuxt stack toward a simpler static-site setup.
[WIP] : #385
The goal is to validate whether Eleventy + Markdown/frontmatter can cover the maintainer landing page and maintainer detail pages while keeping the current production
deployment untouched.
Screencast.from.2026-07-06.00-57-51.webm
I added an isolated eleventy spike under
site/, with a brief document mentioning choices, everything is still a draft and I'm working on it, I'll be doing a redesign on top of this branch with help of another branch from this, the goal is first to perfect this to the pixel for the eleventy tech stack instead of just basic outline, so that any design changes made on top of this don't miss any element or content.The planet part can be a later phase of this, firstly focusing on the whole user facing pages for maintainers.
This PR does not change the current production deployment anyhow (I hope, lol).
How to test the spike
Going ahead, can be done in sub issues :
Good context to remember
Eleventy is something I need reviews on around how regularly this will update and stuff like that, we can reduce maintanence burden by a lot if it's static, and have it be a markdown/json content heavy pipeline with gh actions automating and validating stuff.