Skip to content

docs: slim README, split per-unit docs into docs/ - #38

Merged
domengabrovsek merged 1 commit into
mainfrom
docs/restructure-readme
Aug 9, 2026
Merged

docs: slim README, split per-unit docs into docs/#38
domengabrovsek merged 1 commit into
mainfrom
docs/restructure-readme

Conversation

@domengabrovsek

Copy link
Copy Markdown
Owner

What

The README was a 396-line wall documenting every action and workflow inline. This replaces it with a short overview and moves the detail into one doc per unit.

Changes

  • README trimmed 396 -> 69 lines: what the repo is, the @main referencing / central-pinning model, a composite actions table, a reusable workflows table, and a single Telegram notifications quick start. Everything else links out.
  • docs/actions/ - one reference doc each for setup-node-npm, checkout, aws-credentials, setup-opentofu (purpose, usage, inputs table, notes).
  • docs/workflows/ - one doc each for node-ci, security-scan, cloudflare-pages-deploy, and notifications (the notifications doc folds together the router, the telegram-notify formatter, and all pr-* / ci-status handlers).
  • Repo description updated on GitHub (was Telegram-only) to reflect the actions + CI/deploy + notifications scope.

Verification

  • All relative markdown links resolve to existing files.
  • No em-dashes or hook-blocked words in the new docs.

The README was a 396-line wall covering every action and workflow inline.
Replace it with a short overview plus two tables (composite actions,
reusable workflows) that link to a dedicated doc per unit under docs/.

- add docs/actions/{setup-node-npm,checkout,aws-credentials,setup-opentofu}.md
- add docs/workflows/{node-ci,security-scan,cloudflare-pages-deploy,notifications}.md
- notifications doc folds the router, formatter, and all pr-* handlers together
@domengabrovsek
domengabrovsek merged commit d0bf4c8 into main Aug 9, 2026
10 checks passed
@domengabrovsek
domengabrovsek deleted the docs/restructure-readme branch August 9, 2026 10:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant