kaberett: Trans symbol with Swiss Army knife tools at other positions around the central circle. (Default)
kaberett ([personal profile] kaberett) wrote in [site community profile] dw_suggestions2013-07-08 11:13 am

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.

Poll #13974 Community sticky posts editable by all admins
Open to: Registered Users, detailed results viewable to: All, participants: 43


This suggestion:

View Answers

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%)

jjhunter: Paper sculpture of bulbuous tree made from strips of book pages (poetree admin icon)

[personal profile] jjhunter 2013-08-14 03:52 pm (UTC)(link)
*waves*

I'm one of the co-users of the [personal profile] poetree_admin account mentioned in this suggestion post; the system of written & visual cues [personal profile] alee_grrl and I have developed to signal who wrote / last edited which posts when using that communal admin account may be of use to others in this discussion.

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.,
[Post Title]
[Date]
[personal profile] poetree_admin


jjhunter

[Post content]
For multiple-use posts, such as our Community Calendar, the comm landing sticky, or signup posts for themed community weeks, [personal profile] alee_grrl and I do any pre-drafting we want to in access-locked posts to the [personal profile] poetree_admin account, and then post with that account to [community profile] poetree proper with a footer detailing which of us has most recently edited that post & when.

E.g.
[Post Title]
[Date]
[personal profile] poetree_admin


[Post content]

---
Last edited 8/14/13 by jjhunter
We also use the [personal profile] poetree_admin default icon (the one I'm using here) with our personal accounts if we're acting in our capacities as comm admins but want to be a bit more personal / informal about how we're doing so.