Skip to content
This repository was archived by the owner on Mar 3, 2025. It is now read-only.
This repository was archived by the owner on Mar 3, 2025. It is now read-only.

Implement Multi-Repository Documentation Aggregation #120

Description

@johnx25bd

Description:

We need a way to consolidate documentation from multiple repositories (SDK, API, Location Proof Protocol, etc.) into a single Docusaurus-powered site. Each repository should maintain its own independent documentation while ensuring that all docs appear on a shared site under relevant subpages (e.g., /sdk/, /api/, etc).

Requirements

  • Each repository should store its own documentation in a /docs/ directory.
  • The main Docusaurus site should serve as the entry point and pull in documentation from multiple repositories.
  • Updates to documentation in any repository should be reflected automatically or via a scheduled sync.
  • The solution should not require significant manual intervention after initial setup.
  • The existing Docusaurus setup should be maintained as much as possible.

Proposed Approach

  1. Folder Structure

    • The main Docusaurus repo will maintain a /docs/ directory with subfolders for each component (/docs/sdk/, /docs/api/, etc).
    • Sidebar and navigation should be structured to reflect this hierarchy.
  2. Syncing Documentation

    • Set up a process (manual or automated) to fetch documentation from each repository and place it in the appropriate subfolder.
    • Possible approaches:
      • Git submodules
      • CI/CD pipeline that periodically pulls in updates
      • A lightweight script that syncs and commits changes
  3. Deployment

    • Ensure updates from all repositories are incorporated into the Docusaurus site before deployment.
    • Optionally, use GitHub Actions or another CI/CD tool to automate syncing and deployment.

Next Steps

  • Define the best approach for syncing documentation.
  • Set up an initial prototype for review.
  • Adjust Docusaurus configuration to handle multi-repo documentation.

I would love feedback before finalizing an implementation plan.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions