///

## Writing templates { #writing-templates }

Then you can write a template at `templates/item.html` with, for example:

```jinja hl_lines="7"
{!../../docs_src/templates/templates/item.html!}
```

### Template Context Values { #template-context-values }

In the HTML that contains:

{% raw %}

```jinja
Item ID: {{ id }}
```

          <velocityBasedir>${project.basedir}/../../src/mdo</velocityBasedir>
          <models>
            <model>src/main/mdo/maven.mdo</model>
          </models>
          <templates>
            <template>model.vm</template>
          </templates>
          <params>
            <param>packageModelV4=org.apache.maven.api.model</param>
            <param>isMavenModel=true</param>
          </params>
        </configuration>

# Full Stack FastAPI Template { #full-stack-fastapi-template }

Templates, while typically come with a specific setup, are designed to be flexible and customizable. This allows you to modify and adapt them to your project's requirements, making them an excellent starting point. 🏁

You can use this template to get started, as it includes a lot of the initial set up, security, database and some API endpoints already done for you.

    steps:
      - name: Checkout
        uses: actions/checkout@v5

      - name: Check links
        uses: lycheeverse/lychee-action@v2.6.1
        with:
          # excluded:
          # - notes.md and notes-templates.md - because they are a part of user guide
          # - Kotlin's Module.md - because it's a part of the Kotlin DSL docs
          args: >
            --no-progress --offline '**/*.md' --include-fragments

    - advanced/using-request-directly.md
    - advanced/dataclasses.md
    - advanced/middleware.md
    - advanced/sub-applications.md
    - advanced/behind-a-proxy.md
    - advanced/templates.md
    - advanced/websockets.md
    - advanced/events.md
    - advanced/testing-websockets.md
    - advanced/testing-events.md
    - advanced/testing-dependencies.md
    - advanced/async-tests.md

            { "aliases", "allocation", "count", "fielddata", "health", "indices", "master", "nodeattrs", "nodes", "pending_tasks",
                    "plugins", "recovery", "repositories", "thread_pool", "shards", "segments", "snapshots", "templates" };

    // ===================================================================================
    //                                                                           Attribute
    //

    /**

/**
 * Utility class providing static functions for Fess JSP/JSTL expressions and tag libraries.
 * This class contains various helper methods for formatting, parsing, and manipulating data
 * in Fess web templates, including date formatting, localization, file operations, and
 * query parameter handling.
 *
 * @since 1.0
 */
public class FessFunctions {
    /** Logger instance for this class */

* <a href="https://jinja.palletsprojects.com" target="_blank"><code>jinja2</code></a> - erforderlich, wenn Sie die Standardkonfiguration für Templates verwenden möchten.

* <a href="https://jinja.palletsprojects.com" target="_blank"><code>jinja2</code></a> - Obrigatório se você quer utilizar a configuração padrão de templates.

            doc.put(HL_CACHE, StringUtil.EMPTY);
        }

        try {
            final Template template = handlebars.compile(cacheTemplateName);
            final Context hbsContext = Context.newContext(doc);
            return template.apply(hbsContext);
        } catch (final Exception e) {
            logger.warn("Failed to create a cache response.", e);
        }