Wordpress import for Chyrp

Chyrp is a lightweight blogging engine, written in PHP, working with SQLite and MySQL. It is possible to create different types of posts, e.g. Text, Video, Photo, Link and Quote. It looks like a good open-source alternative for Tumblr.

I currently try out Chyrp, thinking about to replace my private Wordpress blog. The recent Chyrp version includes an option to import content from the Wordpress-XML export file. But it didn’t work for exports from Wordpress.com-Blogs and the default import creates only Text posts in Chyrp, regardless of the post type of the original Wordpress data. So I fixed it and added an additional chyrp module that enables the import of types posts. My Wordpress branch for Chyrp improves:

  • imports from wordpress.com is possible
  • tag import is fixed (only with enabled tag module)
  • category import was added (only with enabled category module)
  • import typed Wordpress posts (link, quote, video, image) to the right Chyrp feathers (link, quote, video, photo) if they are enabled

Unknown post types are still imported as text feather in Chryp, e.g. gallery posts in Wordpress. Currently it is not possible to import them as Photo posts in Chyrp because the photo feather only allows one image per post.

How to import content from Wordpress.com to Chyrp

  1. Go to your Wordpress.com blog dashboard and navigate to the Tools/Export option. Download your data from there as XML and safe it.
  2. In Chyrp you need to enable the module “Wordpress Post Types Importer” and the Link, Quote, Photo and Video feathers.
  3. In Chyrp you go to Manage/Import and:
    1. choose your Wordpress-XML export file as import data
    2. fill in the URL prefix that was used in to link media (images) in the Wordpress posts. For WP.com it probably is: http://{{yourblogname}}.files.wordpress.com/
  4. Wait for the success message.
  5. Check Manage/Posts to control the import.

That’s it.

rel=”source” might be not so awesome! We already have alternative options.

Today I’ve learned from The Cangelog news blog about Jeremy Keith’s proposal to add a relation between a project/document and its souce code by using rel="source" somewhere in the HTML markup. Sounds good, but it would only be a unspecific relation between a document or project or whatever and something related to some unspecific type of source code container :) I really miss the improved semantics here. And we already have options to describe it.

Keith wrote:

I got chatting to Aral about a markup pattern that’s become fairly prevalent since the rise of Github: linking to the source code for a website or project. You know, like when you see “fork me on Github” links. […] We were talking about how it would be nice to have some machine-readable way of explicitly marking up those kind of links, whether they’re in the head of the document, or visible in the body. Sounds like a job for the rel attribute, I thought. […] I’ve proposed rel=”source”.

The “fork me on Github” link has at least 3 different meanings:

  1. the website of a software project contains a relation to the public source code repository of the software
  2. the link points to a repository where the content of the webseite is managed, this link is the same on all pages of the website
  3. the link points to the related source of the currently shown page deep in the repository

A human can see the difference, a machine not. If we add code to markup to make the relation machine-readable, a rel="source" wouldn’t do the job. A machine really needs a very clear description about “X has a relation to Y”, the machine need to know about X, Y and the relation. A machine needs a object, a predicate and a subject to understand the fact.

Lack of the object

The brainstorming page about rel="source" at the Microformats wiki describe the use case as:

When an author links to a project’s (or document’s) source code (e.g. on GitHub, Google Code, etc.) a rel value of “source” could be used to explicitly define that relationship.

It already describes the problem: is it the source code of the (software) project or is it a link to the source code of the document (content of the webpage)? X (the object) is not defined here, a simple rel="source" do not imply entailment, there is no logical consequence. Machines would have to guess what the object is.

Lack of the subject and its type

While there is a discussion about the label on the brainstorming site, a machine only cares about the semantical meaning, “sfuzcfzcsz” could be the name of the property that relate a software project to it’s download archive. rel="source" don’t say anything about the subject or its type, it only describes that the related resource has to do something with source code.

  • Is it the source code in a zip/tar/xyz archive?
  • Is it a file containing uncompressed source code?
  • Is it a repository address you can checkout or clone from? Is it Git, Mercurial, SVN, …?
  • Is it a relation to the homepage of a code repository (e.g. most Github links)?
  • Is the link about a special version, branch, tag of the source code?

