Pick static site generator #5

realaravinth commented 2022年11月07日 12:32:24 +01:00

No description provided.

realaravinth commented 2022年11月07日 12:33:57 +01:00

I propose Zola because it is simple and minimalistic (and is also the tool that I'm familiar with 😊 ).

Features:

1. I18n
2. Search
3. Sass compilation
4. Jinja2 style templates
5. Single binary

I propose Zola because it is simple and minimalistic (and is also the tool that I'm familiar with 😊 ). ## Features: 1. [I18n](https://www.getzola.org/documentation/content/multilingual/) 2. Search 3. Sass compilation 4. Jinja2 style templates 5. Single binary

Ghost commented 2022年11月07日 17:52:35 +01:00

Can it be linked to Weblate somehow? I mean... you can do it manually I'm sure. But is there a recommended way to do that already?

Can it be linked to Weblate somehow? I mean... you can do it manually I'm sure. But is there a recommended way to do that already?

realaravinth commented 2022年11月08日 11:51:21 +01:00

Can it be linked to Weblate somehow? I mean... you can do it manually I'm sure. But is there a recommended way to do that already?

Not yet. Took a deeper look at Zola i18n support, it is very basic and WIP. They are leaning towards implementing Fulent, a format that has limited support in Weblate.

But a manual integration is possible.

> Can it be linked to Weblate somehow? I mean... you can do it manually I'm sure. But is there a recommended way to do that already? Not yet. Took a deeper look at Zola i18n support, it is very basic and WIP. They are leaning towards implementing [Fulent](https://wiki.mozilla.org/Fluent), a format that has [limited support in Weblate](https://docs.weblate.org/en/latest/formats.html#fluent). But a manual integration is possible.

Ryuno-Ki commented 2022年11月08日 15:55:19 +01:00

There are plenty of SSGs to pick from: https://jamstack.org/generators/

Might be worth to have someone go through them and evaluate them according to our criteria.

There are plenty of SSGs to pick from: https://jamstack.org/generators/ Might be worth to have someone go through them and evaluate them according to our criteria.

fnetX commented 2022年11月08日 16:27:47 +01:00

To throw some in:

• I really appreciate onepagers (no file structure, just a long landing page). Especially to present something, this helps in getting users interested and not confused. Stuff like admin docs etc can then be built wiht other tools. To get this started, I often use pandoc (markdown → html, with a custom template and only a few lines of CSS)
• I (ab-)use Material for MkDocs as a theme. https://squidfunk.github.io/mkdocs-material/ it's mainly for docs, but can also suit as a great homepage if you customize a little and think about the file structure

To throw some in: - I really appreciate onepagers (no file structure, just a long landing page). Especially to present something, this helps in getting users interested and not confused. Stuff like admin docs etc can then be built wiht other tools. To get this started, I often use pandoc (markdown → html, with a custom template and only a few lines of CSS) - I (ab-)use Material for MkDocs as a theme. https://squidfunk.github.io/mkdocs-material/ it's mainly for docs, but can also suit as a great homepage if you customize a little and think about the file structure

oliverpool commented 2022年11月08日 21:08:55 +01:00

Cross-posting from the chat

Thank you @fnetX I tried Material for MkDocs and it looks promising!

WIP available under https://oliverpool.srht.site/
I have to decide where to share the code (as a branch here, or repo I own).

*Cross-posting from the chat* Thank you @fnetX I tried Material for MkDocs and it looks promising! WIP available under https://oliverpool.srht.site/ I have to decide where to share the code (as a branch here, or repo I own).

oliverpool commented 2022年11月09日 08:47:38 +01:00

In #7 @Ryuno-Ki mentioned https://www.11ty.dev/.

I used it for a website, but I would not do it again (livereload is quite slow, since the whole site has to be build on every change).

---

I used https://astro.build/ for another site, which I found quite enjoyable (except for their "rushing" out of beta: https://github.com/withastro/astro/issues/4190#issuecomment-1216755788)

In #7 @Ryuno-Ki mentioned https://www.11ty.dev/. I used it for a website, but I would not do it again (livereload is quite slow, since the whole site has to be build on every change). --- I used https://astro.build/ for another site, which I found quite enjoyable (except for their "rushing" out of beta: https://github.com/withastro/astro/issues/4190#issuecomment-1216755788)

Ryuno-Ki commented 2022年11月09日 08:50:04 +01:00

(livereload is quite slow, since the whole site has to be build on every change).

That's not true anymore :)
Might require some configuration, though.

> (livereload is quite slow, since the whole site has to be build on every change). That's not true anymore :) Might require some configuration, though.

oliverpool commented 2022年11月09日 09:09:54 +01:00

Regarding astro.build https://astrowind.vercel.app/ seems to tick many boxes from codename/meta#30

• Responsive
• SEO
• light/dark theme
• No JS
• no external assets
• blog
• RSS

As mentioned, I already worked with this static generator and would be more comfortable than using mkdocs-material.

However astro.build probably has a bus-factor of 1...

Regarding astro.build https://astrowind.vercel.app/ seems to tick many boxes from codename/meta#30 - Responsive - SEO - light/dark theme - No JS - no external assets - blog - RSS As mentioned, I already worked with this static generator and would be more comfortable than using mkdocs-material. However astro.build probably has a bus-factor of 1...

caesar commented 2022年11月09日 09:15:21 +01:00

I think any mainstream SSG will be learnable easily-enough for most frontend devs, so I wouldn't worry too much about bus factor unless something really esoteric is picked.

That said, I haven't used any of the SSGs suggested so far. If I was building the site I'd reach for SvelteKit by default, but like everyone else's suggestions, it's just because I'm familiar with it and I like it.

I've heard good things about Astro.
Zola looks very interesting.
Personally I'd avoid anything Python-based because it's always a nightmare to set up but that's just me 😆

I'd say ease of doing i18n should be a very important factor in the choice.

I think any mainstream SSG will be learnable easily-enough for most frontend devs, so I wouldn't worry *too* much about bus factor unless something really esoteric is picked. That said, I haven't used any of the SSGs suggested so far. If I was building the site I'd reach for SvelteKit by default, but like everyone else's suggestions, it's just because I'm familiar with it and I like it. I've heard good things about Astro. Zola looks very interesting. Personally I'd avoid anything Python-based because it's always a nightmare to set up but that's just me 😆 I'd say ease of doing i18n should be a very important factor in the choice.

Ryuno-Ki commented 2022年11月09日 09:55:56 +01:00

I'd reach for SvelteKit by default

Let's go with Aral's Kitten *jk

> I'd reach for SvelteKit by default Let's go with Aral's [Kitten](https://codeberg.org/kitten/app) *jk

Ghost commented 2022年11月11日 14:34:24 +01:00

For the record @oliverpool experiments with https://astro.build in this pull request.

Now that the discussion settled a little, maybe a decision can be made. As someone writing content I have no preference: happy with anything.

In the meantime I'll just add markdown files at the root of the repository and will move / adapt them in the appropriate directory later.

For the record @oliverpool experiments with https://astro.build in [this pull request](https://codeberg.org/codename/website/pulls/12). Now that the discussion settled a little, maybe a decision can be made. As someone writing content I have no preference: happy with anything. In the meantime I'll just add markdown files at the root of the repository and will move / adapt them in the appropriate directory later.

Ghost commented 2022年11月12日 11:32:26 +01:00

When the static site generator is decided, the CI is ready to use it:

• Modify .woodpecker.yml to use the static site generator
• The HTML pages will show on https://codeberg.page at https://codename.codeberg.page/website/

When the static site generator is decided, the [CI is ready to use it](https://codeberg.org/codename/website/issues/13): * Modify [.woodpecker.yml](https://codeberg.org/codename/website/src/commit/a3eb7979e9f108710199cd7ffa4ef86680fabce1/.woodpecker.yml) to use the static site generator * The HTML pages will show on https://codeberg.page at https://codename.codeberg.page/website/

oliverpool commented 2022年11月14日 10:53:12 +01:00

Since no concern was raised against astro, I went ahead and merged it.

I updated the CI preparation of @dachary to automatically push to https://codeberg.org/codename/pages, which is visitable on https://codename.codeberg.page/ (having / is easier than dealing with a /website/ subfolder).

Feel free to re-open this issue, to reconsider this.

Since no concern was raised against astro, I went ahead and merged it. I updated the CI preparation of @dachary to automatically push to https://codeberg.org/codename/pages, which is visitable on https://codename.codeberg.page/ (having `/` is easier than dealing with a `/website/` subfolder). Feel free to re-open this issue, to reconsider this.