Based on the feedback and the poll, the snippet repository will be housed in the directory alongside plugins and themes. Now is the time to figure out all the details.
Submission and review process
What would be the best way to receive submissions? One possible way:
- Create a form that an authenticated user can submit, which includes an ACE editor for the snippet.
- In the admin, there would be a queue of pending submissions.
- A reviewer would review the snippet.
- If rejected, an email would be sent to the submitter with the reviewer’s comment.
- If approved, the snippet would need to be published on GitHub and then published in the snippet repository.
- Each snippet should have an option to submit feedback or complaint, so users can report issues or add feedback. This can be reviewed privately and acted on if necessary.
Note: We should avoid requiring GitHub/Gist for submissions to keep the barrier to entry low.
Publishing on GitHub
Gists would need to be published under the ClassicPress account since they are not tied to repos. There are 2 questions here:
- Do we create a separate account to manage Gists?
- Can Gist creation process be automated using GitHub CLI (gh gist create) so when the reviewer hits “Publish” the directory creates a Gist and publishes snippet in the directory?
The admin side would need some basic management settings like modifying snippet details, unpublishing a snippet, deleting a snippet, etc.
Let’s figure this out.