Git endpoint for content in WordPress

A horrid, crazy idea: a Git endpoint for the content in my WordPress install.

One step back to the problem I’m trying to solve. More and more, I enjoy writing in Markdown with iA Writer. “Publishing” whatever document I’ve written generally involves hitting the Preview button in iA Writer, and then copy and pasting text into WordPress. Yes, the same workflow I’ve been preaching against for years.

I wish I could have a Git checkout of content in WordPress, make edits locally using my editor of choosing, commit, and push back to master. I’m aware of Jeykll and the other hipster “content management systems”, however I’m still an old-school content in a database kind of guy.

Idea: the 30 day challenge (plugin)

Leah just posted a challenge:

https://twitter.com/LeahROlson/status/236940041656627201

Of course I instantly thought: why isn’t there a plugin for this? It would give you prompts on what to write about, possibly based on your previous posts, and reward you for a job well-done (meeting your word count, etc.). A bit like Plinky but built into your dashboard.

Maybe this will be my afternoon hack for Dev Day tomorrow…

Writing beginner level tutorials

Writing beginner level tutorials. A number of useful tips. My favorite: “use words and phrases that your reader can Google to find more information.” For producers of documentation, I think the biggest challenge is putting yourself in the mindset of the reader. The second biggest challenge is closing the feedback loop between the person who has the knowledge and the person who wants the knowledge.

New York Times releases code to help journalists collaborate on WordPress, other platforms

New York Times releases code to help journalists collaborate on WordPress, other platforms. Track changes within the WordPress editor. Code is available on Github; it would be awesome to see this support realtime collaborative editing too. (via Steve Myers)

The History of Dialogue: Other People’s Papers

But not knowing what plagiarism is isn’t really the problem. It’s unfortunate that right now the university is cracking down so hard on plagiarism. And the reason the university is cracking down so hard on plagiarism is because their product is less and less valuable these days. When students plagiarize, there’s an implicit recognition that “I’m just doing this for the grade.” That’s why they do it. And that’s the way that the majority of students look at the university, and have been for some time now. At my college, the frats had rooms full of file cabinets full of plagiarized papers. Plagiarism is old news. It’s really not just that plagiarism is getting easier to do, with the Internet. The problem is now that the grade doesn’t even get you the job.

The History of Dialogue: Other People’s Papers. (via Andrew and Robin)

Tuesday night distraction: Versioned Data Carnival of Journalism

A few days back, Saturday to be exact, the crazy notion I should spend dozens of hours doing content analysis on The Locals came to my mind. For my Carnival of Journalism blog post, I want to paint a clear picture of what university-sponsored hyperlocal journalism is like today. This can then be a foundation for any bushy-eyed speculation I might do about the future.

Sunday evening, I created a Github repository for two reasons: to see how my code is evolving and to track step by step how I’m putting this data together. After all, journalism must be reproducible.

Now that it’s closer to deadline, I want to open the floor. What data points would you like to see established about The Locals? As of right now, I know that the LEV (Local East Village) produced 100 blog posts in November 2010 from 29 authors and 19 community contributors. The FGCH (Fort Greene-Clinton Hill) produced 105 blog posts in November 2010 from 23 authors and 23 community contributors. The rest of the questions I’ve established are in my research notes.

P.S. Another part of the experiment is to see how well Git works as a versioned authoring tool.