I’m currently working on category mini-sites for overviews of different projects. To do this, one section requires short bios of each organiser of the project, using the following sort of template:
Title: this can be your name or whatever short blurb you find relevant to the project Body: a short bio about you (no more than 200 words), your role and your aim in the project
Tag this post with ‘organiser’ and post it.
You can put it in the Public Workspace section of the category, as long as it’s public.
Our current convention is to place all editorial content of secondary websites filled from Discourse into a sub-category named “Web Content” inside of a project’s Discourse category. That sub-category should not be visible to “normal” Discourse users but rather require a certain group membership (that is however not universally observed … yet). It means that a software taking over that editorial content has to use an API key (as GET parameter … should work as POST parameter as well but does not).
Please use that convention as well. Otherwise, it will become a bit of a messy and noisy place here as there would be small posts tagged with ad-hoc tags. Users would be notified about that content and wonder what it is, and admins may also wonder and delete it and be surprised that they broke some external site. When it’s all in a “Web Content” sub-category with a proper category description, that won’t happen.
If you want to use tags and be sure they won’t be re-organized or deleted in the future, I think there are two good options:
Use a {projectname}-* tag. This is a tag namespace specific to a project like POPREBEL and won’t be touched by site admins. For details, see our manual about tags.
Introduce and use a new webcontent-* tag namespace, and document it in our manual about tags.
But in this case, instead of relying on tags I would propose you create one topic (referenced by ID in your software) with instructions in the first post and let people post their contribution as a reply in that topic. You can give them a formatting template like “Start with a ## Heading. Then one paragraph of text.” Your software can then obtain the raw markup and render it as needed, using a URL with topic ID and post ID, like this:
