gohugo-theme-ananke VS docsy

# 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

> cd (The root directory of the Git project. themes exists in current) > git submodule add https://github.com/google/docsy.git themes/docsy

Site URL Hugo theme introduction https://themes.gohugo.io/themes/docsy/ Sample/Demo https://example.docsy.dev/ Documentation https://www.docsy.dev/ Repository https://github.com/google/docsy

A set of Hugo documentation templates for launching open source content. Use case(s): Documentation Author: The Docsy Authors Minimum Hugo version: 0.73.0 Github stars: 1706 Last updated: 2022-05-14 License: Apache-2.0

Download Docsy Docsy demo site ​​​​Minimum Hugo version: 0.73 GitHub stars: 1.7k License: Apache-2.0

Background: I've been a technical writer for 9 years. 6 at Google, 3 as the only writer at an IoT startup.

I helped Corrily with their docs [1] in August. They were interested in readme.io. I wasn't keen on it because I had worked with Retool a few years back and had found readme.io lacking. But I was pleasantly surprised by how much readme.io has progressed since then! If you're looking for a documentation product that is very easy to update and mostly just works, then it's worth checking out.

On https://web.dev I was introduced to Eleventy. Eleventy [2] is now my go to. The documentation for Elecenty itself is very strangely organized and needs a refactor. But I have found that there is always a way to accomplish whatever I need, and usually elegantly.

Another project worth checking out is Docsy [3]. This is a Jekyll template specifically created for technical documentation.

Back at the IoT startup I had to set up the whole documentation system / tooling myself. I used Sphinx and deployed to Heroku. Haven't used Sphinx since then but I remember being satisfied with it back then.

[1] https://docs.corrily.com

[2] https://11ty.dev

[3] https://docsy.dev

I haven't used either of these, but I've heard good things about both https://github.com/google/docsy and https://thegooddocsproject.dev/. If you choose to use either of these, I'd love to hear about it. I have coworkers who contribute to both of them.