Our most common form of communication is via the blog at 2i2c.org/blog. It is managed by our Hugo website repository.
What to post on the blog#
Generally speaking, we can post as often as we wish. Our blog should be a running heartbeat of our organization, and it is OK if the information on there isn’t perfect. Be creative and experiment with formats that you think might be interesting or fun. If there’s something particularly important, we can signal-boost it with our Mailing list.
Here are a few ideas for blog post topics for inspiration:
2i2c organizational updates. Provide updates about important organizational decisions and changes. For example:
Major changes to strategy
Governance or other organizational changes
Major project updates. For major projects and collaborations, we should provide regular updates about the work that we’ve done. This shouldn’t frame 2i2c as the sole producer for these projects (unless we really are the sole producer), but demonstrate how 2i2c has contributed to the overall effort. For example:
Major deliverables that we’ve met on a project
Open source updates. If we do particular service work, or make a strong technical improvement in an open source project, we should tell the world about it.
Updates from the Managed JupyterHub Serivce. As hub service infrastructure grows and evolves, and as we serve more communities with it, we should tell others about the impact we are having.
Topic dives. There may be particular topics that we want to write about, like open culture, cloud optimization, etc. These will help us crystallize our thoughts, demonstrate expertise, and share knowledge with others.
Blog post checklist#
We have a blog post checklist that helps keep track of the major actions needed to post something and share it. Click the button below to find it.