> For the complete documentation index, see [llms.txt](https://docs.jigx.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jigx.com/getting-started/create-an-app-from-scratch/add-a-component-using-a-template.md). # Add a component using a template We have used the default jig template to add a profile jig to the project in the previous step. Let's go ahead and add a component template. Component templates allow you to quickly build up your solution by inserting the required component into the jig file. In our solution, we have a new customer form, when we signup the new customer we want them to sign the form. Let's use the signature component template to do this.

1. In Explorer in the **jigs** folder, right-click on the **new-customer.jigx** file. 2. Components are normally added under a `children` node in the YAML. Under the last `component.email-field` section just above the `actions` node place your cursor in the correct node position in the YAML editor and press the **ctrl+space** keys. The Jigx component IntelliSense popup displays listing the available components.

3\. Scroll to the bottom and select **Use template**. The template gallery opens providing the templates for various components. Use the *Search* and *category* fields to find the signature template or browse the gallery by scrolling through the options.

4\. Hover over the**Form signature field** template and click the blue **insert** button.

5\. The template YAML will be inserted into your jig file.

6\. Publish your project and tap on the new customer widget on the Home Hub in the app. See the signature component on the form. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.jigx.com/getting-started/create-an-app-from-scratch/add-a-component-using-a-template.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.