From 37d1b7da762c3ac0b55b456b2d34e73204d21b8f Mon Sep 17 00:00:00 2001 From: Sebastian Enns Date: Thu, 1 Oct 2026 11:52:32 +0200 Subject: [PATCH] docs(sushi): remove stale project documentation --- GUIDELINES.md | 12 ------------ TODO.md | 16 ---------------- 2 files changed, 28 deletions(-) delete mode 100644 GUIDELINES.md delete mode 100644 TODO.md diff --git a/GUIDELINES.md b/GUIDELINES.md deleted file mode 100644 index 9c0bbe4..0000000 --- a/GUIDELINES.md +++ /dev/null @@ -1,12 +0,0 @@ -# Sushi engineering guide - -The project conventions are split by task so contributors can find the binding rules quickly: - -- [Create or change a component](docs/component-development.md) -- [Component styling](docs/component-styling.md) -- [Coding conventions](docs/coding-conventions.md) -- [Testing conventions](docs/testing-conventions.md) -- [AI conventions](docs/ai-conventions.md) -- [Contribution workflow](CONTRIBUTING.md) - -These documents form one engineering policy. A component is complete only when its consumer API, accessibility, theming, examples, source documentation, meaningful tests, generated references, and package output agree. diff --git a/TODO.md b/TODO.md deleted file mode 100644 index 786b32d..0000000 --- a/TODO.md +++ /dev/null @@ -1,16 +0,0 @@ -# Release tasks - -- [ ] Transfer the repository to `ramen-suite/sushi-angular` and update local Git remotes. -- [ ] Confirm publish access for the public npm scope `@sushi-kit`. -- [ ] Choose the initial package version and npm dist-tag. -- [ ] Define the versioning and changelog process. -- [ ] Confirm the supported Node.js and npm versions. -- [ ] Configure the CI and release workflow. -- [ ] Run `npm run verify` from a clean checkout. -- [ ] Run the isolated package-install smoke test in CI; extend it with browser checks for overlays before release. -- [ ] Generate and validate third-party license notices. -- [ ] Configure npm authentication, public access, provenance, and release permissions. -- [ ] Publish `@sushi-kit/angular` from the verified commit. -- [ ] Create the matching Git tag and release. -- [ ] Install the published version from npm and repeat the package smoke test. -- [ ] Configure deployment for the playground documentation.