Merge pull request #1 from taoyong-ty/main

Add the initial set of starter templates

Author: taoyong-ty

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1 @@
+By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

.github/workflows/validate-templates.yaml

@@ -0,0 +1,21 @@
+name: Validate Templates
+
+on: [pull_request, push]
+
+jobs:
+  validate-templates:
+    permissions:
+      contents: read
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-node@v4
+        with:
+          node-version: 22
+      - run: npm ci
+      - run: npm run test
+      - uses: actions/setup-python@v5
+        with:
+          python-version: '3.13'
+      - run: pip install -U cfn-lint
+      - run: cfn-lint templates/cloudformation/* --non-zero-exit-code warning

.gitignore

@@ -0,0 +1,5 @@
+/node_modules
+/build
+/dist
+/coverage
+/generated-metadata

.npmignore

@@ -0,0 +1,4 @@
+/node_modules
+/build
+/dist
+/coverage

README.md

@@ -1,11 +1,57 @@
-## My Project
+# CodePipeline Starter Templates
 
-TODO: Fill this README out!
+This repository contains a collection of starter templates for AWS CodePipeline, designed to help users quickly set up and configure their CI/CD pipelines for various project types and deployment scenarios.
 
-Be sure to:
+## Repository Structure
 
-* Change the title in this README
-* Edit your repository description on GitHub
+- `/templates`: Contains the main components of the starter templates
+  - `/metadata`: JSON files describing each template. These files control how templates are rendered in the CodePipeline console. For more details on the schema and usage, refer to the [metadata README](templates/metadata/README.md).
+  - `/cloudformation`: CloudFormation templates for each pipeline configuration.
+  - `/ui-hints`: JSON files controlling the rendering of template configuration in the CodePipeline console. These files define how the template configuration step is displayed. For more information on the schema and usage, refer to the [UI hints README](templates/ui-hints/README.md).
+- `assets`: Contains svg icons for the starter templates 
+
+
+## Development
+
+This project uses Node.js for development tasks. To set up the development environment:
+
+1. Ensure you have Node.js 18 or later installed
+2. Run `npm install` to install dependencies
+
+### Adding new templates
+
+To add a new template, follow these steps:
+
+1. Create a new metadata file for the template in the `/templates/metadata` folder. This file should conform to the schema defined in `/templates/metadata/schema.json`.
+2. Add the corresponding CloudFormation template file in the `/templates/cloudformation` folder.
+3. The build script will automatically validate the metadata and CloudFormation template files, and generate the synthesized files for the CodePipeline Console to render.
+
+### Adding new icons
+ 
+You are not required to add a new icon for your template. You can use the existing `codepipeline.svg` icon located in the `assets/icons/` folder. 
+
+If you want to add a new icon to this package,
+1. Add the SVG file to the `assets/icons/` folder in this project.
+2. The icon-name in the metadata should correspond to the relevant folder, for example, `icon-name: lambda` expects an icon file at `asset/icons/lambda.svg`.
+
+
+### Testing your changes
+
+Our [template validation workflow](.github/workflows/validate-templates.yaml) involves JSON schema validation using npm and CloudFormation linting using [cfn-lint](https://github.com/aws-cloudformation/cfn-lint). To test your changes locally:
+
+1. Ensure you have npm and cfn-lint installed on your system.
+2. Run the following command to validate the JSON files:
+   ```
+   npm run test
+   ```
+3. Run the following command to validate the CloudFormation files:
+   ```
+   cfn-lint templates/cloudformation/*
+   ```
+
+## Contributing
+
+We welcome contributions to this project. Please read our [Contributing Guidelines](CONTRIBUTING.md) for more information on how to add new templates or improve existing ones.
 
 ## Security