This is an example outline for a Rancher article. The main bullet points represent the sections the author thinks might work well within the article. The nested sub-items represent sub-sections and descriptions of what each section will cover. Providing a detailed outline and project scope helps the content team offer feedback early and helps ensure that everyone is aligned on expectations. An outline does not necessarily have to reflect the final form of the article, but it should have provide enough details and structure for us evaluate your ideas.

You can see the published article created from this outline here.

* Introduction
* What are namespaces and why would you use them?
    * set up scope for naming
    * segment the cluster into logical chunks
    * can be used to set policies like RBAC, network policies, and quotas
* Common Namespaces Usage Patterns
    * separating workloads by project or team
    * defining development environments
    * isolating customers in a single cluster
* Overview of preconfigured Kubernetes namespaces and what they're used for
    * default
    * kube-public
    * kube-system
* How to use namespaces (`kubectl` commands and a hands-on example walking through the following operations)
    * viewing the cluster's current namespaces
    * creating new namespaces
    * targeting namespaces in commands with the `--namespace=` option
    * changing the default namespace by modifying the `kubectl` context
    * removing namespaces
* How do Rancher Projects relate to namespaces?
    * Projects group namespaces just like namespaces group workloads
    * Helps organize policy that might span across multiple namespaces
    * Adds an additional layer so you can segment objects along two dimensions
* Conclusion

You Might Also Like