-
Notifications
You must be signed in to change notification settings - Fork 178
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Media Strategy content #748
Merged
Merged
Changes from 18 commits
Commits
Show all changes
22 commits
Select commit
Hold shift + click to select a range
fb155e0
Add Media Strategy content
blink1073 26cefc2
Merge branch 'main' of github.com:jupyter/jupyter.github.io into add-jms
blink1073 5593649
address review
blink1073 4e80c82
Merge branch 'main' of github.com:jupyter/jupyter.github.io into add-jms
blink1073 b7c3985
fix link
blink1073 eeefc15
fix relative links
blink1073 8dfbeb3
remove extra file
blink1073 a3affb3
try an extra slash
blink1073 9b82e1d
remove extra slash
blink1073 ae002d9
ignore medium links
blink1073 d3d0bfd
fix link ignore
blink1073 b8e28cc
address review
blink1073 81022c6
fix usage of email
blink1073 0cfeaa0
clean up submission guidelines
blink1073 4f8d948
ignore twitter links
blink1073 4d06f71
fix ignore
blink1073 ca2a1b6
add another link to submission guidelines
blink1073 e3e4fd6
fix ignore
blink1073 8af4134
address review
blink1073 54140f6
ignore jupytercon link
blink1073 f7905d9
ignore jupytercon link
blink1073 f01f532
ignore jupytercon link
blink1073 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,52 @@ | ||
--- | ||
layout: page | ||
title: Submission Guidelines | ||
tagline: Project Jupyter Media Submission Guidelines | ||
permalink: /media_submissions | ||
--- | ||
|
||
## Editorial Principles | ||
Read more about our [editorial principles](https://jupyter.org/governance/charters/MediaStrategyCharter.html) in our charter. | ||
|
||
## Content Guidelines | ||
The Project Jupyter blog is designed for community members to share valuable and educational content about Jupyter. Blog posts can be about various topics, for example how you got started with Jupyter, the latest extension you built around Jupyter, a quick tutorial on how to use a specific feature, and more. This channel is powered by our community members so there are no particular requirements for how the blog post has to be written. | ||
|
||
Here is an example of a potential structure: | ||
|
||
- Title | ||
- Subtitle (max 140 characters) – summary of what the blog post is about | ||
- Provide one image that represents your project - it can also be a code snippet | ||
- Introduce your topic | ||
- Why is this topic important? What are the benefits for the Jupyter community? | ||
- Do you have an interesting user story or usage example? Include this here. | ||
- Pick a specific usage example and provide a step-by-step guide so the readers can follow along. Make sure to include visuals or | ||
code examples so readers can follow along easily. | ||
- Thank/acknowledge the people who helped make the work described in the blog post possible. This includes anyone who helped you | ||
write the blog post itself. | ||
- End the article with the forward-looking statement about your project or research | ||
|
||
Blog Post Examples: | ||
- Shorter post: [European Commission Funds Jupyter Bug Bounty Program](https://blog.jupyter.org/european-commission-funds-jupyter-bug-bounty-program-b7b96f9831e6) | ||
- Longer post: [Generative AI in Jupyter](https://blog.jupyter.org/generative-ai-in-jupyter-3f7174824862) | ||
- Post using the Jupyter Voice: [JupyterLab is Ready for Users](https://blog.jupyter.org/jupyterlab-is-ready-for-users-5a6f039b8906) | ||
|
||
## RESPONSE TIME: Volunteer working group | ||
Please note that we will vet content against our current editorial review backlog, and follow up with you if there are any issues. Plan ahead. We are primarily a group of volunteers and we will review requests for publication on a weekly basis. | ||
|
||
## BLOG: Submission process (blog.jupyter.org) | ||
- *Create a Medium account*. If you are new to Medium, create an account by following these [instructions](https://help.medium.com/hc/en-us/articles/115004915268-Sign-in-or-sign-up-to-Medium). | ||
- *Request permissions*. Email the Jupyter Media Strategy working group (JMS) at [email protected] to have your Medium account to be added as the writer of the blog. Once you are added as the authorized writer, you should receive an email that allows you to upload your blog. | ||
- *Submit your story*. For step by step instructions see the following Medium [article](https://help.medium.com/hc/en-us/articles/213904978-Add-a-draft-or-post-to-publication). | ||
- *Request review*. Email the JMS at [email protected] confirming you have submitted the story. and provide suggested social media text and image. | ||
|
||
## BLOG: Social media amplification | ||
Project Jupyter has various [social media channels](/social), provide the following information when requesting review: | ||
- Content (max 500 characters for Mastodon, 280 characters for Twitter/X) | ||
- Image for the post if one is available | ||
- Social handles to include (for @mentions) | ||
|
||
## MASTODON: Amplification of a message on Mastodon | ||
The Jupyter blog is the primary channel with which Jupyter communicates with the community. However, occasionally there are messages for which no blog post exists and the JMS will consider amplifying posts on Mastodon. Mastodon is our preferred channel as it best reflects the values of Project Jupyter. | ||
- Content - max 500 characters or a link to another Mastodon post | ||
- Image for the post (if one is available) | ||
- Link to your work, for example a Github link (this will auto-generate an image) |
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,35 @@ | ||
--- | ||
layout: page | ||
title: Media Strategy | ||
tagline: Jupyter Media Strategy | ||
permalink: /social | ||
--- | ||
|
||
The Jupyter Media Strategy Working Group (JMS) exists to ensure that communications in Jupyter official channels are strategic and benefit Project Jupyter. Please see our [charter](https://jupyter.org/governance/charters/MediaStrategyCharter.html) as and [current list of constituents](https://jupyter.org/governance/people.html#jupyter-media-strategy-working-group) for more information. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Another small typo and wording change request on line 8. Change "as and [current list of constituents]" to "and [current list of members]" There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Fixed |
||
|
||
## Jupyter Blog | ||
The Jupyter [blog](https://blog.jupyter.org) is designed for community members to share valuable, educational content, including news and tutorials, about Jupyter. Please see the Jupyter Media Submission [Guidelines](/media_submissions) for details on creating a post. | ||
|
||
## Jupyter Discourse Forum | ||
The Discourse [forum](https://discourse.jupyter.org) is meant to be a welcoming place for discussion about Project Jupyter. Members are encouraged to ask and answer questions, and highlight wins. If you are interested to be a part of the Jupyter Discourse moderation team, please reach out to us at [email protected]. | ||
|
||
## Social Media Accounts | ||
The JMS maintains a list of official Project Jupyter social media accounts to support and promote our organization's interests. We primarily use our Mastodon account for interactive social media engagement, but will also broadcast messages about the blog or Jupyter events on other channels. | ||
|
||
If you are organizing a Jupyter event or have something Jupyter-related that should be boosted by the official Jupyter account, please reach out to us at [email protected]. Please see our Submission [Guidelines](/media_submissions#blog-social-media-amplification) for more information. | ||
|
||
List of channels actively maintained by JMS in alphabetical order: | ||
|
||
- Discourse: https://discourse.jupyter.org | ||
- LinkedIn: https://linkedin.com/company/project-jupyter | ||
- Medium: https://blog.jupyter.org | ||
- Mastodon: https://hachyderm.io/@ProjectJupyter | ||
- Slack JupyterLab: https://jupyterlabworkspace.slack.com | ||
- X/Twitter Jupyter: https://twitter.com/ProjectJupyter | ||
- YouTube: https://youtube.com/@ipython | ||
|
||
List of channels considered inactive but managed by the JMS: | ||
|
||
- Facebook: https://facebook.com/projectjupyter | ||
- Slack JupyterCon 2023: https://jupyterconworkspace.slack.com | ||
- X/Twitter JupyterCon: https://twitter.com/JupyterCon |
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@blink1073 - I see a typo here. On line 38 instead of this: "to have your Medium account to be added as the writer of the blog."
I want it to say this "with your Medium handle to be added as a writer of the blog."
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed.