Skip to content
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 (re)work - Part 1 #1125

Open
garbas opened this issue Sep 19, 2023 · 0 comments
Open

Website (re)work - Part 1 #1125

garbas opened this issue Sep 19, 2023 · 0 comments

Comments

@garbas
Copy link
Member

garbas commented Sep 19, 2023

tl;dr This is a meta ticket to track work done on the website.

In Part 1 focus is to update the current website tech stack. There should not be any visual change. We are leaving that work for the future.

Main goal and the requirement is to have something that more people are comfortable maintaining and finding a helping hand is not an impossible task. That means we selected a stack that lowers the entry bar, has good documentation and keeps maintenance as low as possible.

The group working on this is: @garbas, @thilobillerbeck, @tfc

If anybody want to help please ping us on a Marketing channel

The work for new website is happening in main branch (which is not the default branch at the moment). Once we are confident our work is ready to replace current master branch we will make main branch the default branch.

The stack selected is:

  • astro as the static html generator
  • tailwindcss as the well known and used CSS framework
  • htmx as a simple "Javascript framework" replacement

You might disagree with the above stack, but this issue is not the place to discuss it, but rather to coordinate the work.

thilobillerbeck pushed a commit that referenced this issue Sep 20, 2023
This fixes CI on `main` branch.


ref #1125
garbas added a commit that referenced this issue Sep 21, 2023
This branch adds:
- a reimplementation of the page header in Tailwind (animation currently
not working)
- a more DRY footer and some layout components
- stored menu data in content folder and query it in components
- SVGs imported as proper images instead of inlining

ref #1125

---------

Co-authored-by: Rok Garbas <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant