Thanks for your interest in contributing to 8bitcn.com. We're happy to have you here.
Please take a moment to review this document before submitting your first pull request. We also strongly recommend that you check for open issues and pull requests to see if someone else is working on something similar.
If you need any help, feel free to reach out to @orcdev, or to OrcDev Discord Channel.
- We use pnpm for development.
| Path | Description |
|---|---|
/app |
The Next.js application for the website. |
/components |
The React components for the website. |
/registry.json |
The registry for the components. |
You can fork this repo by clicking the fork button in the top right corner of this page.
git clone https://github.com/your-username/8bitcn.gitcd 8bitcngit checkout -b my-new-branchpnpm i- To run the
8bitcn.comwebsite:
pnpm devWe use a registry system for developing components. You can find the source code for the components under app/components/ui/8bit.
app
└── components
└── ui
├── 8bit
├── badge
└── buttonWhen adding or modifying components, please ensure that:
- You make the changes for every style.
- You update the documentation.
- You update the
registry.jsonfile with your component's metadata.
Before you create a Pull Request, please check whether your commits comply with the commit conventions used in this repository.
When you create a commit we kindly ask you to follow the convention
category(scope or module): message in your commit message while using one of
the following categories:
-
feat / feature: all changes that introduce completely new code or new features -
fix: changes that fix a bug (ideally you will additionally reference an issue if present) -
refactor: any code related change that is not a fix nor a feature -
docs: changing existing or creating new documentation (i.e. README, docs for usage of a lib or cli usage) -
build: all changes regarding the build of the software, changes to dependencies or the addition of new dependencies -
test: all changes regarding tests (adding new tests or changing existing ones) -
ci: all changes regarding the configuration of continuous integration (i.e. github actions, ci system) -
chore: all changes to the repository that do not fit into any of the above categoriese.g.
feat(components): add new prop to the avatar component
If you are interested in the detailed specification you can visit https://www.conventionalcommits.org/ or check out the Angular Commit Message Guidelines.
If you have a request for a new component, please open a discussion on GitHub. We'll be happy to help you out.