Anotherkit
This is a starterkit for Kirby. It sets you up with Kirby 3.5+, TailwindCSS 2.0+ and AlpineJS.
Installation & setup
-
Start your new project with the following command:
composer create-project diverently/anotherkit yourprojectnameA new folder
yourprojectnamewill be created with Kirby already setup.: -
Next,
cdinto the newly created folder and run the following command:php ./configure.phpThis will run a script that will replace all placeholders throughout all the files.
-
After everything is installed, you can run
npm startand start coding.🎉
You can follow the Tailwind Docs for setting up your project specific configuration.
Change package.json
This starterkit includes the semantic-release package. To use it, you should change the repository in package.json. If you don't want to automatically version your repo, just remove the package by running npm uninstall semantic-release last-release-git and remove the release entry in package.json.
Semantic versioning
This starterkit uses semantic-release to automatically tag your commits. Here is an example of the release type that will be done based on a commit message (taken from their Readme):
| Commit message | Release type |
|---|---|
fix(pencil): stop graphite breaking when too much pressure applied |
Patch Release |
feat(pencil): add 'graphiteWidth' option |
|
perf(pencil): remove graphiteWidth optionBREAKING CHANGE: The graphiteWidth option has been removed.The default graphite width of 10mm is always used for performance reasons. |
semantic-release uses Angular Commit Message Conventions, so the type can be one of the following:
- build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
- ci: Changes to our CI configuration files and scripts (example scopes: Circle, BrowserStack, SauceLabs)
- docs: Documentation only changes
- feat: A new feature
- fix: A bug fix
- perf: A code change that improves performance
- refactor: A code change that neither fixes a bug nor adds a feature
- test: Adding missing tests or correcting existing tests
- chore: Changes that affect external dependencies for example