Want new blog posts without the draft tag#176
Open
peterjc wants to merge 2 commits into
Open
Conversation
Also want basic proof reading in advance to speed up the PR review.
nlharris
requested changes
Jun 29, 2026
|
|
||
| ## How to Submit Your Blog Post | ||
|
|
||
| This assumes you've already shared a first draft with the OBF Board for comment |
Member
There was a problem hiding this comment.
Suggested change
| This assumes you've already shared a first draft with the OBF Board for comment | |
| Before starting a PR here, please share your blog post draft (in the form of a google doc) with the OBF Board for comments. Once the Board has reviewed and approved it, please make a PR as described here. |
Member
Author
There was a problem hiding this comment.
Applied with tweak - I do not want to mandate Google Docs in particular.
|
|
||
| 4. View template raw, and Copy and paste all the contents of this template into the new file. | ||
| 5. Replace the placeholder text (date, title, author, content, image name, etc.) with your actual blog content. | ||
| 6. Remove the `draft: true` line (we don't want the template published, we do want your post published). |
Member
There was a problem hiding this comment.
I don't get what this means about the template being published.
Member
Author
There was a problem hiding this comment.
We do not want the YYYY-MM-DD-event-fellowship-blog-template.md page live and visible on the website.
Member
Author
There was a problem hiding this comment.
We do not want the YYYY-MM-DD-event-fellowship-blog-template.md page live and visible on the website.
Evidently my attempt at clarity needs improving...
Suggesting but not mandating Google Docs
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Also make it clearer that we usually do basic proof reading done in advance to speed up the PR review (often with Google Docs but need not be).
Currently we have had to manually remove the
draft: trueline as part of PR review (eg #172) or right afterwards when we notice the post hasn't gone live (eg #139).Q: Provided the post has already been proof-read then there should only be a short delay (a few days) before these being merged, but should the template suggest future dating the post anticipating this?