8000 [blog] 2018-04-10: Kubernetes blog migration (#8010) · ArduinoBot/website@6ad0160 · GitHub < 6605 link rel="icon" class="js-site-favicon" type="image/svg+xml" href="https://github.githubassets.com/favicons/favicon.svg" data-base-href="https://github.githubassets.com/favicons/favicon">
[go: up one dir, main page]

Skip to content

Commit 6ad0160

Browse files
zacharysarahk8s-ci-robot
authored andcommitted
[blog] 2018-04-10: Kubernetes blog migration (kubernetes#8010)
* Add draft for blog migration post * Small revisions * Most important commit ever * Feedback from kbarnard10 - Turn URLs into hyperlinks - Remove one line * Feedback from sarahkconway - Specify that blog reviews are more transparent/streamlined * Feedback from kbarnard10, part 2 Added "how to submit a blog post" Revised "confidentiality" * Feedback from kbarnard10, part 3 * Renamed file for date accuracy * Changed date back, added email link
1 parent 8ad054c commit 6ad0160

File tree

1 file changed

+36
-0
lines changed

1 file changed

+36
-0
lines changed
Lines changed: 36 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,36 @@
1+
---
2+
layout: blog
3+
title: 'Migrating the Kubernetes blog'
4+
date: '2018-04-10T22:20:00.000-07:00'
5+
author: zcorleissen
6+
---
7+
8+
We recently migrated the Kubernetes blog from the Blogger platform to GitHub. With the change in platform comes a change in URL: formerly at [http://blog.kubernetes.io](http://blog.kubernetes.io), the blog now resides at [https://kubernetes.io/blog](https://kubernetes.io/blog).
9+
10+
All existing posts redirect from their former URLs with `<rel=canonical>` tags, preserving SEO values.
11+
12+
### Why and how we migrated the blog
13+
14+
Our primary reasons for migrating were to streamline blog submissions and reviews, and to make the overall blog process faster and more transparent. Blogger's web interface made it difficult to provide drafts to multiple reviewers without also granting unnecessary access permissions and compromising security. GitHub's review process offered clear improvements.
15+
16+
We learned from [Jim Brikman](https://www.ybrikman.com)'s experience during [his own site migration](https://www.ybrikman.com/writing/2015/04/20/migrating-from-blogger-to-github-pages/) away from Blogger.
17+
18+
Our migration was broken into several pull requests, but you can see the work that went into the [primary migration PR](https://github.com/kubernetes/website/pull/7247).
19+
20+
We hope that making blog submissions more accessible will encourage greater community involvement in creating and reviewing blog content.
21+
22+
### How to Submit a Blog Post
23+
24+
You can submit a blog post for consideration one of two ways:
25+
26+
* Submit a Google Doc through the [blog submission form](https://docs.google.com/forms/d/e/1FAIpQLSch_phFYMTYlrTDuYziURP6nLMijoXx_f7sLABEU5gWBtxJHQ/viewform)
27+
* Open a pull request against the [website repository](https://github.com/kubernetes/website/tree/master/blog) as described [here](/docs/home/contribute/create-pull-request/)
28+
29+
If you have a post that you want to remain confidential until your publish date, please submit your post via the Google form. Otherwise, you can choose your submission process based on your comfort level and preferred workflow.
30+
31+
**Note:** Our workflow hasn't changed for confidential advance drafts. Additionally, we'll coordinate publishing for time sensitive posts to ensure that information isn't released prematurely through an open pull request.
32+
{: .note}
33+
34+
### Call for reviewers
35+
36+
The Kubernetes blog needs more reviewers! If you're interested in contributing to the Kubernetes project and can participate on a regular, weekly basis, send an introductory email to [k8sblog@linuxfoundation.org](k8sblog@linuxfoundation.org).

0 commit comments

Comments
 (0)
0