Automattic / Automattic/cortext
Sharing and permissions
- Dominant language
- JavaScript
- Stars
- 51
- Forks
- 2
- Avg merge
- 3h 12m
- Merged PRs (30d)
- 8
Description
## Goal
Let users control who can see or access Cortext pages and collection views.
## Scope
* Add private, shared, and public states for Cortext content.
* Add share controls for pages and collection views.
* Reuse WordPress capabilities where possible.
* Coordinate with frontend rendering so public content renders without leaking private rows or pages.
* Keep the first version focused on access control and sharing UX.
Contributor guide
Research direction
Start by mapping the existing page and collection-view rendering and the WordPress capabilities used for access checks. Define how private, shared, and public states and their share controls fit together, then verify that public rendering cannot expose private rows or pages. No files or tests are named, so the implementation entry points and completion checks must first be established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, wordpress
- Domain
- authorization, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100