Thanks for considering contributing to this project. There are a number of way you can help this project grow and improve:
- tell a friend
- propose a feature
- report a bug
- submit a fix
- improve the documentation
- add a localisation
- develop a plug-in
For this project to be a safe, welcoming space for collaboration, contributors must adhere to our code of conduct.
One of the best (and easiest) ways to grow this project is to tell people about it!
If you are using Indiekit, add yourself to the list of people using Indiekit on the IndieWeb wiki.
The motivation behind Indiekit is to build a tool that makes interacting with IndieWeb protocols and technologies accessible, adaptable and approachable. Indiekit also aims to be platform agnostic and built for the long term.
Features and improvements that move the project closer to these goals are strongly encouraged.
We use GitHub issues to track feature requests. Browse existing proposals before adding yours.
We use GitHub issues to track bugs. Browse existing reports before adding yours.
Commit messages for fixes should be prefixed with
fix:, for example:
fix: do not throw error for signed in users
If a fix affects a specific module, include the name of the module in the commit message, for example:
fix(endpoint-micropub): only return queried values
Documentation should be accessible, easy to read and avoid jargon.
Commit messages for documentation updates should be prefixed with
docs:, for example:
docs: fix typo in getting started instructions
Localazy is used to manage localisations. If you see a translation that is not quite right or would like to add a new language, create an account and contribute to the project.
You can use Indiekit’s plug-in API to add (or prototype) a new feature.
When publishing a plug-in to the npm registry, add the
indiekit-plugin keyword to help other Indiekit users find it. To have a plug-in listed in the plug-in directory, submit a pull request against the relevant page in the documentation.
This project uses a monorepo structure, with concerns split into separate Node modules located in the
|Coordinating functions and the Express web server.
|Frontend component library, used for the application interface.
|Error handling for the core module and plug-ins.
|Project initialiser, used when running
npm create indiekit.
|Application endpoint plug-ins.
|Publication preset plug-ins.
|Content store plug-ins.
Helper functions used in tests are in the
Indiekit uses the Express server framework.
Configuration defaults get merged with any user-defined values (Indiekit uses cosmiconfig to find and load a configuration object).
Plug-ins listed under the
plugins array are then loaded and interrogated for known API methods, which further update the configuration.
Express waits for a resolved configuration file before starting the server.
To run the server locally, first install its dependencies:
The provided configuration file allows some options to be assigned using environment variables.
.env file in the root of the project, for example:
# Database connection string URI (optional)
# Test saving files to a content store on GitHub (optional)
# Test syndicating content to a Mastodon server (optional)
You can then start the server:
To automatically restart the server whenever a file change is detected, use:
npm run dev
To enable authentication, use the
npm run dev --production
The project uses both unit and integration tests. Run tests using the following command:
To run an individual test, use
node followed by the path to the test. For example:
The project aims to achieve close to 100% test coverage. You can check code coverage by running the following command:
npm run test:coverage
You can check that any changes use the preferred code style by running the following command:
npm run lint
You automatically fix any issues by running the following command:
npm run lint:fix