Optimize Getting Started learning experience - #336
Merged
Merged
Conversation
README.md tells readers to cite the Zenodo concept DOI, but CITATION.cff carried no DOI at all, so GitHub's "Cite this repository" output and every APA or BibTeX export produced from that file omitted the one identifier the README asks people to use. The CFF formatters behind that output read the top-level doi key only and never fall back to identifiers, so the concept DOI goes there. It is also the value that does not go stale: it resolves to the latest archived version and matches both the README text and the badge. The identifiers list then records the concept and version DOIs separately with descriptions, keeping the distinction the README teaches visible in the metadata itself. The two entries under references are the AsiBackbone and NetCoreApplicationTemplate repositories, which .zenodo.json already related by DOI. They now carry those same DOIs, so the citation graph is the same whether it is read from CITATION.cff or from the Zenodo deposit. .zenodo.json declared its three DOI relations as scheme "url" with doi.org URLs. Zenodo normalizes these on ingest, so the published record already stores them as bare DOIs with scheme "doi"; this is a correction to the source file rather than to the deposit, removing a discrepancy between what the repository declares and what Zenodo actually holds. ROADMAP's ongoing-maintenance item now names the version DOI alongside the version and date, and records that the deposit mints it after the release. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
…eed link relative
`publish-docs.yml` runs `tools/validate-doc-metadata.cs` but did not list it
among the `tools/*.cs` path filters, so a change to that validator alone could
not republish the site. `docs-validation.yml` already lists it; add it here too.
The RSS autodiscovery link and the footer subscribe link hard-coded
`/Learning/feed.xml`, which 404s at the `localhost:8080` preview CONTRIBUTING.md
tells contributors to use. Render both with `{{_rel}}feed.xml` instead. Because
`_appFooter` is interpolated as raw HTML and is never re-parsed as a template,
the footer markup moves from `docfx.json` global metadata into the local
`_master.tmpl` override, and the template's header comment records the added
reason for the override.
`validate-doc-metadata.cs` now resolves the autodiscovery href against the
page's own canonical URL, so it still proves every page points at the published
feed while accepting the depth-correct relative form.
Fixes #267
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Adds docs/articles/2026/your-audit-log-is-not-evidence.md, a standalone article arguing that a log line written after an operation narrates an outcome rather than establishing what was decided. The article works through four failures: the record captures the outcome instead of the decision and its inputs, nothing binds the record to the operation it describes, the record is written after the protected effect, and integrity ends at whatever the log sink provides. It closes with record-focused tests, explicit guidance on when an ordinary structured log is the right answer, and a review checklist. Registers the article in docs/articles/toc.yml and docs/articles/index.md following the existing newest-first ordering and permanent year/slug URL convention. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
…into issue_work
Enable and document the desired repository security posture for Learning, including Dependabot security updates, secret scanning, push protection, and an explicit main-branch ruleset. Preserve required documentation, link, sample, and CodeQL checks while requiring squash-only linear history, stale-review dismissal, resolved review threads, and a pull-request-only emergency bypass. Closes #287
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.
Summary
Optimizes the
docs/getting-startedexperience to make ASI Backbone Learning easier to navigate, scan, and evaluate without changing the underlying architectural guidance.This update restructures the primary Getting Started pages around clearer entry points, shorter decision paths, and more consistent learning patterns while preserving the existing DocFX-compatible Markdown structure and destination links.
Changes
Optimized
docs/getting-started/index.mdOptimized
docs/getting-started/adoption-personas-and-entry-points.mdOptimized
docs/getting-started/find-your-path.mdOptimized
docs/getting-started/learning-model.mdOptimized
docs/getting-started/learning-path-map.mdDesign Goals
Fix
Find Your Pathlink to reference the renamedFive-Part Foundationheading ingetting-started/index.md.InvalidBookmarkwarning that was treated as an error by the documentation build.Validation
git apply --check.git diff --checkpassed for each change.docs/getting-startedwere modified.