Where to put the relation in?

You may able to use rel="source" on a meta and anchor element in HTML. Please try to use it on a PNG image — e.g. a computer generated fractal — to describe a relation to the source code of the generating program. Good luck! There is no Microformat vocabulary to wrap it in. Leads to the next problem:

What about listings?

If you have a listing of software projects on one webpage, how can we set the correct relations. Using rel="source" multiple times on various links? A machine would only see multiple source relations on one HTML document because currently there is no proper vocabulary in MF1 and MF2 that you can use to describe the software project or web document, maybe h-item but according the spec “h-item is almost never used on its own.”

Already existing and working alternatives

According to a “rel usecase repository”, Keith writes:

The benefit of having one centralised for this is that you can see if someone else has had the same idea as you. Then you can come to agreement on which value to use, so that everyone’s using the same vocabulary instead of just making stuff up.

Good advice :) There are alternative options developed by the RDF and Microdata communities, developed months or years ago:

  • The DOAP project “create an XML/RDF vocabulary to describe software projects, and in particular open source projects.” The DOAP vocabulary provides properties like repository and more to describe relations to Repositories, Downloads, Wikis, Issue Lists and a lot of more stuff. You can add DOAP to your HTML via RDFa and Microdata.

  • The schema.org vocabulary provides concepts like CreativeWork, SoftwareApplication, Code and properties like codeRepository and downloadUrl, also useable in you HTML markup via RDFa and Microdata syntax.

  • Update (Feb 21): there is already a rel-vcs Microformat that is used and supported by various tools. But t is not listed in the “the official registry for rel values.” Of course it shares most of the problems with rel-source regarding semantics.

We don’t need to live in a religious Microformats-centric world with the Microformats wiki as your bible. :) And rel="source" would be probably not so awesome because:

  • it does not add enough semantics that machines can understand the correct fact
  • there are already alternatives that work

#CSSOff 2013: Markup Mayhem or Closed Design Disaster?

The CSSOff competion 2013 started today. And I got bitterly disappointed. And it seems I’m not the only one after I read the #cssof tweets. Some of the guys criticize mainly the design.

Me not. In my opinion it doesn’t matter if we find the design beautiful and eye candy. Everyone has different preferences. The design is some kind of poster and magazine style that has been (or is) trending recently. It looks close to a print product. This isn’t a problem because CSSOff is done to get challenged at a very high cutting edge level. Transferring this layout to the web keeping the document accessible and good structured, this is really a challenge and fun because we could try out all the new techstuff we usually can’t use in payed client projects.

I am disappointed because the sources of the competition are closed source and not accessible to everyone. And it may imply some legal problems, too (at least in some countries). One of the CSSOff rules is to build on open and standardized technologies like HTML, CSS and Javascript. But you need closed commercial software to work with the layout source: it’s a Photoshop file. Damn it! This is a problem.

PSD templates mostly suck, this too: The usage and layering in the PSD file contains all the “nice” stuff that is hated by developers, e.g. weak names for the layers (I can’t see if it uses layer groups as I don’t have Photoshop) and filter effects not rendered to raster graphics (at least as layer copy).

Dependence on closed commercial software: if you don’t own a copy of Photoshop you can’t access the PSD file format. The sources come with PNG as fallback but this is a joke. It is a flat image without any other informations. If you don’t have the correct version of Photoshop you could run into problems. If your PS version don’t support the right layer effects, you have a problem. If you use another software to open PSD files but that software lacks full PSD support, you simply can’t work with the sources. Check the difference between the fallback PNG (right) and the PSD file opened in Gimp (left):

CSSOff Closed Design Disaster

Other words needed what the problem is about?

