This is the respository for our website!
It's made in Next.js, a React framework by Vercel.
A big welcome and thank you for considering contributing to Tonomy! It is people like you that help shape the future where your identity is in your hands.
Reading and following these guidelines will help us make the contribution process easy and effective for everyone involved. It also communicates that you respect the time of the developers managing and developing these open source projects. In return, we will reciprocate this by adressing your issue, assessing changes and helping you finalize your pull requests.
- Getting Started
- Dependencies
- Run
- Feature branch policy
- Component picking
- Pull Requests
- Miscellaneous
- Template source
- Issues
- Getting Help
- Nodejs v16.4.1+
- Install packages with
npm i. - Run
npm run devto start the development server.
We work with a specific policy for making feature branches to contribute.
- Branches should be named feature/(task number)-(task name).
- If applicable, PRs of feature branches should be linked to the Zenhub task(s) using the browser extension.
Branch process:
master
\
| \
| | development
| \
| \
| | | feature/xxx
- Branch: master
- Deployed: https://tonomy.foundation
- Staging Branch: development
- Staging: https://staging-website.tonomy.foundation
Branch process:
id
\
| \
| | development-id
| \
| | \
| | | feature-id/yyy
- Branch: id
- Deployed: https://tonomy.io
- Staging Branch: development-id
- Staging: https://staging-website.tonomy.io
- Branch: template
- Deployed: https://tonomy-foundation-template.vercel.app
PRs are the best and quickest way to get your fix, improvement or feature merged. In general, PRs should:
- Only fix/add the functionality in the issue
- Address a single concern in the least number of changed lines as possible
- Be named 'feature/(issue number)-(task name)
This template is from Themeforest.
Issues should be used to report problems with the project, request a new feature, or to discuss potential changes before a PR is created.