Skip to content

netboxlabs/console-docs

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 

Repository files navigation

NetBox Enterprise Documentation Repository

This repository contains the commercial/enterprise documentation for NetBox Labs products. The documentation is integrated with the main NetBox Labs documentation site at https://netboxlabs.com/docs.

πŸš€ Quick Start - Writing Documentation

1. Clone and Setup

git clone https://github.com/netboxlabs/console-docs
cd console-docs

2. Install Dependencies

# Using Python virtual environment (recommended)
python3 -m venv venv
source venv/bin/activate
pip install -r requirements.txt

# Or using global Python (if you have permission issues)
/Users/[username]/Library/Python/3.9/bin/mkdocs serve

3. Start Local Preview

mkdocs serve
# Visit: http://127.0.0.1:8000

4. Write Your Documentation

  • Create or edit .md files in the docs/ directory
  • Use proper semantic tagging in frontmatter (see Tagging Guide)
  • Test locally before committing

5. Submit Your Changes

git checkout -b feature/your-feature-name
git add docs/your-new-file.md
git commit -m "Add documentation for your feature"
git push origin feature/your-feature-name
# Create a pull request on GitHub

πŸ”„ How Documentation Goes Live (Two-Step Process)

Important: Documentation requires two separate pull requests to go live:

Step 1: Content Repository (This Repo)

  1. Create PR in this repository (console-docs)
  2. Get it reviewed and merged
  3. Tag the version (for production releases)

Step 2: Integration Repository

  1. Create PR in netboxlabs-website-dochub
  2. Update integration configuration to include your new content
  3. Get it reviewed and merged

Why Two Steps?

  • console-docs (this repo) β†’ Contains the actual documentation content
  • netboxlabs-website-dochub β†’ Combines content from multiple repos and publishes to the live site
  • Integration required β†’ Changes here don't automatically appear on the live site

Repository Integration Flow

graph LR
    A[console-docs<br/>πŸ“ Your Content] --> B[dochub<br/>πŸ”§ Integration Site]
    C[netbox repo<br/>πŸ“š Community Docs] --> B
    D[Other Repos<br/>πŸ“– Additional Content] --> B
    B --> E[netboxlabs.com/docs<br/>🌐 Live Site]
    
    style A fill:#e1f5fe
    style B fill:#fff3e0
    style E fill:#e8f5e8
Loading

Key Points:

  • πŸ”’ Content stays hidden until both PRs are merged
  • 🏷️ Version tags control what customers see
  • πŸ”„ Two-repo process ensures content quality and integration

πŸ“ Documentation Standards

Required Frontmatter

Every documentation file should include proper frontmatter with semantic tags:

---
tags:
  - cloud                    # Edition (NetBox Cloud, Enterprise, Community)
  - enterprise
  - discovery                # Product (discovery, assurance, operator, etc.)
  - getting-started          # Content type (installation, configuration, etc.)
title: "Your Document Title"
description: "SEO-friendly description"
author: "NetBox Labs Documentation Team"
last_updated: "2025-01-27"
---

Edition Tags (Choose Appropriate Ones)

tags:
  - cloud      # NetBox Cloud features
  - enterprise # NetBox Enterprise features  
  - community  # NetBox Community (open source) features
  - airgap     # Air-gapped deployment features

Product Tags

tags:
  - netbox     # Core NetBox functionality
  - discovery  # NetBox Discovery features
  - assurance  # NetBox Assurance features (premium only)
  - operator   # NetBox Operator features (premium only)
  - branching  # NetBox Branching extension (premium only)

Content Type Tags

tags:
  - installation     # Installation and setup guides
  - configuration    # Configuration and settings
  - troubleshooting  # Problem resolution guides
  - getting-started  # Introductory guides
  - administration   # System administration
  - api             # API documentation
  - authentication  # SSO, security, access control

πŸ“ Repository Structure

console-docs/
β”œβ”€β”€ docs/                           # πŸ“ Documentation content
β”‚   β”œβ”€β”€ administration-console/     # NetBox Cloud admin features
β”‚   β”œβ”€β”€ cloud-connectivity/         # Cloud connectivity guides
β”‚   β”œβ”€β”€ netbox-assurance/          # NetBox Assurance documentation
β”‚   β”œβ”€β”€ netbox-discovery/          # NetBox Discovery documentation
β”‚   β”œβ”€β”€ netbox-enterprise/         # NetBox Enterprise guides
β”‚   β”œβ”€β”€ netbox-extensions/         # Extensions and add-ons
β”‚   └── netbox-integrations/       # Third-party integrations
β”œβ”€β”€ ai-reference/                   # πŸ€– AI development resources
β”œβ”€β”€ mkdocs.yml                      # πŸ”§ Local development configuration
β”œβ”€β”€ versions.json                   # πŸ“‹ Version control configuration
└── README.md                       # πŸ“– This file

🎯 Version Management

Current Version Structure

Version Status Branch Customer Visibility Purpose
v1.10 🟒 Current main βœ… Visible Current customer documentation
v1.9 πŸ”΅ Stable v1.9 βœ… Visible Maintenance for existing customers
v1.11 🟑 Beta v1.11 ❌ Hidden NetBox Enterprise + Helm features
v1.12 πŸ”΄ Alpha v1.12 ❌ Hidden NetBox Enterprise + HA features

Where to Add Your Documentation

βœ… For Current Features (Immediate Visibility)

git checkout main  # v1.10 content - goes live immediately
# Edit documentation for current features
git add docs/path/to/file.md
git commit -m "Update SSL certificate installation steps"
git push origin main
# After PR merge + dochub integration β†’ Live on website

πŸ”„ For Future Features (Hidden Until Release)