The source archive don’t includes layout annotations and raw data: it only contains the PSD, the PNG fallback and a very small Readme file. The only useful information is about the used Google Webfonts. No annotations about used font sizes, weights and lineheights, no info about the grid, no raw/single/retina versions of the used images, no text file with the text blocks used in the layout, no info about used angles on rotations, nothing. Only the useless __MACOS meta folder so everyone can see that someone owns an Apple machine. Probably you really need Photoshop to get your hands on all this important facts. Some attenders filled the gap and provide info on used fonts, source images and texts.

The sources are not free (as in freedom): this is really a problem because the competition terms demand that all results have to be submitted under a Creative Commons CC-BY license. We would need also sources under a free license for that. Propably all images from the layout stay under copyrights and they are not released under a free license. There is no picture old enough that it could be under public domain. I don’t think that product images (barbie box, transformers bluray) are under CC-BY, same for the altered Abbey Road cover (barcode instead of cross-walk stripes) by the Beatles or the stock photographs. You only can get free usable results on free useable sources, and free as in freedom, not as in free beer. You can’t use everything that you can copy for free from web, at least not in a open competiton asking the attenders to illegaly claim other copyrights.

Probably there are some more critical issues with the layout resources but my points above are enough for now.

I wish everyone good luck with the competition. I would like to attend but I don’t have full access to the sources because I use Linux and don’t own a copy of Photoshop. This is sad because the layout is technically complex enough that it could have been a good play with all the nice cutting edge tech. But it is graphically not overcomplex, it could have been easily done with Inkscape and images really released under CC-BY.

Evaluate User Feedback!

> Many years ago now Google actually paid for a usability study for one of the features I was speccing (microdata) and it was absolutely fascinating to see how people’s actual performance was so divergent from their impressions. We’d ask them questions like “which would be simpler, this or this” and then we’d actually test them by having them use the options, and there was just no relationship between what people said they wanted, and what people were actually able to use.

> Often when people send feedback (not just authors, pretty much anyone who hasn’t been in the process for a long time starts this way) they send feedback along the lines of “I want to add feature X” or “I want feature X to be extended in manner Y”. But when we drill down, ask them “what problem are you trying to solve”, or “what’s your use case” (same question but phrased differently), we often find that either (a) they actually don’t have a real problem, they just thought that it would be a good idea, or (b) their solution wouldn’t actually solve their problem. Often we’re able to come up with much simpler solutions (or point to already-existing solutions), which is quite satisfying.

> Interview with Ian Hickson, HTML editor (html5 Doctor)

(Source: twitter.com)

Software Wars: movie about how free software will save the world

> The average computer user is unaware there is a war for freedom going on that will determine the path of modern society. Software Wars is a movie about the battle for our right to share technology and ideas. This software will not be ‘owned’ by corporations like Microsoft, Apple, and Google, who are mostly impeding technological progress.Source: Software Wars @ indiegogo

> The main producer is Keith Curtis, a Seattle-based author and programmer who spent 11 years at Microsoft before being converted to the world of Linux and open-source software. The movie is based on a portion of Curtis’ book, “After the Software Wars,” but he’s working on the project with an extensive virtual team out of L.A. — Source: GeekWire

I already had Curtis’ book from 2009 on my list “20 Free Books on Linux, Open Source Software & Philosophy.”

I wondering if that movie is going to be a objective documentary about the subjects Free Libre Open Source Software (FLOSS) and proprietary systems. I guess it won’t be like that. But at least it could be a movie nice to watch, and it can be used in campaigns for free software projects and as an opposite to proprietary software campaigns that people usually watch every day at TV/commercial breaks.

So let us support the crowdfunding campaign of Software Wars.

SEO improvements with Google Data Highlighter?

Semantic enhancements and structured data on websites helps to improve your SEO. Usually you use Microformats, Microdata and RDFa/Lite for it but you (or your developers) have to learn the syntax markup and vocabularies first. Now, Google added the Data Highlighter to the webmaster tools: a point-and-click tool that helps you to “show Google patterns of structured data on your website without modifying your pages.”

Google loves structured data because they use it to get more information about your content, better understanding of you content could improve your ranking in search engines. Google pushed a lot of initiatives to invite website owners to create more structured data:

