Sam Morris

We currently have two different developer guides in documentation, and both could use clearer names. For the one inside the Admin Guide, `Customization Guide` is more accurate for what it...

docs: Update general docs README

1

https://github.com/JanssenProject/jans/blob/main/docs/README.md This file is already out of date and needs to be updated with final content.

docs: rename category filenames from Kubernetes to Cloud Native

2

### Prepare - [x] Read [PR guidelines](https://github.com/JanssenProject/jans/blob/main/docs/CONTRIBUTING.md#prs) - [x] Read [license information](https://github.com/JanssenProject/jans/blob/main/LICENSE) ------------------- ### Description Renamed most filenames from Kubernetes to Cloud Native to be more inclusive of different deployment...

docs: "Kubernetes" docs names should be generalized to "Cloud Native"

1

Currently, our documentation is divided along Cloud Native and Virtual Machine administration, since these are the two broad categories. So far, we've been using "Kubernetes" instead of "Cloud Native" for...

Mkdocs makes no distinction (anymore) between files named `README.md` and `index.md`. Right now, we have a mixture of the two. It makes more sense for the `README.md` naming convention, since...

As the reference guide grows, its current structure is becoming unwieldy. We need to reorganize it for legibility. For example, we should break the lists of configuration into categories that...