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 New post type: a recap table
Post
New post type: a recap table
Motivation
I often want to use a table to:
- Compare different solutions (for example, solutions addressing a new feature-request).
- List related posts and duplicates (some topics can be extremely diluted in dozens of posts in a community or even spread over several communities. In this case it would sometimes seem useful to me to list all these related posts in one place and it could prevent new duplicates by giving more visibility to the initial post).
However, currently I don't know where to put such a "recap table" as it belongs neither to a question nor an answer.
On Meta I allow myself to be more lax on this aspect and I sometimes post this type of recap in an answer like here. But this way of doing things does not seem viable to me on a site other than Meta because if we do not respect the very principle of what a question or an answer to a question is, we risk losing the interest of a Q&A (IMHO).
Proposal
A solution could be to create a new type of post (let's call it "Recap post" but I'm not good at choosing names ;-) which can only be a table with a caption (and optionally also with a title: TBD).
The problem is, How to force the author to write only a table while allowing a lot of freedom on the content?
One solution could be to automatically detect if the post contains:
- A table (typeset in Markdown).
- A caption (limited in size, the limitation should probably be dynamically linked to the table size because a big table could need, for example more footnotes to explain their content) (below the table maybe).
- (Optionally a title, limited in size, above the table).
If it is not possible to automatically detect such complex content, then the user can tell the number of rows and columns and then the corresponding table cells could be filled one by one in separated text boxes (idem for the caption and the title), something like that:
It is not optimal because it is cumbersome to fill in and the text is not contained in one single Markdown block. It makes links harder to make between cells and between cells and caption...(But even in that state I will definitely use it personally!)
Whatever the technical solution adopted, this post type could have the following feature (IMHO):
- "Middle level post" maybe displayed just below the question and above the answers.
- Freely editable: anybody with the Participate Everywhere privilege can edit the post directly
- Cannot be voted on (TBD)? (or maybe yes if it encourage people to make it when necessary...)
- No tags (TBD)?
- Allowing comments (TBD)?
- Maybe "owned" by the person who created them as for wiki posts?
EDIT after follow-up comment:
Issues
How to deal with answers posted after the "recap table post"? How to encourage people to update the "recap table post" if relevant?
The freely edit property is necessary but not sufficient (even if the owner is notified when a new answer is posted). Another solution to encourage editing would be to display a warning to a user posting a new answer (if a "table recap post" is already present), but again, maybe not sufficient.
Note that this issue is mainly present when comparing answer of the same question for example (but the range of use of this type of post would not be restricted to just this use)
1 comment thread