Master this essential documentation concept
Prefixes added to a main domain name to create separate sections of a website, often used for organizing different types of content
Subdomains serve as powerful organizational tools that enable documentation teams to create distinct, purpose-driven sections of their web presence while maintaining connection to the main brand domain. By adding prefixes like 'docs', 'api', or 'help' before the primary domain, teams can establish clear content boundaries and user expectations.
When restructuring your website with subdomains to separate product areas, support portals, or developer resources, your team likely creates training videos explaining the architecture decisions and implementation details. These videos capture valuable context about why specific subdomains were created and how content should be organized across them.
However, when this knowledge remains trapped in hour-long architecture meetings or training sessions, new team members struggle to quickly understand your subdomain strategy. Finding the exact moment when someone explains which content belongs on which subdomain becomes a frustrating exercise of scrubbing through video timelines.
By converting these video discussions into structured documentation, you create searchable references that clearly outline your subdomain architecture. Technical writers can extract specific guidelines about subdomain naming conventions, content organization principles, and governance rules. This documentation becomes particularly valuable during content migrations or when onboarding new contributors who need to understand where their content belongs in your subdomain hierarchy.
Documentation derived from video discussions also helps maintain consistency in how subdomains are referenced across your technical documentation, ensuring teams use the correct terminology when referring to different sections of your site.
A company with multiple products struggles with users finding relevant documentation, leading to confusion and support tickets when all content is mixed together on a single domain.
Create dedicated subdomains for each product (product1.docs.company.com, product2.docs.company.com) to provide focused, product-specific documentation experiences.
1. Audit existing content and categorize by product 2. Set up DNS records for each product subdomain 3. Configure separate documentation platforms or sections 4. Migrate content to appropriate subdomains 5. Implement cross-linking between related products 6. Update navigation and search to be product-focused
Users find relevant information 60% faster, support tickets decrease by 40%, and each product team can independently manage their documentation lifecycle.
Technical API documentation overwhelms end-users while simplified user guides frustrate developers, creating poor experiences for both audiences.
Establish api.company.com for technical documentation and help.company.com for end-user support, each optimized for their specific audience needs.
1. Analyze user personas and content consumption patterns 2. Categorize existing content by technical complexity 3. Design distinct user interfaces for each audience 4. Set up specialized tools (API docs platform vs help center) 5. Create audience-specific navigation and search 6. Implement targeted onboarding flows
Developer satisfaction increases by 45% due to comprehensive technical resources, while end-user task completion improves by 35% through simplified guidance.
Documentation updates risk breaking live user experiences, and there's no safe way to preview changes or test new content structures before publication.
Use staging.docs.company.com for content development and testing, with docs.company.com serving as the stable production environment.
1. Mirror production environment setup on staging subdomain 2. Implement content synchronization workflows 3. Create review and approval processes 4. Set up automated testing for links and formatting 5. Establish deployment pipelines between environments 6. Configure access controls for internal team review
Content quality improves with 90% fewer broken links or formatting issues, and teams can safely experiment with new content structures without user impact.
International users struggle with English-only documentation, but managing multiple languages on a single domain creates complexity in content organization and maintenance.
Deploy language-specific subdomains (es.docs.company.com, de.docs.company.com) to provide native-language experiences with appropriate cultural adaptations.
1. Identify priority markets and languages 2. Set up subdomains with proper hreflang configuration 3. Implement translation management workflows 4. Create region-specific content strategies 5. Configure localized search and navigation 6. Establish maintenance processes for multilingual content
International user engagement increases by 70%, translation management becomes streamlined, and local teams can adapt content for cultural relevance.
Choose subdomain names that immediately communicate their purpose and content type to users, making navigation predictable and professional.
Maintain visual and functional consistency across subdomains while allowing each to serve its specific purpose effectively.
Set up comprehensive tracking and monitoring for each subdomain to understand user behavior and maintain performance standards.
Develop a strategic approach to moving content to subdomains that preserves SEO value and user bookmarks while improving organization.
Define which teams or individuals are responsible for each subdomain's content, technical maintenance, and user experience.
Join thousands of teams creating outstanding documentation
Start Free Trial