These sections cover our practices and resources for communicating outside of the project.
We have a blog at
This is most-often used for major project updates, but can also be used to discuss particular decisions or features in more detail, give general updates about what we are up to, etc.
Generally speaking, we post under a generic “Executable Books” author byline, keep doing this until we define authorship guidelines for posts.
In some cases team members may be asked to give presentations on behalf of the Executable Books project. We do not yet have a formal policy for giving presentations. In the meantime, the JupyterHub external communications practices are a good place to start.
Talks/ folder in the Google Drive has several slides from old talks that have been given by team members.
If you give a talk, consider adding it so that others may learn or re-use the content.
Social media accounts#
We have two Twitter accounts as a centralized place where people can follow to learn about updates in our project.
@executablebooks: Covers general project updates and the broader Jupyter Book, Sphinx, etc ecosystem.
@myst_tools: Specific to MyST Markdown, open MEP proposals and their decisions, syntax updates, etc.
We use these accounts to “push” information and boost the visibility of the project. We do not use them to engage in discourse with others on social media.
Use these accounts to announce new releases and major features, upcoming events, and generally helpful information to our community.