![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
![[site community profile]](https://www.dreamwidth.org/img/comm_staff.png)
Community sticky posts editable by all admins
Title:
Community sticky posts editable by all admins
Area:
page: entries, site: community features, workflow: community administration
Summary:
It would be helpful if community accounts could make sticky posts inside the community, then editable by everyone with admin rights within that community.
Description:
Communities already make use of sticky posts for a variety of reasons - e.g. dw_suggestions has one (made by denise) that acts as an introduction and usage guide to the comm.
I suggest that it would be helpful for communities to be able to contain sticky posts nominally made by the community account itself, giving all community admins editing rights over it. I imagine this working via the "post as: another user" module in the new update page.
Example use cases: in dw_dev_training, I envisage this being used as an up-to-date centralised record of current babydev bait; Momijizukamori has said they'd love something like this to link to resources, beyond the bare bones in dreamscape's community profile.
ISSUES that I can come up with:
- community accounts currently can't be associated with posts, as far as I know, so that would be an exciting thing to work with
- would probably want there to be one post permitted per community (so would need to work out how to limit this - wouldn't just want automatic overwrite of pre-existing posts!)
Alternative solutions/workarounds:
(1) Create a mutual admin account (as in use at <user name="poetree"> with the shared account <user name="poetree_admin">). Downsides: security hassle - DW tends to discourage sharing accounts, I think? Logging out/in/out/in hassle - this will presumably be removed as and when seamless account switching is implemented.
(2) Some styles permit insertion of custom text to be displayed in the sidebar. Standardisation of this feature across styles (complete with full mark-up!), including choice as to where to site the custom text within the layout, might be a suitable alternative that would be editable by all admins.
This suggestion:
Should be implemented as-is.
18 (41.9%)
Should be implemented with changes. (please comment)
4 (9.3%)
Shouldn't be implemented.
4 (9.3%)
(I have no opinion)
14 (32.6%)
(Other: please comment)
3 (7.0%)
no subject
no subject
So either have such posts be written by the comm, or have authorship reassigned if an edit is done by a different admin?
no subject
Oh I'd missed that part of the suggestion. Thanks. Hmm. I'd still like it better if that was separate from entries but I think this has more to do with sticky entries and communities in general than this suggestion. :)
no subject
no subject
I guess the "right way" to do this would be to allow posts on communities to have multiple authors. But while I haven't checked, I imagine that would be a Really Big Deal in a messing-with-fundemental-data-structures way. So if we want to do this (which I agree would be useful) it's a matter of deciding which type of bodge is preferred ;-)
no subject
no subject
no subject
no subject
no subject
no subject
no subject
So in my version it's post-by-post. I suppose you could also duplicate this in comm account settings as a global ticky box that applies to all sticky posts that will ever be made in the comm.
Either way, if the community started off with one admin who wants to maintain strict editorial control (try not to mind my inner control freak, thanks), this allows her or him to let go of that control strictly at will, easing their anxiety.
Whew. my inner control freak almost completely melted down just writing that.
no subject
no subject
I think people are getting confused by the poll question, since it's not as specific as your post.
no subject
I'm one of the co-users of the
For one-time posts to POETREE such as a comm announcement or a particular instance of a weekly feature (e.g. Sunday Picnic posts) the authoring admin includes their DW user name formatted in small italics in isolation at the top of the post as a byline.
E.g., For multiple-use posts, such as our Community Calendar, the comm landing sticky, or signup posts for themed community weeks,
E.g. We also use the