Docs style guide - how should mixed content be badged?
Problem to solve
The GitLab documentation style guide states that where content applies to a specific product tier, a badge indicating that is to be added to the title. For details, see Product tier badges.
The problem here is that some content may apply to different tiers. In these circumstances, a single tier can't be applied to a page.
Further details
Example pages:
- https://docs.gitlab.com/ee/user/project/settings/project_access_tokens.html
- Compares two features, each of which has a different tier
- Is mostly free, but has a few Ultimate features
Here is the full list of pages with no tier on the H1:
- Activate GitLab EE with a license file or key
- Add Docker executor support for a Windows version
- Advanced configuration
- AI/ML powered features
- All feature flags in GitLab
- Architecture at GitLab
- Architecture
- Arkose Protect
- Authenticate with registry in Docker-in-Docker
- Azure MinIO gateway when using the GitLab chart
- Backup and restore
- Build packages
- Check for background migrations before upgrading
- Choosing a GitLab subscription
- CI/CD variables
- Community programs
- Comparison of GitLab self-managed with GitLab SaaS
- Configure GitLab as an OAuth 2.0 authentication identity provider
- Configure MinIO with the GitLab chart
- Configure the GitLab chart with an external database
- Configure the GitLab chart with an external Gitaly
- Configure the GitLab chart with an external NGINX Ingress Controller
- Configure the GitLab chart with an external object storage
- Configure the GitLab chart with an external Redis
- Configure the GitLab chart with external GitLab Pages
- Configure the GitLab chart with FIPS-compliant images
- Configure the GitLab chart with GitLab Geo
- Configure the GitLab chart with Mattermost Team Edition
- Configure the GitLab chart with persistent volumes
- Configure the GitLab chart with UBI-based images
- Connecting a Kubernetes cluster with GitLab
- Contribute to development
- Corporate contributor license agreement
- Create a Civo Kubernetes cluster
- Create a Google GKE cluster
- Create an Amazon EKS cluster
- Create Kubernetes clusters
- Cron
- Decision Making
- Deprecations by version
- Design Decisions
- Developer Certificate of Origin Version 1.1
- Downgrading from EE to CE
- Features available to Starter and Bronze subscribers
- Find more tutorial content
- Generate test vulnerabilities
- Git concepts
- Gitaly and Geo capabilities
- Gitaly Cluster recovery options and tools
- GitLab CLI -
glab
- GitLab Data Seeder
- GitLab Dedicated
- GitLab Docs
- GitLab Docs
- GitLab Helm subcharts
- GitLab Mattermost
- GitLab release and maintenance policy
- GitLab Release CLI tool
- GitLab Runner Autoscaling
- GitLab Runner feature flags
- Goals
- GraphQL API Resources
- Group access and permissions
- Group access tokens
- Hardening - Application Recommendations
- Hardening - CI/CD Recommendations
- Hardening - Configuration Recommendations
- Hardening - General Concepts
- Hardening - Operating System Recommendations
- How to configure GitLab Runner for GitLab CE integration tests
- IAM roles for AWS when using the GitLab chart
- Individual contributor license agreement
- Install GitLab Runner Operator
- Interactive API documentation
- Internal Executor Interface
- Learn GitLab with tutorials
- Legal
- Make Docker-in-Docker builds faster with Docker layer caching
- Manage groups
- Managing Kubernetes secrets in a GitOps workflow
- Marketplace partners
- Migrate a Git repository into Git LFS with BFG
- Monitoring Gitaly and Gitaly Cluster
- Namespaces
- OpenShift support
- Organization
- Parallels
- Plan and operate a fleet of shared runners
- Processing specific job classes
- Project access tokens
- Publish packages with Yarn
- Reducing memory use
- Reference architecture
- Release CI/CD examples
- Release fields
- Removals by version
- Resource usage
- REST API deprecations and removals
- Reviewing GitLab Runner
- SaaS runners on Linux
- Set up macOS runners
- Set up standalone PostgreSQL database
- Setup standalone Gitaly
- Setup standalone Redis
- Supported package functionality
- The Customers Portal
- Timeline events
- Troubleshooting file export project migrations
- Troubleshooting groups
- Troubleshooting job artifacts
- Troubleshooting the GitLab agent for Kubernetes
- Troubleshooting the GitLab Container Registry
- Troubleshooting the Terraform integration with GitLab
- Tutorial Build, test, and deploy your Hugo site with GitLab
- Tutorial Create a complex pipeline
- Tutorial Make your first Git commit
- Tutorial Use GitLab to run an Agile iteration
- Tutorials Build your application
- Tutorials Develop with GitLab
- Tutorials Find your way around GitLab
- Tutorials Learn Git
- Tutorials Manage your infrastructure
- Tutorials Plan and track your work
- Tutorials Secure your application and check compliance
- Updating to GitLab 13.2 Email confirmation issues
- Use Auto DevOps to deploy to Amazon ECS
- Use Auto DevOps to deploy to EC2
- Use custom Docker images for the GitLab chart
- Use GitLab CI/CD to deploy to Heroku
- Use TLS between components of the GitLab chart
- View vulnerabilities in a pipeline
Edited by Suzanne Selhorn