git checkout -b feature/new-feature
# Add documentation for future features
git add docs/netbox-assurance/new-feature.md
git commit -m "Add documentation for upcoming feature"
git push origin feature/new-feature
# Stays hidden until feature branch is merged to a live version

🏷️ Semantic Tagging System

This repository uses a comprehensive semantic tagging system for intelligent content organization:

Click to expand complete tagging reference

Technical Category Tags (38+ Available)

tags:
  # Authentication & Security
  - authentication # SSO, security, access control
  - sso           # Single sign-on features
  - ldap          # LDAP integration
  - saml          # SAML authentication
  - rbac          # Role-based access control
  - security      # Security features
  - encryption    # Encryption and certificates
  
  # System Administration
  - administration # System administration
  - database      # Database management
  - backup        # Backup and restore
  - migration     # Data migration
  - upgrade       # Version upgrades
  - maintenance   # System maintenance
  
  # APIs and Integration
  - api           # REST API, GraphQL, SDKs
  - rest-api      # REST API specific
  - graphql       # GraphQL API
  - webhooks      # Webhook integrations
  - automation    # Automation and scripting
  - plugins       # Plugin development
  
  # Operations and Monitoring
  - operations    # Monitoring, backups, maintenance
  - monitoring    # System monitoring
  - notifications # Alerts and notifications
  - logging       # Logging and audit trails
  - metrics       # Performance metrics

NetBox Model Categories

tags:
  - circuits        # Circuit providers and connectivity
  - dcim           # Data Center Infrastructure Management
  - ipam           # IP Address Management
  - tenancy        # Multi-tenancy features
  - virtualization # Virtual machines and clusters
  - vpn            # VPN tunnels and configurations
  - wireless       # Wireless networks
  - extras         # Custom fields, webhooks, templates
  - core           # Core NetBox functionality

πŸ€– AI-Assisted Development

This repository includes comprehensive AI reference materials in the ai-reference/ directory:

AI Reference Resources

ai-reference/
β”œβ”€β”€ README.md                           # Complete AI reference guide
β”œβ”€β”€ QUICK_REFERENCE.md                  # Fast lookup for common tasks
β”œβ”€β”€ templates/                          # Document templates
β”‚   β”œβ”€β”€ netbox-feature-doc-template.md  # Standard feature documentation
β”‚   └── product-landing-page.md         # Product overview template
β”œβ”€β”€ style-guides/                       # Writing guidelines
β”‚   β”œβ”€β”€ netbox-docs-style-guide.md      # Complete style guide
β”‚   └── product-tagging-guide.md        # Tagging system guide
└── content-strategy/                   # Strategy and planning
    └── navigation-strategy.md          # User-centric navigation

Using AI Reference Materials

When working with AI tools:

  1. Reference the style guide: ai-reference/style-guides/netbox-docs-style-guide.md
  2. Use templates: ai-reference/templates/
  3. Apply proper tagging: ai-reference/style-guides/product-tagging-guide.md

πŸ“¦ External Documentation Sync

Some documentation is synced from external repositories:

Path Repository Purpose Update Method
docs/netbox-extensions/changes/ netbox-changes NetBox Change Management docs Script-based sync

Updating External Documentation

# For maintainers only
./scripts/update-changes-docs.sh
git add docs/netbox-extensions/changes/
git commit -m "Update NetBox Changes documentation"
git push

πŸ“‹ Important Guidelines

βœ… DO:

  • Use proper semantic tagging in all documents
  • Test locally before committing
  • Create feature branches for new content
  • Follow the two-step process for live deployment
  • Reference AI templates when writing

❌ DON'T:

  • Don't commit directly to main without review
  • Don't forget frontmatter tags in your documents
  • Don't assume changes go live automatically (requires dochub integration)
  • Don't merge unreleased features into live branches

πŸ› οΈ Advanced Configuration

Click to expand advanced technical details

Version Configuration Management

Version visibility is controlled by versions.json:

{
  "versions": [
    {
      "version": "v1.10", 
      "branch": "main",
      "title": "v1.10 (Current)",
      "default": true,
      "status": "current"
    }
  ],
  "future_versions": [
    {
      "version": "v1.11",
      "branch": "v1.11",
      "title": "v1.11 (Beta) - NetBox Enterprise with Helm",
      "status": "beta"
    }
  ]
}

Integration with Dochub

The repository sends webhook notifications to netboxlabs-website-dochub when versions are deployed. The semantic tagging system enables:

  • Content Filtering: Edition-specific content visibility
  • Navigation Generation: Automatic sidebar generation
  • Search Enhancement: Tag-based search and filtering
  • Cross-Product Discovery: Related content recommendations

Automated Deployment Process

# Tagging triggers automatic deployment
git tag v1.10.1
git push origin v1.10.1
# β†’ Triggers GitHub Actions β†’ Notifies dochub β†’ Updates live site

⚠️ Troubleshooting

If you see errors like this:

ERROR - Config value 'theme': Unrecognised theme name: 'material' ERROR - ModuleNotFoundError: No module named 'pymdownx'

Solution: Try uninstalling mkdocs from your package manager (e.g. brew uninstall mkdocs) and use only the pip-installed version. MkDocs doesn't work well when installed via multiple methods.

πŸ†˜ Getting Help

  • Community Support: Join Slack in the #netbox channel
  • Documentation Issues: Create an issue in this repository
  • Integration Questions: Ask in the netboxlabs-website-dochub repository

Ready to contribute? Start with the Quick Start section above and remember the two-step process for going live!

About

NetBox Cloud documentation

Topics

Resources

Stars

Watchers

Forks

Packages

No packages published

Contributors 18