You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 7, 2024. It is now read-only.
I've been browsing the codebase, as I would like to propose some changes, yet it seems to me the current approach is somewhat over-engineered for its goal.
I would like to propose we use a tool like Zola or Hugo to write the content in simple to maintain markdown files, and let the theme and workflows generate the final site.
I believe this change would benefit in the following ways:
Less overhead to maintain.
Less overhead to onboard (no need to learn yew, or know node)
We can focus only on writing content with a simple syntax.
An easier way to maintain may help bring more
I have a couple of examples in my public repos, will share some links.
Many thanks,
H.
The text was updated successfully, but these errors were encountered:
SGTM. For the moment this site was developed the focus used to be learning about Rust + Wasm on the Web.
But in terms of goals, I believe static site generators are more suitable for use cases where you want to focus in content publishing, were you publish posts or documentation based on some markdown/template.
In this particular case, we are developing a landing page with informational purposes.
If theres no plans on adding content I would even go with pure HTML/CSS & JavaScript, for simplicity.
Hi,
I've been browsing the codebase, as I would like to propose some changes, yet it seems to me the current approach is somewhat over-engineered for its goal.
I would like to propose we use a tool like Zola or Hugo to write the content in simple to maintain markdown files, and let the theme and workflows generate the final site.
I believe this change would benefit in the following ways:
I have a couple of examples in my public repos, will share some links.
Many thanks,
H.
The text was updated successfully, but these errors were encountered: