-A Hugo theme for creating great technical documentation sites
- {{< blocks/link-down color="info" >}} -
-
-{{% /blocks/lead %}}
-
-{{< blocks/section color="dark" type="features">}}
-{{% blocks/feature icon="fa-lightbulb" title="See Docsy in action!" url="/docs/examples/" %}}
-As well as our example site, there's a growing number of projects using Docsy for their doc sites.
-{{% /blocks/feature %}}
-
-
-{{% blocks/feature icon="fa-brands fa-github" title="Contributions welcome!" url="https://github.com/google/docsy" %}}
-We do a [Pull Request](https://github.com/google/docsy/pulls) contributions workflow on **GitHub**. New users are always welcome!
-{{% /blocks/feature %}}
-
-
-{{% blocks/feature icon="fa-brands fa-twitter" title="Follow us on Twitter!" url="https://twitter.com/docsydocs" %}}
-Find out about new features and how our users are using Docsy.
-{{% /blocks/feature %}}
-
-{{< /blocks/section >}}
diff --git a/userguide/content/en/about/_index.md b/userguide/content/en/about/_index.md
deleted file mode 100644
index 5bc40e2b08..0000000000
--- a/userguide/content/en/about/_index.md
+++ /dev/null
@@ -1,137 +0,0 @@
----
-title: About Docsy
-linkTitle: About
-menu: {main: {weight: 10}}
-layout: docs
----
-
-{{% blocks/cover title="About Docsy" height="auto" %}}
-
-Docsy is a pre-configured Hugo theme that provides the core features and behaviors needed to create a technical documentation site. Use Docsy to set up your documentation website, including an optional Blog section, and then spend your time focusing on authoring technical content. Depending on how you choose to configure Docsy and whether you use a hosting service that supports continuous builds, you can even just add your Markdown or HTML content file into a folder on your source repository, and then sit back while it automatically gets added to your site - complete with updated menus.
-
-Read on to find out more, or visit our [documentation](/docs/) to get started!
-{{% /blocks/cover %}}
-
-{{% blocks/section type="section" color="primary" %}}
-## So what’s a technical documentation site?
-
-A technical documentation site is a website that your users can visit to find the documentation for your technical project. Your documentation set contains all the information you think your users might need to engage with your project, from overviews that help them understand what the project is for, to instructions for specific tasks. Depending on the size of the project, a documentation set can be a page or two or an entire “book” with different types of information.
-
-**Most users don’t want to have to spend much time looking at docs - they want to try your great project!** So how do you make sure your technical documentation set gives users what they need to easily understand your project and get things done? We think a good technical documentation set should be:
-
-* **Reliable**: Is it true?
-* **Comprehensive**: Does it have all the information your target users might need?
-* **Well-organized and navigable**: Can the user find the information they need? Are similar types of information (all the information about a feature, all your reference information) grouped together?
-
-If you have users around the world, you might also want to provide your content in multiple languages, and if you have an open source project, you’ll probably want your users to be able to contribute to the docs.
-
-Once you have your content, you use a technical documentation site to publish your technical documentation set online for your users. In addition to your documentation, your site might also contain material like contact information, a blog, or information about how to contribute to the project.
-{{% /blocks/section %}}
-
-{{% blocks/section type="section" color="white" %}}
-## How does Docsy help?
-
-Particularly when working with open source projects, it can be difficult to figure out how to turn all your product knowledge into a website that helps and engages your users. **Enter Docsy!**
-
-Docsy gives you a theme for the [Hugo](https://gohugo.io/) static site generator, an established open source tool that builds ready-to-serve websites from a set of theme and content files. The Docsy theme provides you with useful stuff for a technical documentation site that *isn’t* your own content:
-
-| Page layouts optimized for different content types - | -Navigation, page menus, headers, landing pages, blog snippets, feedback links - you just provide the content. - | -
| Autogenerated navigation - | -Organize your docs in logical folders and get instantly updated navigation to help your users find them. - | -
| Language switchers - | -Builds on Hugo’s multi-language support to make it easy to create a site in multiple languages. - | -
| Feedback, contribution, and contact links - | -Let your users file issues and edit docs with a single click, or follow contact links to join you on Slack, Twitter, or mailing lists. - | -
| Custom shortcodes - | -Reusable snippets of HTML you can use to create alerts, image boxes, landing page blocks, and more. - | -
| Easy customization - | -Use the theme as-is for a basic, clean design, or update a file or two to get your own look. - | -
| Simple previews and deployment - | -Because Docsy is a Hugo theme, you get all the advantages of building with Hugo - simple, fast local previews, and, depending on your deployment options, continuous deployment from GitHub or other Git providers. - | -
- 
- assets/scss/_variables.scss][_variables]. For information about other Bootstrap 4 variables, see [Variable defaults][] and Bootstrap's [v4-dev/scss/_variables.scss][] file.
-- [`assets/scss/`**`_styles_project.scss`**][_styles_project] is where you can add your own custom SCSS styles, including overriding any of the styles in Docsy's theme SCSS files.
-
-[_styles_project]: https://github.com/google/docsy/blob/main/assets/scss/_styles_project.scss
-[_variables_project]: https://github.com/google/docsy/blob/main/assets/scss/_variables_project.scss
-[_variables]: https://github.com/google/docsy/blob/main/assets/scss/_variables.scss
-[v4-dev/scss/_variables.scss]: https://github.com/twbs/bootstrap/blob/v4-dev/scss/_variables.scss
-[Variable defaults]: https://getbootstrap.com/docs/4.1/getting-started/theming/#variable-defaults
-
-{{% alert title="Tip" %}}
-PostCSS (autoprefixing of CSS browser-prefixes) is not enabled when running in server mode (it is a little slow), so Chrome is the recommended choice for development.
-{{% /alert %}}
-
-## Site colors
-
-To easily customize your site's colors, add SCSS variable overrides to
-`assets/scss/_variables_project.scss`. A simple example changing the primary and
-secondary color to two shades of purple:
-
-```scss
-$primary: #390040;
-$secondary: #A23B72;
-```
-
-The theme has features such as rounded corners and gradient backgrounds enabled by default. These can also be toggled in your project variables file:
-
-```scss
-$enable-gradients: true;
-$enable-rounded: true;
-$enable-shadows: true;
-```
-
-## Fonts
-
-The theme uses [Open Sans](https://fonts.google.com/specimen/Open+Sans) as its primary font. To disable Google Fonts and use a system font, set this SCSS variable in `assets/scss/_variables_project.scss`:
-
-```scss
-$td-enable-google-fonts: false;
-```
-
-To configure another Google Font:
-
-```scss
-$google_font_name: "Open Sans";
-$google_font_family: "Open+Sans:300,300i,400,400i,700,700i";
-```
-
-Note that if you decide to go with a font with different weights (in the built-in configuration this is `300` (light), `400` (medium) and `700` (bold)), you also need to adjust the weight related variables, i.e. variables starting with `$font-weight-`.
-
-## CSS utilities
-
-For documentation of available CSS utility classes, see the [Bootstrap Documentation](https://getbootstrap.com/). This theme adds very little on its own in this area. However, we have added some color state CSS classes that can be useful in a dynamic context:
-
-* `.-bg-
- {{}}
- {{%/* tab header="Swahili" lang="sw" */%}}
- 
- **Karibu sana!**
- {{%/* /tab */%}}
-{{}}
-```
-
-This code translates to the right aligned tabbed pane below, showing a `Welcome!` greeting in English, German or Swahili:
-
-{{< tabpane text=true right=true >}}
- {{% tab header="**Languages**:" disabled=true /%}}
- {{% tab header="English" lang="en" %}}
- 
- **Welcome!**
- {{% /tab %}}
- {{< tab header="German" lang="de" >}}
- Herzlich willkommen!
-
- {{< /tab >}}
- {{% tab header="Swahili" lang="sw" %}}
- 
- **Karibu sana!**
- {{% /tab %}}
-{{< /tabpane >}}
-
-### Shortcode details
-
-Tabbed panes are implemented using two shortcodes:
-
-* The `tabpane` shortcode, which is the container element for the tabs. This shortcode can hold the optional named parameters `lang`, `highlight` and `right`. The value of the optional parameters `lang` and `highlight` are passed on as second `LANG` and third `OPTIONS` arguments to Hugo's built-in [`highlight`](https://gohugo.io/functions/highlight/) function which is used to render the code blocks of the individual tabs. Specify `right=true` if you want to right align your tabs. In case the header text of the tab equals the language used in the tab's code block (as in the first tabbed pane example above), you may specify `langEqualsHeader=true` in the surrounding `tabpane` shortcode. Then, the header text of the individual tab is automatically set as `lang` parameter of the respective tab.
-* The various `tab` shortcodes represent the tabs you would like to show. Specify the named parameter `header` for each tab in order to set the header text of the tab. If the `header` parameter is the only parameter inside your tab shortcode, you can specify the header as unnamed parameter, something like `{ tab "My header" }} … {{ /tab }}`. If your `tab` shortcode does not have any parameters, the header of the tab will default to `Tab n`. To split the panes into a left aligned and a right aligned tab group, specify `right=true` in the dividing tab. By giving `right=true` several times, you can even render multiple tab groups. You can disable a tab by specifying the parameter `disabled=true`. For enabled tabs, there are two modes for content display, `code` representation and _textual_ representation:
- * By default, the tab's content is rendered as `code block`. In order to get proper syntax highlighting, specify the named parameter `lang` --and optionally the parameter `highlight`-- for each tab. Parameters set in the parent `tabpane` shortcode will be overwritten.
- * If the contents of your tabs should be rendered as text with different styles and with optional images, specify `text=true` as parameter of your `tabpane` (or your `tab`). If your content is markdown, use the percent sign `%` as outermost delimiter of your `tab` shortcode, your markup should look like `{{%/* tab */%}}`Your \*\*markdown\*\* content`{{%/* /tab */%}}`. In case of HTML content, use square brackets `<>` as outermost delimiters: `{{}}`Your <b>HTML</b> content`{{}}`.
-
-{{% alert title="Info" %}}
-By default, the language of the selected tab is stored and preserved between different browser sessions. If the content length within your tabs differs greatly, this may lead to unwanted scrolling when switching between tabs. To disable this unwanted behaviour, specify `persistLang=false` within your `tabpane` shortcode.
-{{% /alert %}}
-
-## Card panes
-
-When authoring content, it's sometimes very useful to put similar text blocks or code fragments on card like elements, which can be optionally presented side by side. Let's showcase this feature with the following sample card group which shows the first four Presidents of the United States:
-
-{{< cardpane >}}
-{{< card header="**George Washington**" title="\*1732 †1799" subtitle="**President:** 1789 – 1797" footer="">}}
-
-{{< /card >}}
-{{< card header="**John Adams**" title="\* 1735 † 1826" subtitle="**President:** 1797 – 1801" footer="" >}}
-
-{{< /card >}}
-{{< card header="**Thomas Jefferson**" title="\* 1743 † 1826" subtitle="**President:** 1801 – 1809" footer="" >}}
-
-{{< /card >}}
-{{< card header="**James Madison**" title="\* 1751 † 1836" subtitle="**President:** 1809 – 1817" footer="" >}}
-
-{{< /card >}}
-{{< /cardpane >}}
-
-Docsy supports creating such card panes via different shortcodes:
-
-* The `cardpane` shortcode which is the container element for the various cards to be presented.
-* The `card` shortcodes, with each shortcode representing an individual card. While cards are often presented inside a card group, a single card may stand on its own, too. A `card` shortcode can hold text, images or any other arbitrary kind of markdown or HTML markup as content. If your content is programming code, you are advised to make use of the `card-code` shortcode, a special kind of card with code-highlighting and other optional features like line numbers, highlighting of certain lines, ….
-
-### Shortcode `card` (for text, images, …)
-
-As stated above, a card is coded using one of the shortcode `card` or `card-code`.
-If your content is any kind of text other than programming code, use the universal `card`shortcode. The following code sample demonstrates how to code a card element:
-
-```go-html-template
-{{*/>}}
-Imagine there's no heaven, It's easy if you try
-