Klaus' Korner

As I mention last month, I started to seriously think of switching over from Enki to WordPress. I do like Enki, but the fact that I have limited time to maintain the code as well as write postings is a major reason. In addition since I now have a iPad and there is a iOS app that allows me to maintain the blog from anywhere, I just can not resist…

I realized that since switching my site to the new Enki based software that Google stopped indexing the site’s pages. Thinking about the cause I came up with the conclusion that because all the pages and blog articles are dynamically generated it would take ages for them to end up in the indexes of search engines. What I needed was a way to help the search engines by adding a…

Updated – March 25, 2011 – The article has been modified to also be relevant to WordPress. For what ever reason the Enki creator forgot that for the XHTML 1.x Strict recommendations the W3C no longer include the target attribute of the <a> tag. The simple fix would be to use the Transitional version since it still includes it, but since this specs is depreciated, one should stay away from…

I notice that the main page (home page) displays the full article content for each posting. Looking at the code revealed that the only adjustment available via the configuration file was the number of articles on the main page, not the length for a summary of each article.

The main reason for the new look is that I decided to switch from RapidWeaver (RW) to Enki. Basically I became tired of creating my blog articles in RW, compiled the pages and uploaded the complete set of pages to the hosting site. Don’t get me wrong RW makes it ridiculously easy to create stunning websites, but for the use as a blog engine, like other web design tools, the…