Render pages and forms

Compose a documentation layout

1import { renderDocsLayout, renderForm } from "@qentrah/templates";
2 
3const form = renderForm({
4  action: "/articles",
5  method: "POST",
6  fields: [{ name: "title", label: "Title", type: "text", required: true }],
7  submitButtons: [{ label: "Save", type: "submit" }],
8});
9 
10const html = renderDocsLayout({
11  title: "New article",
12  content: form,
13  currentPath: "/articles/new",
14  navigation: [{ title: "Articles", path: "/articles" }],
15});

Both functions return strings. The form action must point to a route implemented by your server. Rendering a form does not save a record.

Form data contract

fields and submitButtons are required. Optional form settings include id, action, method, hxPost, hxPut, hxTarget, title, description, and className. Field types include text, email, textarea, select, checkbox, rich_text, number, date, multi_select and file.

Input handling

The templates interpolate HTML. Validate and sanitize untrusted values in your application. Server handlers must perform their own authentication, authorization and input validation. Never treat a rendered interface as a security boundary.

Existing template families

The root also exposes cache, database-table, content-edit, content-new, checkbox, FAQ, API-reference, field-types and content-list renderers. Inspect each declaration’s data type before calling it; the renderers do not share one universal parameter object.