-
Notifications
You must be signed in to change notification settings - Fork 8
Docs reorg #135
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Docs reorg #135
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
add reference to forum
remove redundant content from getting-started
Add new organization to project docs Update PI references in project docs
Move useful info to federation.rst
Mark-Powers
approved these changes
May 27, 2025
Contributor
Mark-Powers
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall looks good. A few concerns
- The create issue link doesn't work for me. I submitted another PR we can merge into this in #136
- We'll have to corresponding update #124 to conform to this organization
- Can you check on the
.github/CODEOWNERSfile? It doesn't seem to be working. Ideally the users in the file are notified when an issue or PR is created based on that, which would be useful if users are submiting those.
Move create issue to footer template
Contributor
Author
|
@Mark-Powers is there any thing else? I am not sure what to do with the CODEOWNERS file. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Chameleon Documentation Reorganization Summary
Overview
This document summarizes all changes made in the
docs_reorgbranch to improve the structure, organization, and maintainability of the Chameleon Cloud documentation.Major Changes
1. Documentation Structure Reorganization
Technical Documentation Restructuring
The monolithic documentation files were split into modular directory structures with dedicated index pages:
launching_gui.rst,launching_cli.rst,interacting.rstinstallation.rst,authentication.rst,rc_script.rst,usage.rstcatalog.rst,gui_management.rst,cli_management.rst,heat_templates.rst,sharing.rst,advanced_topics.rsthardware_catalog.rst,rest_api.rstfeatures.rst,api_access.rst,navigation.rstsupported_images.rst,cc_snapshot.rst,gui_management.rst,cli_management.rstjupyter_collaboration.rst,jupyter_dedicated.rstkvm_gui.rst,kvm_lbaas.rst,kvm_cli.rstnetworks_basic.rst,networks_vlan.rst,networks_stitching.rst,networks_fabnet.rst,networks_jumbo_frames.rstindex.rstgui_reservations.rst,cli_reservations.rstconcepts.rst,gui_management.rst,cli_management.rst,mounting.rstbrowsing_artifacts.rst,packaging_artifacts.rst(Trovi)swift_gui.rst,swift_cli.rst,swift_mount.rstBackwards Compatibility
:orphan:directive and meta refresh tagsCross-Reference Updates
contents.rstandtechnical/index.rsttoctree directives2. Content Improvements
Technical Overview Updates
technical/index.rstGetting Started Guide
federation.rstUser Documentation
Home Page Refresh
3. Documentation Standards
Header Capitalization Standards
Established consistent header formatting across all documentation:
===): Title Case===): Title Case---,~~~,^^^): Sentence caseStructural Fixes
getting-started/index.rst4. User Experience Improvements
Feedback Channel
Fixed Issues
5. Content Cleanup
Impact Summary
Commit History
Key commits in chronological order:
822d6ff- Fix technical overview table of contents256bf12- Reorganize the documentation structurebada40d- Reorganize more technical documentation667191e- Update shares directory structureb0fbdaf- Implement feedback channel for documentationb489592- Fix content headings on technical pages94c8f5f- Standardize header names in documentation