Sunday, 7 October 2007

Content Solution - personal experiences

Content Solution 2 is installed simply by uploading files to a new directory and then stepping through a very simple setup routine.

If you have several authors, it can be a good idea to install Content Solution on different domains -- one domain for each author.

Don't run Content Solution with FireFox. I had to resort to Microsoft Internet Explorer to make it run as it should. No problem - as long as you're aware of it.

The Content Solution is OK (not good, but OK) for storing content. I prefer my own CMS with my own MYSQL database for storing content, but if you get used to it, Content Solution will do.

Use Content Solution for fetching text from the internet and then rewriting it by substituting regular words with variables. The sentence "Welcome to Oslo" can easily be altered to "Welcome to [city]", and if the variable [city] has five different values -- voila; you've got five different texts instead of one. Change two words into two different variables, and assign five different values to each variable; and you suddenly have 25 different texts! Shuffle sentences in the text -- and you have texts that are unique enough to pass the Google Duplicate Content Radar.

Content Solution outputs RSS, which can be imported into Blog Solution for further use. This is done on a once-for-all-basis, and everything happens automatically if you've set up everything correctly:

For instance: You create a text in Content Solution that outputs 1024 versions of that text through a RSS feed, with scrambled sentences an' all. Create nine more of those texts within the same theme, and you've got more than 10.000 texts, ready to be publicized. Now Blog Solution comes in handy: Blog Solution publicizes one post every day, just to make sure it doesn't look strange when 10.000 new posts suddenly appear out of the blue.

Content Solution is a bit harder to use than Blog Solution, but the instruction videos are pretty neat and extremely helpful.

[update 2007-10-08] Non-English text: I've tried to scrape and edit text in Norwegian, with only partial success.

First and foremost: You can search and scrape from Google within Content Solution, but you're getting the American English Google results. You cannot localize the various search engines, which make this function somewhat limited. The solution is to search Google outside Content Solution and simply copying the text to Content Solution before you start editing it. But I can live with that.

The editor doesn't support national characters like æ, ø, å, ñ, etc which is the most serious error in Content Solution's editor. Unfortunately, this error makes Content Solution virtually useless for non-English languages.

[update 2007-10-09] One workaround for national characters is to enter the unicode instead of the character itself in Content Solution's editor. This works for me! The same goes for the variables, but there is no need to use national characters in the variable's name.

To replace characters with unicode, you need a conversion table.