docs: Add pandoc theme to docs site

[aslak01]

📑 Description

Added a nicer theme (with dark mode support) to the pandoc markdown-html conversion, tweaked colors to match astrotheme.

Credit to https://github.com/jez/pandoc-markdown-css-theme

Preview: https://aslak01.github.io/astrocommunity/

ℹ Additional Information

Moved bash script and resources to /docs/

[github-actions]

Review Checklist

Does this PR follow the [Contribution Guidelines](development guidelines)? Following is a partial checklist:

Proper conventional commit scoping:

• If you are adding a new plugin, the scope would be the name of the category it is being added into. ex. feat(utility): added noice.nvim plugin

• If you are modifying a pre-existing plugin or pack, the scope would be the name of the plugin folder. ex. fix(noice-nvim): fix LSP handler error

• Pull request title has the appropriate conventional commit type and scope where the scope is the name of the pre-existing directory in the project as described above

• README is properly formatted and uses fenced in links with <url> unless they are inside a [title](url)

• Entry returns a single plugin spec with the new plugin as the only top level spec (not applicable for recipes or packs).

• Proper usage of opts table rather than setting things up with the config function.

• Proper usage of specs table for all specs that are not dependencies of a given plugin (not applicable for recipes or packs).

[Kamilcuk]

Hi. The page looks just incredibly stunning. Check review checklist - follow "proper conventional commit scoping", see https://www.conventionalcommits.org/en/v1.0.0/ . Your commits should start with build(docs): for example. The page visual is just 5 out of 5 stars.

[aslak01]

Thanks @Kamilcuk, and thanks for the original script, it was really inspiring to see such a simple way to hook into github files/actions rather than using pre made abstractions. I would like to mess around with this system more, but at the moment I'm too busy. I can imagine some bash script component system to make it easier to work on individial bits of the generated site, or something like it.

Also, seems like your suggested title does not pass the repo checks either, to me it looks like it's expecting a pr to target a specific already existing plugin, but I didn't have the time to look at it too much.

[Uzaaft]

Turns out the theme is not changing only in the arc browser. On safari it changes fine. @aslak01 Did you by any chance test on firefox/chrome?

[Uzaaft]

Hi. The page looks just incredibly stunning. Check review checklist - follow "proper conventional commit scoping", see conventionalcommits.org/en/v1.0.0 . Your commits should start with build(docs): for example. The page visual is just 5 out of 5 stars.

Wrong. Its docs.

[Uzaaft]

See f5f3442

[Uzaaft]

Chrome works fine. Firefox as well.

Fuck Arc, less than 1% uses it. LGTM.

@mehalter U merge pookie?

[Uzaaft]

@aslak01 any reason why you added a shitton of fonts? Cant they be fetched at runtime?

[ALameLlama]

Pretty sure we can remove most of these just by doing

@import url('https://fonts.googleapis.com/css2?family=Inter:wght@100;200;300;400;500;600;700;800;900&display=swap');

should be able to remove the font folder and font.css if we include that import in the theme.css

[aslak01]

Yep, that'd work but I prefer to self-host fonts rather than depend on google fonts where I can personally. It's the same pattern that's in use on astronvim.com.

If you look in the network tab, only two fonts files are loaded, the rest are just there in case we need them in the future, since Inter is an open source font and provides the entire set of weights and styles as a set.

[aslak01]

@Uzaaft I can change it to fetch the font remotely if you want to make that a requirement but in my opinion "locally" hosted fonts are better.