Standardizing projects with custom blueprints in CodeCatalyst

You can standardize the development and best practices for your CodeCatalyst space's projects with custom blueprints. Custom blueprints can be used to define various aspects of a CodeCatalyst project, such as workflow definitions and application code. After a custom blueprint is used to create a new project or applied to existing projects, any changes to the blueprint are available to those projects as pull request updates. As a blueprint author, you can view details about which projects are using your blueprints throughout your space, so you can see how standards are being applied across projects. Lifecycle mangement of a blueprint allows you to centrally manage the software development lifecycle of every project, giving you ability to make sure the projects in your space continue to follow best practices with the latest changes or fixes. For more information, see Working with lifecycle management as a blueprint author.

Custom blueprints provide the ability to update blueprint versions against the prior project through resynthesis. Resynthesis is the process of rerunning blueprint synthesis with updated versions or the ability to incorporate fixes and changes into existing projects. For more information, see Custom blueprints concepts.

You may already have standardization and best practices in place. Instead of creating and developing a custom blueprint from scratch, you can choose to convert an existing source repository with source code into a custom blueprint. For more information, see Converting source repositories to custom blueprints.

To view the blueprints SDK and sample blueprints, see the open-source GitHub repository.