guides: Add instructions for multiple SSG tools

[davlgd]

Checklist

• My PR is related to an opened issue : #

⚠️ If changes affect GitHub Action files

• I have added tests to cover my changes : link

Pull request type

Please check the type of change your PR introduces:

• Documentation content changes
• Bugfix on the site
• Build related changes
• Other (please describe):

Description

New guides for multiple SSG:

• Astro
• Docusaurus
• 11ty
• Hexo
• Hugo
• Lume/Deno
• mdBook
• MkDocs
• Nuxt

I used partials for shared instructions and added SVG icons

Reviewes

Who should review these changes? @

[github-actions]

Deployment has finished 👁️👄👁️ Your app is available here

[juliamrch]

Build folder

Update: after running some tests, that seems to be an issue in our Node runtime, and not Static.

It should be noted that folders like /dist or /build in JavaScript/Typescript based frameworks aren't committed by default, and that Clever Cloud permission levels will log "permission denied" when trying to create it and use it as webroot.

In these tutorials, we need to specify that the user must:

1. Build locally the site before the first deploy
2. Commit the build folder

Files inside the /dist and /build can be omitted, because they will be recreated again while deploying.

For example, see these instructions on deploying a T3 app on Clever Cloud.

[juliamrch]

I find all these new guides amazing. Thanks for all this work.

Only change to ensure presentation consistency and readability is to replace the title by the framework name, and we should be good to go.

[davlgd]

I'm not sure so short titles will be good for SEO. Can you check with marketing team?

[juliamrch]

I'm not sure so short titles will be good for SEO. Can you check with marketing team?

It's not a SEO but a readability issue. Readability and clarity in sidebar for the doc is always privileged, and yes, even over SEO. Check the rest of the titles in /guides: it's the framework name, and that's it. The SEO is handled by the description in metadata.

[davlgd]

The metadata is not enough for a good SEO strategy, that's my point. We also need these guides to be found/read. I agree on the importance of readability, but it can't be only one or the other. It's why I asked to involve marketing team to reach a consensus on this.

[juliamrch]

Replace path to avoid hiding frameworks in another level and let them be indexed by alphabetical order as intended for this page.

[juliamrch]

The metadata is not enough for a good SEO strategy, that's my point. We also need these guides to be found/read. I agree on the importance of readability, but it can't be only one or the other. It's why I asked to involve marketing team to reach a consensus on this.

Head of Marketing has already approved the structure of this page when building the site and restructuring the doc. It took a lot of discussions and research. This subject has already been covered.

[davlgd]

If it's ok for marketing team, it's ok for me

[github-actions]

🚀 Your app has been updated and is available here

[juliamrch]

Subjects left:

• Do we need a partial for the cards, since we a a single level in /guides/_index/md?
• Subtitle partial missing to keep the look consistent

I can do these changes after merging and before pushing to prod, it's not a big issue

[juliamrch]

There were some conflicts in icons.yml that I just fixed (by setting current fluent and grade icons). Could you review it @davlgd ? And if everything is ok we can merge the new guides.

[davlgd]

It's ok for me @juliamrch

[github-actions]

Your review app has been deleted 👋