Project migration #5

New issue

Open

opened 2024-10-26 15:59:18 -03:00 by aleidk · 0 comments

aleidk commented

2024-10-26 15:59:18 -03:00

Owner

The project need an overhaul to provide a more simpler way to update content, be more future proof and prevent CI/CD failing.

Astro is a really good SSG, but each time I want to work on this project, a brand new version of Astro has come and I cannot keep up with it, so I'm gonna change to a more "stable" and "complete" SSG that does the bare minimum that I need. More complex functionality can be added as custom hooks into the SSG and/or with custom JS.

Steps:

Styles has been move to it's own repo (alecodes/mini-strap), remove from here and import the library/components
Setup new SSG, options:
- Cobalt
- Zola
- Static Web Server -> this could be useful for a docker deploy
Setup repository functionality from other projects:
- Issue templates
- Autodeploy that respect the content update vs project update

The project need an overhaul to provide a more simpler way to update content, be more future proof and prevent CI/CD failing. Astro is a really good SSG, but each time I want to work on this project, a brand new version of Astro has come and I cannot keep up with it, so I'm gonna change to a more "stable" and "complete" SSG that does the bare minimum that I need. More complex functionality can be added as custom hooks into the SSG and/or with custom JS. Steps: - [ ] Styles has been move to it's own repo (alecodes/mini-strap), remove from here and import the library/components - [ ] Setup new SSG, options: - [Cobalt](https://cobalt-org.github.io/) - [Zola](https://www.getzola.org/) - [Static Web Server](https://static-web-server.net/) -> this could be useful for a docker deploy - [ ] Setup repository functionality from other projects: - Issue templates - Autodeploy that respect the content update vs project update