gohugo-theme-ananke VS Hugo

# update packages sudo apt-get update sudo apt-get upgrade # install dependencies sudo apt install hugo git neovim ca-certificates \ curl apt-transport-https lsb-release gnupg # add microsoft signing key to install azure cli sudo mkdir -p /etc/apt/keyrings curl -sLS https://packages.microsoft.com/keys/microsoft.asc | gpg --dearmor | sudo tee /etc/apt/keyrings/microsoft.gpg > /dev/null sudo chmod go+r /etc/apt/keyrings/microsoft.gpg AZ_REPO=$(lsb_release -cs) echo "deb [arch=`dpkg --print-architecture` signed-by=/etc/apt/keyrings/microsoft.gpg] https://packages.microsoft.com/repos/azure-cli/ $AZ_REPO main" | sudo tee /etc/apt/sources.list.d/azure-cli.list # install the azure cli sudo apt-get update sudo apt-get install azure-cli # create the static site hugo new site azure-static-site cd azure-static-site git init # setup static site theme git submodule add https://github.com/theNewDynamic/gohugo-theme-ananke themes/ananke echo "theme = 'ananke'" >> config.toml # create a page on the site hugo new posts/my-first-post.md # edit the post using neovim nvim content/posts/my-first-post.md # start the hugo dev server hugo server --buildDrafts hugo server -D

Agree completely with /u/GaProgMan said about showing your code. It sounds as if the theme simply lacks the styling — CSS or Sass — to show the missing items, but there’s no way for anyone else to be reasonably sure about that without seeing as much of your code if possible (ideally, the entire repo). While others can certainly see the Ananke repo, we can’t know what, if any, modifications you may have made to its styling.

Download Ananke theme for Hugo

$ cd quickstart $ git init $ git submodule add https://github.com/theNewDynamic/gohugo-theme-ananke.git themes/ananke

scripts: hugo: kool docker -p 1313:1313 klakegg/hugo:ext-alpine dev: kool run hugo server -D # remove or modify to suit the needs of your project quickstart: - kool start - git init - git submodule add https://github.com/theNewDynamic/gohugo-theme-ananke.git themes/ananke - echo theme = \"ananke\" >> config.toml - kool run hugo new posts/my-first-post.md - kool run dev setup: - kool start - kool run dev

At one point though I realized there is a scaling problem with my build minutes. I knew that golang has considerably faster builds and in my case the easy fix is swapping over to Hugo.

This blog is running on Hugo. It had previously been running on Jekyll. Both these SSGs ship with the ability to create excerpts from your markdown content in 1 line or thereabouts.

Hugo

Hugo is a popular static site generator specifically designed to create websites and documentation lightning-fast. Its minimalist approach, emphasis on speed, and ease of use have made it popular among developers, technical writers, and anybody looking to construct high-quality websites without the complexity of typical CMS platforms.

As per many other comments, it sounds like a static site generator like Hugo (https://gohugo.io/) or Jekyll (https://jekyllrb.com/), hosted on GitHub Pages (https://pages.github.com/) or GitLab Pages (https://about.gitlab.com/stages-devops-lifecycle/pages/), would be a good match. If you set up GitHub Actions or GitLab CI/CD to do the build and deploy (see e.g. https://gohugo.io/hosting-and-deployment/hosting-on-github/), your normal workflow will simply be to edit markdown and do a git push to make your changes live. There are a number of pre-built themes (e.g. https://themes.gohugo.io/) you can use, and these are realtively straightforward to tweak to your requirements.

Create the technical documentation of your project You can use any of the following options: * A wiki, like the ArchWiki that uses MediaWiki * Read the Docs, used by projects like Setuptools. Check Awesome Read the Docs for more examples. * Create a website * Create a blog, like the documentation of Blowfish, a theme for Hugo.

Doing this made me appreciate existing SSGs like Hugo and Next.js even more👏👏

I suggest hugo: https://gohugo.io/

Generates a completely static website from MD (and other formats) files; also handles themes (including a lot of them rendering well on mobile), and different types of content - posts, articles, etc. - depending on the theme.

It's open source and, being completely static, cheap as fuck to self host.