-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Website refactor (flask) #74
Comments
Thanks @VeckoTheGecko, for this suggestion for a complete change in the workflow. Maybe you're right that we need a more flashy ('flasky') workflow for the website, but I'm kind of fond of the simpleness of pure html. Call me old-fashioned? In any case, I think this has much lower priority than some of the stuff for the Parcels documentation? Who knows, we might end up with all the Parcels info served through sphinx/parcels-docs anyways? |
Sounds good. Definitely a lower priority 🙂. Just wanted to also flag it in case there were plans in future to broaden the scope of the website. |
Original idea still stands for the most part (will likely still go with flask, but also might do something else), but things to note are:
|
The site currently has data and content intertwined with each other in the HTML making the site a bit difficult to maintain/grow.
I propose to introduce flask with Frozen-Flask to provide tooling to make the site easier to oversee, maintain, and extend.
Main changes:
index.html
andutrechtteam.html
to templatesyaml
files. During build, this data is populated into the templatesEverything according to plan, building the site will create the exact same website files that currently exist. I'm already familiar with this tooling, so this PR shouldn't take me too long to implement.
Blocked by #73
The text was updated successfully, but these errors were encountered: