Repository navigation
docs: organize public guides and preserve validation history - #34
Merged
Merged
Conversation
This was referenced Oct 20, 2026
rafatahmed
added a commit
that referenced
this pull request
Nov 7, 2026
docs: organize public guides and preserve validation history
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
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.
The public planning guides mixed usage instructions with internal milestones and dated development logs. Organize navigation into Get started, Growers and agronomists, User manual, API reference, Models and chemistry, Evidence and audits, and Changelog.
Detailed workflows now sit under the manual, schemas and units under the API reference, and source reviews and verification records under Evidence and audits. Remove milestone labels from navigation, clarify the measured-curve versus equilibrium pH workflows, and distinguish the three EC methods.
Preserve existing page URLs and affected section anchors. Relocate historical validation logs and superseded pH requirements without changing their original text; retain provenance, model limits, failed-run context, and distinctions between computational evidence and physical validation. Document the maintenance rules for this organization.
Validation:
Documentation only; no chemistry, runtime behavior, or scientific parameters changed.