Skip to content

Resolve TODO: templates are admin-configurable via ACP #6

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
bonelifer merged 1 commit into from
Sep 23, 2026
Merged

Resolve TODO: templates are admin-configurable via ACP #6

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 13 additions & 3 deletions docs/TODO.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,6 +17,16 @@ The template picker lives on the edit page itself (not the overview page's
quick-create box, which still just takes you straight to a blank edit form
and lets you pick there).

Not scoped further yet — open question: should templates be
admin-configurable/extensible beyond these two, or are "Blank" and "Generic"
enough?
Templates are admin-configurable: admins can add new templates beyond the
built-in "Blank" and "Generic" ones, via an ACP page.

Still needs deciding before implementation:

- What a template is allowed to contain (plain text with placeholders?
BBCode? anything the message parser accepts?) and how that's authored in
the ACP form.
- What sanitization that admin-authored template content needs before it's
inserted into the edit form's message body — it's admin-authored rather
than end-user input, but still ends up in content regular members see and
can build on, so it shouldn't get a free pass on the same checks normal
article content goes through.
Loading