miniohq / gluegun Goto Github PK

Since the repo is now cleaned up. Please send a pr to customize color/font etc only for docs.minio.io. The changes should only be driven from variable.scss files and no other conflicts should exist.

From user Andrew on Slack channel:

Hi, the links to Client grants, Configuring wso2, Configuring opa, Configuring etcd (optional needed only in gateway or federation mode) in the document page for Minio STS Quickstart Guide (https://docs.minio.io/docs/minio-sts-quickstart-guide.html) are not accessible, can someone take a look?

Eg : Learn more about Deploying MinIO in Distributed Mode <- Deploying is capitalized.
This guide covers deployment documentation for Orchestration platforms <- Orchestration

It's unclear what our principle of capitalization is. Please can you clarify for us to fix them if needed.

Change logo to raspberry colored logo.

In order to simplify our yml file, we can just hardcode analytics scripts that are not widely used, as we have been adding lots of fields lately.

Short term solution: one 404.html with css and js links from vendor folder.
Longterm solution: Generate 404.html from 404.erb

I would like to specify topics in the site.yml as files that exist and properly render in the content system but do NOT appear in the left nav.

To solve this issue, we would need Algolia to index our English and Chinese docs separately.

It was discussed in a recent meeting to allow categories specified in the site.yml to be landing pages with editable content.

The logo is displayed in full size before being resized while switching between translations.

As @jtsymonds reported on miniohq/min.io#500, we are displaying a generic favicon as the docs site doesn't currently have one. We can directly add the favicon on miniohq/gluegun and if necessary we add a field for the favicon on the yml file for the minio/gluegun repository for a more general approach.

As per @Jayshreemagdum's feedback, we would like to remove the MinIO logo on the Quickstart Guide located on the index page of the docs. However, we would like to keep it on the GitHub repo. To fix this, we can use the display: none; CSS rule isolating the logo element.