Some of the sites I work with do in fact have 1000s of “staff”.
thechocolatelife
•
Sep 8
And that should be an option for those publishers who wish it. I do not.
I ask my staff contributors to produce a minimum number of posts/year to earn/keep a staff position.
Cathy
Team•
Sep 8
Sure. Given the annoying flow of adding a new staff contributor, it’d sort of have to be opt-in.
But now I’m curious (if off topic) - do you delete contributors who don’t meet your annual requirement? And if so, do you go back and add their byline to the top of the post body manually?
thechocolatelife
•
Sep 8
Delete: I just checked that myself, actually, and I am not entirely consistent.
I set a threshold – any contributor with eight or more posts gets kept. For the others it depends. That’s because my thoughts have changed over the past five years, which influenced how I handled things at the time and I can’t reconstruct the logic now.
Cathy
Team•
Sep 8
Oh yes, definitely with editorial review. :) It’s likely to get some spam.
Yeah, a generic “Community” staff member would work. Or you could do the Staff Builder to actually put bylines on it, but that might be more trouble than worth.
thechocolatelife
•
Sep 8
Would the Staff Builder create a unique staff member for each? I don’t see a proliferation of staff accounts with one post (or at most a few posts) each, is viable in the long run.
As I see it, during the editorial review process the staff member in charge of review/publishing would add the byline at the top of the post with an (optional) bio graph at the bottom.
thechocolatelife
•
Sep 8
Only with editorial review, but yes – removing friction would be a good idea.
Perhaps there is a Community staff member and all of the community-submitted and approved posts can be attributed to that staff member?
Log in to comment and vote
Comments7
Cathy
Sep 8
Some of the sites I work with do in fact have 1000s of “staff”.
thechocolatelife
Sep 8
And that should be an option for those publishers who wish it. I do not.
I ask my staff contributors to produce a minimum number of posts/year to earn/keep a staff position.
Cathy
Sep 8
Sure. Given the annoying flow of adding a new staff contributor, it’d sort of have to be opt-in.
But now I’m curious (if off topic) - do you delete contributors who don’t meet your annual requirement? And if so, do you go back and add their byline to the top of the post body manually?
thechocolatelife
Sep 8
Delete: I just checked that myself, actually, and I am not entirely consistent.
I set a threshold – any contributor with eight or more posts gets kept. For the others it depends. That’s because my thoughts have changed over the past five years, which influenced how I handled things at the time and I can’t reconstruct the logic now.
Cathy
Sep 8
Oh yes, definitely with editorial review. :) It’s likely to get some spam.
Yeah, a generic “Community” staff member would work. Or you could do the Staff Builder to actually put bylines on it, but that might be more trouble than worth.
thechocolatelife
Sep 8
Would the Staff Builder create a unique staff member for each? I don’t see a proliferation of staff accounts with one post (or at most a few posts) each, is viable in the long run.
As I see it, during the editorial review process the staff member in charge of review/publishing would add the byline at the top of the post with an (optional) bio graph at the bottom.
thechocolatelife
Sep 8
Only with editorial review, but yes – removing friction would be a good idea.
Perhaps there is a Community staff member and all of the community-submitted and approved posts can be attributed to that staff member?