docs+ci: onramp overhaul — value-prop README, no-code contributor track, CI#223
Open
CPAtoCybersecurity wants to merge 4 commits into
Open
docs+ci: onramp overhaul — value-prop README, no-code contributor track, CI#223CPAtoCybersecurity wants to merge 4 commits into
CPAtoCybersecurity wants to merge 4 commits into
Conversation
…oor router - H1 now names what the tool is; org attribution and version moved to About - Live demo link above the fold - Router table pointing to all five onramp folders - Disclaimer and credits moved below installation
- Two-track structure: no-code (test procedures, artifacts, case-study findings) and code - Step-by-step first contribution flow with claim protocol and model PR - Fix LICENSE relative link
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
1 participant
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
Wires the existing onramp to the front door, based on community feedback (Discord + first-contributor questions on #33/#48):
npm test+ build on PRs, plus a weekly Markdown link-check (the Jan folder renames silently broke links across 20+ issues; this prevents the class).Notes for in-flight PRs
Test plan