kubernetes
Add guide to blog contributions
Add a dedicated section about contributing to the Kubernetes official blogs.
Pull request preview available for checking
Built without sensitive environment variables
| Name | Link |
|---|---|
| Latest commit | aa361ddcd115d7918d3812b2677bfcc47a19280c |
| Latest deploy log | https://app.netlify.com/sites/kubernetes-io-main-staging/deploys/67e3f79b5792df0007a57cbd |
| Deploy Preview | https://deploy-preview-50092--kubernetes-io-main-staging.netlify.app |
| Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
![netlify[bot] avatar](https://avatars.githubusercontent.com/in/13473?v=4 "Published by a pub.dev verified publisher"){kind=small}
I think merging this makes the site overall better (as it stands today), but I intend to polish and squash this PR when I get time.
@sftim I agree with your prior comment and am happy to provide another review once you squash and polish so that we can have these changes merged. Thanks again for putting this together!
I'd intended to write about being a writing buddy. Added, hyperlinked, committed, pushed.
@sftim it might be a good idea to update the SiG-Docs Blog subproject README (https://github.com/kubernetes/community/blob/master/sig-docs/blog-subproject/README.md) adding the distinction between main and maintainer blog, reviewing the existing sections (submit, review and mainenance) to add new details and link to the new pages that will be published after this PR is closed.
What do you think?
@graz-dev I would prefer to hold off on updating the README particularly regarding the maintainer/main blog distinctions, as we're currently in the processes of discussing with ContribEx the idea of merging the two blogs together, and this guide is hoping to serve the purpose of recruiting more reviewers to a combined blog team (alongside the improvements to contributing blogs itself)
@graz-dev I would prefer to hold off on updating the README particularly regarding the maintainer/main blog distinctions, as we're currently in the processes of discussing with ContribEx the idea of merging the two blogs together, and this guide is hoping to serve the purpose of recruiting more reviewers to a combined blog team (alongside the improvements to contributing blogs itself)
@natalisucks ack! It was just to keep the things aligned, but maybe it's better to wait the decision about the future of the two blogs.
/hold
This tries not to make too much change, but at the same time it's size/xxl now and is documenting a policy that's clearly different from what is written down today.
OK to unhold when there is consensus (or lazy consensus) that we should do that.
There's a lot of support for one team; what we do about the two separate index pages isn't yet settled.
with my SIG Docs co-chair hat on, I support these changes. would love to hear from @divya-mohan0209 @reylejano @katcosgrove @salaxander and @tengqm so we can get leadership consensus.
Given KubeCon/CloudNativeCon EU is over, and after a great chat with @lmktfy about moving this forward, I'm adding the required approval from docs. I'd love Contributor Comms or another Docs approver to add their LGTM 👍 /hold cancel /approve
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: natalisucks
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~OWNERS~~ [natalisucks]
- ~~content/en/docs/OWNERS~~ [natalisucks]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
LGTM label has been added.