Blog | Create separate content repository

[j12y]

It's not much of an issue now, but we could pull markdown files for blog posts, tutorials, etc. from a second repository so that we are not intermingling code updates with content requests / efforts.

for instance, a second repository:
https://github.com/devrel-foundation/site-content

[anajsana]

@j12y I’d like to understand the motivation behind this. Have there been any feedback from the community about this? 🙂

I’m generally a fan of keeping the number of repositories to a minimum, so my preference would be to use issue templates to guide contributors when submitting content and manage the review process through a tagging system instead (e.g., pending review, approved, declined, etc)

[j12y]

Have there been any feedback from the community about this?

Nope, no feedback one way or the other.

I’d like to understand the motivation behind this.

Benefits for Authors

• less complexity on where to put markdown files

Benefits for Reviews

• review process (labels) that would be appropriate for content rather than for web development and content

Benefits for Dev

• reduce merges related to content when making web changes (including page copy)