All these initiatives depends on webmasters and developers who are able to add special markup to their pages. The Data Highlighter now “improves” that process because you can use a point-and-click tool to describe your actual content, no markup additions are necessary.

This makes things easier but could harm the web ecosystem because if you use the Data Highlighter to describe your content then only Google knows this description. This may help you to rank your site better in Google but it puts you in a situation with strong dependencies on Google. No other search engine provider like Bing, Yahoo or Yandex can use that structured information, no other indepentent tool can see those semantic enhancements. Second, if you change your site structure and markup you need to perform the Data Highlighter tool again on your website, even if it still contains the same data.

Test and use the Data Highlighter (be aware: it currently only works with events! Do not define your shop items as events :) ), use it to learn what Structured Data is and how it can help to improve your business, but please don’t rely only on this tool. Learn how to add structured data and semantic enhancements directly to your website (or just pay someone who knows how to do it), long term this will perform better.

(Source: googlewebmastercentral.blogspot.de)

Developers advent: Snow on the dev floors and 24 new web doors … ‘til Christmas

The blog is back, maybe without a bang but with some advent calendars for developers:

  • 24 Pull Requests is a little project to promote open source collaboration during december. The idea is basically “Send a pull request every day in december leading up to Christmas”, encouraging developers to give back to open source with little gifts of code throughout december.
  • 24 ways is the advent calendar for web geeks. Each day throughout December we publish a daily dose of web design and development goodness to bring you all a little Christmas cheer.
  • Performance Calendar: The speed geek’s favorite time of the year
  • Web Advent 2012: Join us each day as our wonderful authors provide presents of tips, tricks, & tidbits to usher in the new year.
  • Perl Advent Calendar 2012: twenty four merry days of Perl
  • Seit 2005 ist es gute Tradition jedes Jahr aufs neue, einen Webkrauts-Adventskalender mit interessanten Themen von CSS3 und SASS über Wireframes und Tools hin zu SEO, Barrierefreiheit und dem mobilen Web zu füllen.

Looks like we got some more advent calendars for web designers and developers last year, the PHPadvent (now webadvent) seems not to be ready this year.

Please contribute your suggestions if you know other calendars for developers.

End Software Patents: Marginal Revolution writer and George Mason economics professor Alex Tabarrok argues for an end to software patents.

(Source: fsf.org)

PubwichFork 2.1 released

7 months after version 2.0, the new PubwichFork 2.1 comes with improved support for responsive mobile layouts and updated social media service classes.

After saving original Pubwich from death, PubwichFork 2.0 was downloaded appr. 350 times, installs from the repository not included, it attracted attention in some weblogs for web developers, PubwichFork powered sites were shown on barcamps and featured in a professional journal.

Now PubwichFork 2.1 comes with some minor but nice improvements.

Download and installation

That’s easy! Just download the PubwichFork 2.1 archive (we provide Zip and Tar), unpack it in your webspace and follow the config instructions from the manual.

Improvements made in PubwichFork 2.1

Check the changelog for a detailed list of changes.

Links

About PubwichFork

PubwichFork aggregates your latest Social Web and Social Media content across multiple service websites, e.g. your Twitter stream or Flickr photos. Then it renders one single website featuring all your content. PubwichFork is written in PHP and licensed Open-Source under a GPL.

PubwichFork was featured in WebResourcesDepot, La Ferme du Web, PHPspot and Hot Scripts Blog. (only to ping that sites about this realease :)

Zend Framework 2

A little bit more than a month ago Zend Framework 2 stable finally has be seen the light, after all the years of development it was finished earlier than the new Berlin Airport, a never ending story and source for jokes :)

Zend put a new website online and used new URIs for downloads but it seems that they forgot to set redirects, so some install routine of Zend Framework enabled software had to get updated.

Everyone who wants to dive into the new version of the well known PHP framework, check out those nice resources out there:

Since the first release of ZF2, the developer community released two more minor bugfix releases: recent version is 2.0.2.