Automattic / Automattic/blicki
Editor permissions at subpage level
- Dominant language
- PHP
- Stars
- 27
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
Hi, I was in Dr. Conner's class at the end of last semester when Gracie showed us Blicki. I had suggested that editors and contributors have permission at the subpage level since Dr. Conner was thinking about using blicki for a classroom setting. In this way, teachers or editors of certain sections would have control only of those sections. For example on a classroom blicki page like home/semester/classes/ENC3150, a student contributor could only log in past the .../ENC3150 page. The same would be so for an editor, perhaps of a section in an online newspaper like home/USFSPstudentnews/section/artsandentertainment/articles, an editor would only have control of pages past .../artsandentertainment.
I mentioned this idea to Gracie at the time and she told me to post it here, I just hadn't got around to it, but I didn't forget!
Thanks.
-philip
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no files, tests, or entry points. Start by locating the existing WordPress editor and contributor permission handling, then determine how permissions could be scoped to paths such as home/semester/classes/ENC3150; done should ensure users can access only pages below their assigned subpage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php, wordpress
- Domain
- authorization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100