> For the complete documentation index, see [llms.txt](https://docs.aurelia.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aurelia.io/developer-guides/error-messages/0088-to-0723/aur0708.md).

# AUR0708

Template compilation error: the custom element "yyyy" does not have any content other than local template(s).

### **Error message**

Template compilation error: the custom element "{{0}}" does not have any content other than local template(s).

### **Parameters**

1. `elementName`: The name of the custom element being compiled.

### Error explanation

This error occurs during template compilation when the main template of a custom element consists *only* of one or more local element definitions (`<template as-custom-element="...">`). A custom element's template must contain some actual content or structure besides just defining local elements.

Local elements are defined within a parent component's template, but the parent component itself must still have its own primary template content.

### Common causes

* Creating a custom element template that only contains `<template as-custom-element="...">` tags.

### How to fix

* Add some actual content (HTML elements, text, bindings, etc.) to the main `<template>` of the custom element, alongside any local element definitions.
* If the intention was simply to group reusable templates, consider defining them as separate components instead of local elements within an otherwise empty parent.

### Example of Incorrect Usage:

```html
<!-- my-container.html -->
<template>
  <!-- Error: Only local element definitions, no other content -->
  <template as-custom-element="local-one">
    <div>Local One</div>
  </template>
  <template as-custom-element="local-two">
    <span>Local Two</span>
  </template>
</template>
```

### Example of Correct Usage:

```html
<!-- my-container.html -->
<template>
  <!-- Add some primary content for the container -->
  <h1>My Container</h1>
  <local-one></local-one>
  <hr>
  <local-two></local-two>

  <!-- Local element definitions are fine alongside other content -->
  <template as-custom-element="local-one">
    <div>Local One</div>
  </template>
  <template as-custom-element="local-two">
    <span>Local Two</span>
  </template>
</template>
```


---

# 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.aurelia.io/developer-guides/error-messages/0088-to-0723/aur0708.md?ask=<question>&goal=<user_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.