Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

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.

Comments on Do we need templates for new posts?

Parent

Do we need templates for new posts?

+6
−0

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. 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?

History
Why does this post require moderator attention?
You might want to add some details to your flag.
Why should this post be closed?

0 comment threads

Post
+2
−3

Please no, except perhaps for unusual form-like posts.

I have never experience seeded text to be useful. It's actually a negative because it distracts and I have to delete it. Seeded text is never what I want to say. It also feels like an intrusion on my author's rights, and nannyish in general.

If a post has to conform to some very specific formatting, then it might make sense. That would be very rare, however. Perhaps recipes on Cooking fall into that category. I am not familiar with them. Even then, you have to be careful that it doesn't stifle creativity in those cases where an unusual approach benefits the post. I don't think this feature would be appropriate for any of the places I have been here (which is pretty much everywhere except Cooking and Judaism).

By all means, provide lots of documentation. In the end, though, it's up to each author what to write. Then it's up to the community to judge that writing.

History
Why does this post require moderator attention?
You might want to add some details to your flag.

1 comment thread

General comments (5 comments)
General comments
Monica Cellio‭ wrote over 3 years ago

I did say "optional". I'm asking whether it should be available, meaning whether it's useful in some places. Where it's not useful, don't use it.

Olin Lathrop‭ wrote over 3 years ago

@Monica: The question then becomes where it is useful. My point is that it is so rarely useful that I'm worried about people thinking it's a cool feature and turning it on in places it would annoy me.

Mithrandir24601‭ wrote over 3 years ago

"Even then, you have to be careful that it doesn't stifle creativity in those cases where an unusual approach benefits the post." is definitely a thing that would need to be thought about - I just posted a recipe with an intermediate 'chill-in-fridge' step that can last from 30 minutes to overnight - is it possible to implement that in a way that works in the form, while being useful and searchable etc.?

Monica Cellio‭ wrote over 3 years ago

Templates should always be treated as starting points -- suggested text, but not a format enforced by the UI. That way if you need to adjust the presentation for a recipe, you can. For example, sometimes it makes sense to treat a thing and its sauce as two mini-recipes within a recipe. (@Mithrandir24601, I would think that "chill overnight" is just one of the steps.)

Olin Lathrop‭ wrote over 3 years ago

@Monica: I remember some things on SE having seeded text (voting to close for "other" reason was one of them, I think), and it was never ever useful. It was always something I had to delete to say what I wanted to say. If anything, it had the reverse effect from what was intended. Having to delete the text first fostered a sortof screw these assholes attitude, which resulted in less detail and handholding of the user.