cdfoundation
Assess the Blog platform use tool like - dev.to as the CDF blog post platform.
Advantages in terms of centralized content to engage people on the topic also use the API https://developers.form.com/api
The link to the API is broken. Is this a suggestion to replace Wordpress?
We discussed a more open approach to blogging but opted to not change our process for the time being.
Not sure we need a tool just yet. A google sheet for a handful of blogs as a backlog grooming and Google docs is simple and should works well for working on blog with 1-X number of people on the blog. Once a blog topic finalized then drop in the CDF board for tracking.
@zestyroxy I think the API URL is - https://developers.forem.com/api.
Google Docs could be a good start for collaboration as @robertjahn called out. One card in the kanban board can track the progress.
It might be worthwhile to find a way to commit the publish-ready article to git and use some CC/CD pipeline to deploy it under cd.foundation domain
@safeercm Git is not ideal to copy edit articles.
Blog ideas and progress can be tracked on the Kanban board, but the content should be sent to the editor (me) in a text file, ideally in GDocs. It's much easier to comment and edit articles in a proper text editor. Git would not speed up this process since I need to vet every article on behalf of the CD Foundation.
Here are the blog guidelines: https://github.com/cdfoundation/foundation/blob/master/blog-guidelines.md And the submission form: https://cd.foundation/cdf-blog-submission-form/
@zestyroxy I was suggesting a git-based workflow for deploying the blogs after the final editorial review, not for collaboration or review. For collaboration, Google Docs would be a good starting place.
What would be the benefit of changing the process to deploy the blogs?