Organize docs into structured directory hierarchy with docs.json index #58
+1,170
−93
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
This commit addresses all tasks from Issue #21 by documenting the Project Board column setup requirements and creating comprehensive configuration instructions. Changes: - Updated PROJECT_BOARD_GUIDE.md with detailed Project #10 setup section - Added Quick Setup Checklist for board creation - Documented detailed automation rules for each column (Backlog, Planned, In Progress, Review, Done) - Added step-by-step automation configuration instructions - Created testing workflow to verify board setup - Enhanced automation section with visual table - Added manual card movement procedures - Created PROJECT_BOARD_VERIFICATION.md with complete verification report Findings: - Project #10 does not currently exist (404 response) - Column structure is well-defined and ready for implementation - All automation rules have been documented comprehensively - Setup checklist and testing procedures are now available Next Steps: - Organization admin needs to create the project board - Follow the setup checklist in PROJECT_BOARD_GUIDE.md - Run the documented test workflow to verify automation - Add screenshots after board creation https://claude.ai/code/session_01YBeh6jmBiCHJRCeVrMy6iG
Implements the DOCS_STRUCTURE_PROPOSAL.md reorganization: - Move 15 documentation files from root into docs/ subdirectories (governance/, planning/, operations/, business/, audit/, automation/) - Move scripts and labels.json into scripts/ directory - Create README.md index files for docs hub and each subdirectory - Create docs.json central documentation index with classification, ownership, and update cadence metadata per DOCUMENT_CLASSIFICATION_POLICY - Update all internal cross-references across 31+ files including workflows, issue templates, and moved documents - Update root README.md with documentation navigation section Root now contains only standard GitHub files (README, CONTRIBUTING, SECURITY, LICENSE, PR template) keeping it clean and navigable. https://claude.ai/code/session_014pmU63keycr2m1B1LnU2RZ
github-actions
bot
added
size: M
Documentation Freshness CheckMissing Documentation UpdatesPer DOCUMENT_CLASSIFICATION_POLICY.md, the following docs should be updated in this PR:
This check is enforced by DOCUMENT_CLASSIFICATION_POLICY.md Section 2.1 |
github-actions
bot
added
type: documentation
Fix template paths to match new docs/ directory layout and bump Last Updated date, satisfying DOCUMENT_CLASSIFICATION_POLICY Section 2.1 requirement that issue template changes include PROJECT_BOARD_GUIDE updates. https://claude.ai/code/session_014pmU63keycr2m1B1LnU2RZ
🏷️ Milestone & Task Label CheckThis PR has strategic labels but no milestone label (e.g., Available milestones:
Please add a milestone label and optionally a task label ( See MILESTONES_OVERVIEW.md for milestone details. This check is enforced by the milestone-task-enforcement workflow. |
🎯 Goal Alignment CheckThis PR is marked as strategic but doesn't explicitly mention alignment with current organizational goals. Current Goals for 2026 Q1:
Consider:
See GOALS.md for details. This is an automated check to ensure organizational alignment. |
Documentation Freshness CheckMissing Documentation UpdatesPer DOCUMENT_CLASSIFICATION_POLICY.md, the following docs should be updated in this PR:
This check is enforced by DOCUMENT_CLASSIFICATION_POLICY.md Section 2.1 |
…structure Resolves merge conflict between docs reorganization and Issue #21 (complete-issue-21-tasks) branch: Conflict: Issue #21 added Project #10 setup documentation to PROJECT_BOARD_GUIDE.md at root, while our branch moved that file to docs/operations/. Resolution keeps all Issue #21 content (164 lines of column config, automation rules, testing workflow) in the new docs/operations/ location with corrected relative links. Additional changes: - Move PROJECT_BOARD_VERIFICATION.md into docs/operations/ - Fix internal links in verification doc for new directory context - Add verification doc to docs.json index and operations README https://claude.ai/code/session_014pmU63keycr2m1B1LnU2RZ
🎯 Goal Alignment CheckThis PR is marked as strategic but doesn't explicitly mention alignment with current organizational goals. Current Goals for 2026 Q1:
Consider:
See GOALS.md for details. This is an automated check to ensure organizational alignment. |
Documentation Freshness CheckMissing Documentation UpdatesPer DOCUMENT_CLASSIFICATION_POLICY.md, the following docs should be updated in this PR:
This check is enforced by DOCUMENT_CLASSIFICATION_POLICY.md Section 2.1 |
Update hardcoded root-level file paths in both workflows to match the new docs/ directory structure. This was causing false positives on the freshness check (couldn't find PROJECT_BOARD_GUIDE.md at root since it moved to docs/operations/) and would cause the staleness audit to silently skip all moved documents. Changes: - doc-freshness-check.yml: Update livingDocs array and use .some(f => f.endsWith()) for flexible path matching on PR diffs - doc-staleness-audit.yml: Update docs array with full paths https://claude.ai/code/session_014pmU63keycr2m1B1LnU2RZ
🎯 Goal Alignment CheckThis PR is marked as strategic but doesn't explicitly mention alignment with current organizational goals. Current Goals for 2026 Q1:
Consider:
See GOALS.md for details. This is an automated check to ensure organizational alignment. |
Update the API path to fetch docs/planning/GOALS.md with fallback to the legacy root path for transition compatibility. Without this, the workflow would fail to load goal definitions after the docs reorganization merges to master. Goal 3: Establish Governance & Processes - this PR implements the approved docs structure proposal and document classification policy. https://claude.ai/code/session_014pmU63keycr2m1B1LnU2RZ
🎯 Goal Alignment CheckThis PR is marked as strategic but doesn't explicitly mention alignment with current organizational goals. Current Goals for 2026 Q1:
Consider:
See GOALS.md for details. This is an automated check to ensure organizational alignment. |
✅ Goal Alignment ConfirmedThis PR aligns with the following organizational goal(s):
Thank you for contributing to our strategic objectives! 🎉 Track progress: Strategic Goals & Initiatives Board |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Implements the DOCS_STRUCTURE_PROPOSAL.md reorganization:
(governance/, planning/, operations/, business/, audit/, automation/)
ownership, and update cadence metadata per DOCUMENT_CLASSIFICATION_POLICY
workflows, issue templates, and moved documents
Goal 3: Establish Governance & Processes - Implements the approved documentation structure proposal, organizing all documents per the Document Classification Policy and establishing the docs.json index for maintainability.
Root now contains only standard GitHub files (README, CONTRIBUTING,
SECURITY, LICENSE, PR template) keeping it clean and navigable.
https://claude.ai/code/session_014pmU63keycr2m1B1LnU2RZ