To get started:
git clone git@github.com:tinacms/tinacms.git
cd tinacms
npm install && npm run bootstrap
npm run build
# Start Gatsby demo
cd packages/demo-gatsby
npm run startDo not run npm install from inside the packages directory
TinaCMS uses Lerna to manage dependencies when developing locally. This allows the various packages to reference each other via symlinks. Running npm install from within a package replaces the symlinks with references to the packages in the npm registry.
| Commands | Description |
|---|---|
| npm run bootstrap | Install dependencies and link local packages. |
| npm run build | Build all packages. |
| npm run watch | Watch all packages for rebuilds. |
| npm run test | Run tests for all packages. |
| lerna run build --scope <package> | Build only <package>. |
Tina has three main branches:
- master: The bleeding edge of tinacms
- next: A preview of the next release
- latest: The current stable release
The flow of changes therefore looks like:
fix-some-bug=>master=>next=>latest
This flow happens over a 2 week release process:
- Day 1: A new
nextbranch is created frommaster. - Week 1:
nextis kept up to date withmasterwith frequent pre-releases - Week 2:
nextis frozen for new development but critical bug fixes can be cherry picked. - Day 14:
nextis released to npm, and then merged intolatest