Template:Category/Post/footer
Footer template for Category:Post pages — paired with Template:Category/Post.
Post pages invoke this at the END of the page body so the comments section renders below the post's prose:
Comments
Why a separate template: the SemanticSchemas dispatcher auto-renders Template:Category/Post at the TOP of every Post page, so anything in that template lands above the prose. Comments belong at the bottom, so they live here in a footer the author drops in manually — same pattern as Template:Category/Project/footer.
How comments work
No custom comment system: comments live on the post's Talk page and are authored with DiscussionTools (the same tooling the wiki already uses for its forum/discussion board). This footer just surfaces them:
- When the Talk page exists, its discussion is transcluded here as a
read-only preview followed by a link to the full Talk page. DiscussionTools' reply/Add-topic UI only activates in the Talk namespace, so the transcluded copy on this main-namespace post page renders as static text — readers click through to the Talk page to actually reply, where the full threaded UI lives.
- When it doesn't exist yet, an invite to start the discussion shows
instead (the link lands on the empty Talk page, where DiscussionTools' Add-topic affordance creates it).
The preview is height-capped (see .post-discussion-thread
in Template:Category/Post/styles.css) so a long thread doesn't
dominate the post; short threads show in full, longer ones scroll
within the box.
The talk page is resolved with Template talk:Category/Post/footer, i.e.
always the Talk page of the post this footer is rendered on — there is
no page-override parameter (none is needed for the normal case of
invoking the footer from the post's own page).
NOTE: the Template talk:Category/Post/footer transclusion sits on its
own line inside .post-discussion-thread on purpose. Don't
collapse it back onto the same line as the opening
:
if the transcluded content follows inline markup, its first line
(usually a == topic == heading) is no longer at the start
of a line, so MediaWiki renders the leading == as literal
text instead of a heading. The newline keeps the first topic heading
parsing correctly.
Deployment
Like the UI/* widgets and the Project footer, this
template isn't reachable from any category's display template, so it
only syncs if it's listed in the wiki's SchemaSync:Config
pages: list. Add Template:Category/Post/footer
there.