Boilerplate for Git Repositories
A boilerplate file structure to be used by Git-based projects. It contains most of the files expected to be inside CKEditor-related repositories.
The boilerplate is generic enough to be used by any project out there.
Currently there are two presets available:
- For projects using ECMAScript 5 – the
- For projects using ECMAScript 2015+ (ESNext) – the
- For CKEditor 5 repositories – the
The following section lists documentation-related files that should be available in the project.
All projects must have a
README.md file which replaces this one.
Includes the default license terms used by most CKEditor projects.
Describes the standard contribution process adopted for CKEditor projects.
A template for the changelog file.
The following section lists developer-targeted files that should be available in the project.
This is the Grunt configuration file. It exposes the following tasks:
grunt default– Alias for
grunt githooks– Installs a Git pre-commit hook to run
jshint:git variations run the checks on files that will end up in the next
git commit only. It's
therefore much faster.
All Grunt tasks are available inside the
The npm configuration file which describes the project and includes dependencies for Node tools used in the project.
EOL and content type rules for Git.
The list of paths to be ignored by Git. This file also sets the list of paths to be ignored by the
Unified configurations for IDEs. See editorconfig.org for more information.
Using This Repository
This repository can be used as a starting point for new projects or to bring existing projects to a common pattern. It helps to preserve uniformity across different projects.
The following steps assume that you are located inside your local clone of the target repository.
1. Enabling the Boilerplate in a Repository
git remote add boilerplate https://github.com/ckeditor/ckeditor-boilerplate.git
2. Injecting the Boilerplate into a Repository
git fetch boilerplate git merge boilerplate/master # or boilerplate/esnext
If any files are already present in your repository, there is a chance that the merge will cause conflicts. Generally it should be straightforward to resolve them.
3. Get Boilerplate Updates
Just repeat step 2.
First Steps after Including the Boilerplate
The boilerplate contains generic files, many of them serving as templates for your projects. The following are the things to do once you incorporate it into your project.
Reviewing file content:
README.md– Replace this file with the content that describes your project.
CONTRIBUTING.md– Ensure that the content of this file applies to your project.
- Replace the software name with your project name.
- Check if the license option fits your project.
- Ensure that the entire content of this file is appropriate for your project.
package.json– Fill all entries accordingly.
grunt are installed globally, run a few commands:
npm install– Downloads all project dependencies into
grunt githooks– (optional) If you want to have pre-commit linting enabled straight in your project.
Other than the files available in this repository, it is expected that target projects will also contain the following directories:
The source code of the project.
If any build is created, it should be placed in this folder.
The place for tests. Its final placement is per project. It can either stay in the project root or inside sub-directories that represent parts of the project, like modules or plugins.
Copyright (c) 2014 CKSource - Frederico Knabben
All boilerplate code is licensed under the terms of the MIT license.
LICENSE.md is available in this repository as a template for your project, it does not apply to the
boilerplate project itself.