backstage-plugins
A standalone monorepo for Backstage plugins published under the @estehsaan npm scope, following the same workspace pattern as backstage/community-plugins.
Packages
| Package | Version | Description |
|---|---|---|
@estehsaan/backstage-plugin-onboarding |
Frontend onboarding checklist plugin | |
@estehsaan/backstage-plugin-onboarding-backend |
Backend for the onboarding plugin | |
@estehsaan/backstage-plugin-onboarding-common |
Shared types and permissions |
Installation (for consumers)
# In your Backstage app
yarn --cwd packages/app add @estehsaan/backstage-plugin-onboarding
# In your Backstage backend
yarn --cwd packages/backend add @estehsaan/backstage-plugin-onboarding-backend
See CONTRIBUTING.md for full contribution and publishing instructions.
Repository Structure
workspaces/
onboarding/ # workspace root (independent yarn workspace)
plugins/
onboarding/ # @estehsaan/backstage-plugin-onboarding
onboarding-backend/ # @estehsaan/backstage-plugin-onboarding-backend
onboarding-common/ # @estehsaan/backstage-plugin-onboarding-common
package.json
Development
# Install all dependencies
yarn install
# Type check
yarn tsc
# Build all packages
yarn build:all
# Run the frontend plugin dev server
cd workspaces/onboarding/plugins/onboarding
yarn start
# Run tests
yarn test
Releasing
This repo uses semantic-release for automated versioning and publishing.
Commit conventions drive releases
Release type is inferred from Conventional Commit messages:
feat:triggers a minor releasefix:triggers a patch releasefeat!:or aBREAKING CHANGE:footer triggers a major releasedocs:,chore:,ci:,test:do not trigger a release
Automated publishing via GitHub Actions
- Open a PR with Conventional Commit-style commits
- Merge to
main - The Release workflow analyzes commits since the last release, bumps versions, publishes to npm, and updates release notes/changelog automatically
First-time setup: add an
NPM_TOKENsecret to GitHub Actions — see CONTRIBUTING.md#github-actions--npm_token.
Contributing
See CONTRIBUTING.md for commit conventions, branch naming, semantic-release workflow, and more.