-
Notifications
You must be signed in to change notification settings - Fork 160
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
Publish blog from website rather than Medium? #281
Comments
seems like a good idea to me - a quick search suggests it shouldnt be too hard to migrate medium -> jekyll i guess the main advantage of using medium is the connection/discovery that comes with it |
No objection from me if someone is willing to do the work! |
i can pick this up as i have time |
@phlax - great! Was you plan to migrate the posts and "close" the Medium site? FYI, OpenTelemetry did a similar switch from Medium to a webiste-local blog. For OTel we chose to make "placeholder" entries for all posts that were already on Medium, rather than copy them over. For example see:
You might then want a short post on Medium to let folks know that the blog has officially moved. |
i was wondering about this - whether we can redirect existing articles to new - otherwise yep lets add a placeholder etc |
relatedly - i checked and the medium pages seem to use the envoyproxy domain for links so im hoping there is not SEs with any medium URLs that we need to worry about - i think its mostly a case of keeping the discoverability on medium - which then leads to the question of whether to publish placeholders for new articles quite busy atm, but ill keep thinking on it and take a look further once the current round of Envoy releases is out of the way |
The blog is currently hosted on Medium at blog.envoyproxy.io. Might it make sense to repatriate the blog entries into the website? A website-repo local blog usually makes for a much more active blog: it becomes easier for community members to submit posts via PRs.
Thoughts @phlax @mattklein123?
/cc @nate-double-u @caniszczyk
The text was updated successfully, but these errors were encountered: