jupyter / jupyter/jupyter.github.io
Make the Medium blog more discoverable on Jupyter.org
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 208
- Forks
- 205
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 10
Description
Our medium blog is the only formal channel of communication between Jupyter and the outside world. However it is not linked prominently on jupyter.org (EDIT: It is linked under News, I didn't realize this linked to the blog!), and it isn't served as a sub-folder of jupyter.org (e.g. jupyter.org/blog, instead it is blog.jupyter.org) so it doesn't benefit from the same SEO.
I think our blog is pretty important, and we should find more ways to drive attention to it. This will boost our reach, give us more leverage in communications, and connect our website with our primary means of communication.
Suggestion
I'd propose all of the following but if there are strong objections to one of them, would be fine doing only a subset.
- Rename
NewstoBlogso that it's easier to glance (or,Blog & Newsso that it is more noticeable in general?) - Add a list of the last 5 blog posts on the medium blog somewhere on the landing page
- Link the blog from our footer
- Link the blog from the community page
- Link the blog from the jupyter documentation
Inspiration
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the existing News link on jupyter.org, then inspect the landing page, footer, community page, and documentation link locations named in the issue. Decide which proposed blog placements are in scope and verify that the selected links or blog-post listing are visible and point to https://blog.jupyter.org/.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html, jekyll
- Domain
- content, web-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100