Today I submitted #445 for new pages for Kaggle competitions. Now I am reflecting on this process:
The workflow for publishing this content looks like this:
Colleagues ask UX designer for new Google docs for K3 & K4 content
UX designer creates template for K3 & K4 based on live K2 page
UX designer sends back Google doc links to colleagues
Colleagues write/edit content in Google docs
Google docs are passed back to UX designer
UX designer observes unresolved comments in Google docs and reaches out to additional colleagues to confirm if resolved or not
Colleagues edit Google docs
Colleagues pass Google docs back to UX designer
UX designer submits issue #445, requesting that development modify HRA website infrastructure and add two new pages
Development builds infrastructure and two new pages
Development sends preview to UX designer
UX designer inspects preview and communicates if changes are needed
UX designer approves development's preview
Development merges PR
Content is available on the website
Questions I will remain curious about:
How might we best utilize and maximize our time at work?
How do bioinformatics companies share exciting updates about their work?
Is there a blogging functionality web component that could be added to future versions of the HRA?
Observations about this process:
HRA release week is always busy. I was the blocker in steps 1 and 8: I lived in Figma and GitHub this week while working on 7th release UX-related tasks. I am not a fan of being the blocker!
I am not approving content of this nature, so I often feel like an extra cook in the kitchen.
I want people to feel empowered that they have the tools they need to provide content for the HRA.
Questions for the future:
The redesigned HRA website will not have pages of this nature. How will we capture this information?
Would it be appropriate to have a blogging component for this type of HRA content?
This component could need the following for our colleagues:
Simple UI
Credentials such as login info, author tracking
Rich text editing
Reviewing functionality
Publish to website functionality
Edit functionality
Is this a 3rd party web component?
How much does it cost?
Do we build this ourselves?
Is it worth it?
What else could be done to improve this workflow for our colleagues?
How else might we improve website content publishing processes for the HRA?
Blogging functionality for newsworthy HRA posts?
Today I submitted #445 for new pages for Kaggle competitions. Now I am reflecting on this process:
The workflow for publishing this content looks like this:
Questions I will remain curious about:
Observations about this process:
Questions for the future: