Boilerplates

Overview

The Crystallize Legacy Boilerplates is a collection of pre-made boilerplates for the Crystallize platform. These boilerplates simplify the development process by providing ready-to-use templates for various components and functionalities. The goal of this collection is to centralize all the legacy boilerplates in one place to facilitate maintenance and encourage community contributions through open discussions, issue reporting, and pull requests.

Features

• Managed Repositories: All the legacy boilerplates are managed in this Git repository, making it easier to maintain and contribute.
• Centralized Contributions: Issues and pull requests for the boilerplates are open on this repository, allowing for centralized discussions and contributions.
• Shared Components: The boilerplates share common elements such as coding standards, CI & Automations, and tests.
• Independence of Components: Despite being centralized, each individual component (boilerplate) still maintains its independence and is pushed to its own repository.

Installation

To install a specific boilerplate from the Crystallize Legacy Boilerplates collection, follow these steps:

1. Create a new Github sub-repository for the desired component.
2. Add an entry in the components/manifest.json file to include the new boilerplate.
3. Clone the repository of the chosen boilerplate using the git clone command.
4. Follow the specific installation instructions provided in the repository’s documentation to set up the boilerplate in your development environment.
5. Start implementing your customized solution based on the selected boilerplate.

Summary

The Crystallize Legacy Boilerplates collection offers a centralized repository for managing and maintaining pre-made boilerplates for the Crystallize platform. These boilerplates provide developers with a head start by offering ready-to-use templates for various components and functionalities. Contributions to the boilerplates can be made through open discussions, issue reporting, and pull requests on the centralized repository. Despite being centralized, each individual component in the collection maintains its independence and is pushed to its own repository.