Repository navigation
Document blog post workflow from doc text to promotion #168
Description
A documented workflow for going from Google Doc blog text and images (ideally source images are in folder, not taking screenshots from the doc), link to website Wiki, alt-text guidance, create and use markdown list of authors & their ORCID IDs, how and when to use Ronny’s code for cross-posting (should we always update NASA-Openscapes home page with new blog posts? Events only?), how to use MainPlanning GitHub Project for getting assigned (update Issue template for blog post to point to this documentation), deadlines, communications, drafting txt links and images for social media, posting to Slack, handoff to core team member to post to NMFS Google Space.
Give access to Blogs Google Folder, pull request permission on website, access to MainPlanning Project.
A plan for initial “checking your work” - one core team member merges PRs.
Ileana or Ileana and Stef to onboard them (we could cowork to draft the documentation … maybe after our GitHub Clinic prep is done)
Metadata
Metadata
Assignees
Type
Projects
- Status
Activity
ronnyhdez commentedon Sep 18, 2026
One suggestion for the google docs drafting workflow: could we include the image filename and alt text where each image should go, along with a link to the original image in Google Drive? For example:
This could help us plan alt text or the caption and make it easier to move the post from the google doc to the qmd file.