docs(kno-13411): add number, color and list input field types to schema references

[emisilvacab]

Description

Documented three new partial/message type input field types in both schema reference pages:

• Number — numeric input with optional min/max bounds and unit label
• Color — hex color input (#RGB / #RRGGBB), including support for branding variable references
• List — repeatable list of items with optional per-item JSON Schema validation, plus Liquid usage examples for iteration and indexing

Tasks

KNO-13411

Screenshots

[linear-code]

KNO-13411

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docs	Ready	Preview, Comment	Jun 2, 2026 2:06pm

[cursor]

Risk MEDIUM: Adds documentation for three new input field types (number, color, list) to schema reference pages across two content sections.

Reasons

• Changes span two documentation sections (content/in-app-ui/ and content/template-editor/), triggering MEDIUM per classification rules
• Large purely additive diff (375 lines added, 0 deleted) across 2 existing MDX files
• No code, component, config, or package changes (no HIGH triggers)
• No new pages, sidebar changes, or navigation modifications
• Content between the two files is nearly identical — worth verifying they stay in sync

Notes

• Verify the internal link to /template-editor/branding in the Color section resolves correctly
• Confirm the Liquid code examples in the List "Usage" section render properly in the MDX pipeline
• Check that the duplicated content between both schema-reference files is intentionally mirrored and consistent

  

_{Sent by Cursor Automation: Docs PR classifier}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit fbea131. Configure here.}

[cellomatt]

Per QA discussion

Suggested change

	"question": { "type": "string" },
	"answer": { "type": "string" }
	"question": { "type": "string", "title": "Question" },
	"answer": { "type": "string", "title": "Answer" }

[cellomatt]

Per QA discussion

Suggested change

	"question": { "type": "string" },
	"answer": { "type": "string" }
	"question": { "type": "string", "title": "Question" },
	"answer": { "type": "string", "title": "Answer" }

[cellomatt]

These changes look good to me. The only followup question I have is wondering whether we should also update the FAQ for working with structured JSON data here; the example is a list of JSON objects. We could either point to the list input, or expand on the examples to have both a list and a single json object? Could also be done separately from this PR.

[emisilvacab]