Welcome to Codidact Meta!
Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.
Post History
We have some posting tips on the "ask question" (or "create post" etc) pages, and we plan to add better contextual help in the future. Another way to guide people would be with templates, a "proto...
#2: Post edited
by
Moshi
·
2020-09-10T02:29:49Z (about 4 years ago)
merging [post] and [posts]
#1: Initial revision
by
Monica Cellio
·
2020-07-23T03:12:42Z (over 4 years ago)
Do we need templates for new posts?
We have some posting tips on the "ask question" (or "create post" etc) pages, and we plan to add better contextual help in the future. Another way to guide people would be with *templates*, a "proto-question" (or proto-blog-post or proto-challenge etc) that you get in the editor. A template could be a mix of content (like headings) and instructive HTML comments.
I got this idea when I saw this [request for better recipe formatting on Cooking](https://cooking.codidact.com/questions/276836). Most recipes follow a particular format -- introduction, ingredients, equipment, instructions -- but people have to create that structure by hand, each time. Over on SE, on some sites people asked for such templates to help people ask decent questions (particularly on SO, as I understood it). On GitHub, a feature request is similarly populated with some instructive comments.
Should we have (optional) templates for posts? I'm imagining that a template could be defined *per category and per post type* -- so articles in the Recipes category get that special recipe template, but it wouldn't affect questions or other categories. On Judaism, the Challenges category supports both articles (to announce challenges) and questions (to collect suggestions), so articles in that category could have a template without affecting questions in that category.
This approach would not help with finer distinctions, though. One could imagine feature requests on Meta having a template and bug reports having a different template, but that would mean either having several buttons ("create feature request", "report bug", "request support", "discuss something") or adjusting the editor contents after tags are chosen, which seems hard to do robustly. Alternatively, we could let the author select a template (or not) if templates are defined for that site (or category?), but this might mean newer users would be less likely to use them, defeating one of the purposes.
Should we do something like this? If so, how should we structure it?