-
Notifications
You must be signed in to change notification settings - Fork 417
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
Convert Blogposts to Markdown #36
Comments
To remove html from preview and keep formatting the best idea is to use post excerpt, it requires a little change on the blog.html template. Maybe I could do this on a different PR after all post has been converted. What do you think? |
Well spotted! I agree that doing that would make sense as it's more or less the standard way as far as I know. I'll open another issue for that 👍 |
#36 convert Announcing Global Day Of Coderetreat 2016
#36 convert How to participate in the Global Day of Coderetreat 2016
…r/coderetreat.github.io into jdvr-convert-to-markdow-post4-#36
The following commits have added more blogposts from the archive. They need converting to Markdown as well: 1c08e58 and 94d6ba6 Also, these blogposts might need additional cleanup work, such as:
|
@rradczewski Coudl you please add the new posts to the list and cross the one which have been converted?. I will check the author profile photo, but I think is better to work with the preview on the other issue (#43) |
added the rest. Wow that's plenty 😓 |
What do you think about change the strategy and create a PR for every five post instead of the one PR for each post.? |
Good idea! |
#36 2016 Q1 Nokia Chengdu TC Code Retreat Day
I'd like to quickly talk about the posts and whether we want to keep them on the mainblog at all. I'll bring this up with the other orgas next time we meet, but I wouldn't want you to put so much energy in to posts that maybe aren't relevant anymore. |
As of 13-03-2018, it was agreed that we will indeed try to convert the current html posts to markdown, but only for the ones that really deserve investing effort on. Otherwise, we leave those ones with html format, which implies they automatically become the major "to-be-decommissioned" candidates. |
We want to make it easier to maintain the website. In order to do so, we'd like to convert all pages that don't necessarily need HTML to look decent to markdown.
We expect that this will decrease complexity when making changes to the styles and will help us stick to a general structure when writing new articles.
The blogposts in question are:
The blogposts should keep their overall structure, some breaking changes are fine 👍
We can do this one by one in a PR that is referencing this issue, I'll cross the posts off the list once they'r converted. Netlify will provide us with PR Previews 👍
The text was updated successfully, but these errors were encountered: