\n<\/span><\/a>Gist – WordPress Sync<\/h1>\nThis is a tale of how this very section – hacks.ash.wine<\/a> works.<\/p>\nI \u2764\ufe0f<\/g-emoji> Gists<\/a>, and I have a habit of posting small stuff\/code\/discoveries\/guides etc. up there so I can revisit them later. (All of my public gists : https:\/\/gist.github.com\/Ashwinning<\/a>)<\/p>\nAdditionally I use Gistbox<\/a>, which allows me to categorize\/add labels to my gists and find search through them faster.<\/p>\n![\"\"](\"https:\/\/camo.githubusercontent.com\/fab3e84160b1bf7e718f77c53b85114f92ac5073\/68747470733a2f2f692e6779617a6f2e636f6d2f66303933373563393764623665636436353638353033363461616530343034652e706e67\")
<\/a><\/p>\nBut not all my gists are important, and most of them aren’t useful for other people, so I wanted to archive all the ones that could be potentially useful for others at hacks.ash.wine.<\/p>\n
\n<\/span><\/a>Problems and Solutions<\/h2>\nThis could have been solved easily by creating a Jekyll repository at Github, and posting stuff there in markdown, but I like being able to have separate Gist repositories for separate things.<\/p>\n
That too could be solved by writing a small script to sync my gists with the jekyll, but then
\n1. I’d have to port the WordPress theme\/CSS\/etc to a jekyll blog.
\n2. Redo changes to the theme header & footer every time it changed on the wordpress site.
\n3. I wouldn’t be able to keep multiple files in their own git repo for each ‘hack’.<\/p>\n
Also, I’ve had bad luck with Jekyll (on docker on Windows)<\/a> before.<\/p>\n\n<\/span><\/a>The Original Solution<\/h2>\nTo do this, originally, I created a Python script<\/a> which would go through all my gists, then all my WordPress posts, then compare if there were any gists that hadn’t been posted to WordPress yet, and post those.<\/p>\nThe script searches for a #gistblog<\/code> hashtag in the gist description to identify if a gist should be synced, the rest of the hashtags as passed on as WordPress tags, the remaining gist description is used as the WordPress post title.<\/p>\n![\"\"](\"https:\/\/camo.githubusercontent.com\/5f280c4ecfd3f4daffcc32c7686bfb67f0d3c7dd\/68747470733a2f2f692e6779617a6f2e636f6d2f66303731636639663436363031336466313264316630393731336637356332662e706e67\")
<\/a><\/p>\nAs far as the post content itself was concerned, the script simply posted the gist url as the body of the WordPress post, and let wordpress handle the embedding.<\/p>\n
It worked out pretty well actually! Here’s an example of what an embedded post looks like : http:\/\/ash.wine\/what-a-gist-embed-looks-like\/<\/a><\/p>\n\n<\/span><\/a>The Problem<\/h2>\nThere’s a big problem with this approach – SEO.<\/p>\n
There’s a chance that Google cannot see\/will not index the asynchronously loaded content of the gist.<\/p>\n
Well, what’s the point of aggregating content for others, if other can’t find it when they need it?<\/p>\n
\n<\/span><\/a>Introducing Gist-Wordpress-Sync 2.0<\/h2>\nThe new approach is an iteration over the previous one, but with a couple of new features:<\/p>\n
\n- The application now requests the raw content of each tagged gist, runs it though the Github Markdown Parsing API<\/a>, and posts the rendered HTML content to WordPress as the post’s body.<\/li>\n
- It stores the gist’s
id<\/code> and updated_at<\/code> attributes as WordPress custom_fields<\/code> with every post (to track and update posts).<\/li>\n- Abstracts configuration settings into a
.settings<\/code> file so the script can be easily configured for other blogs.<\/li>\n<\/ol>\nThe biggest downside is that since WebHooks don’t work for Gists, the application has to be manually run when changes are made to Gists.<\/p>\n
It is still very<\/strong> rough around the edges, and may require tweaking for it to fit your taste\/preferences, and the configuration of your WordPress blog.<\/p>\nThe repository is available here : https:\/\/github.com\/Ashwinning\/Gist-Wordpress-Sync<\/a><\/p>\n
I Additionally I use Gistbox<\/a>, which allows me to categorize\/add labels to my gists and find search through them faster.<\/p>\n But not all my gists are important, and most of them aren’t useful for other people, so I wanted to archive all the ones that could be potentially useful for others at hacks.ash.wine.<\/p>\n This could have been solved easily by creating a Jekyll repository at Github, and posting stuff there in markdown, but I like being able to have separate Gist repositories for separate things.<\/p>\n That too could be solved by writing a small script to sync my gists with the jekyll, but then Also, I’ve had bad luck with Jekyll (on docker on Windows)<\/a> before.<\/p>\n To do this, originally, I created a Python script<\/a> which would go through all my gists, then all my WordPress posts, then compare if there were any gists that hadn’t been posted to WordPress yet, and post those.<\/p>\n The script searches for a As far as the post content itself was concerned, the script simply posted the gist url as the body of the WordPress post, and let wordpress handle the embedding.<\/p>\n It worked out pretty well actually! Here’s an example of what an embedded post looks like : http:\/\/ash.wine\/what-a-gist-embed-looks-like\/<\/a><\/p>\n There’s a big problem with this approach – SEO.<\/p>\n There’s a chance that Google cannot see\/will not index the asynchronously loaded content of the gist.<\/p>\n Well, what’s the point of aggregating content for others, if other can’t find it when they need it?<\/p>\n The new approach is an iteration over the previous one, but with a couple of new features:<\/p>\n The biggest downside is that since WebHooks don’t work for Gists, the application has to be manually run when changes are made to Gists.<\/p>\n It is still very<\/strong> rough around the edges, and may require tweaking for it to fit your taste\/preferences, and the configuration of your WordPress blog.<\/p>\n The repository is available here : https:\/\/github.com\/Ashwinning\/Gist-Wordpress-Sync<\/a><\/p>\n![\"\"](\"https:\/\/i.gyazo.com\/f09375c97db6ecd656850364aae0404e.png\")
\n<\/span><\/a>Problems and Solutions<\/h2>\n
\n1. I’d have to port the WordPress theme\/CSS\/etc to a jekyll blog.
\n2. Redo changes to the theme header & footer every time it changed on the wordpress site.
\n3. I wouldn’t be able to keep multiple files in their own git repo for each ‘hack’.<\/p>\n\n<\/span><\/a>The Original Solution<\/h2>\n
#gistblog<\/code> hashtag in the gist description to identify if a gist should be synced, the rest of the hashtags as passed on as WordPress tags, the remaining gist description is used as the WordPress post title.<\/p>\n![\"\"](\"https:\/\/i.gyazo.com\/f071cf9f466013df12d1f09713f75c2f.png\")
\n<\/span><\/a>The Problem<\/h2>\n
\n<\/span><\/a>Introducing Gist-Wordpress-Sync 2.0<\/h2>\n
\n
id<\/code> and updated_at<\/code> attributes as WordPress custom_fields<\/code> with every post (to track and update posts).<\/li>\n.settings<\/code> file so the script can be easily configured for other blogs.<\/li>\n<\/ol>\n