<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE rss [<!ENTITY % HTMLlat1 PUBLIC "-//W3C//ENTITIES Latin 1 for XHTML//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml-lat1.ent">]>
<rss version="2.0" xml:base="https://diaryproducts.net">
<channel>
 <title>Diary Products - Hannes Schmidt - CMS</title>
 <link>https://diaryproducts.net/taxonomy/term/12/all</link>
 <description></description>
 <language>en</language>
<item>
 <title>Drupal vs. Wordpress</title>
 <link>https://diaryproducts.net/about/cms/drupal/drupal_vs_wordpress</link>
 <description>&lt;p&gt;A close relative of mine asked me to help him with choosing, installing and maintaining a blog for him. I am a big fan of Drupal (the software behind this blog, in case you were wondering) but just couldn&#039;t bring myself to recommend it. Don&#039;t get me wrong, Drupal is IMHO superior in almost all technical aspects but its user interface is just not as easy to use as WordPress. The person in question being a fairly inexperienced user of web technologies, usability was a major concern. The result can be admired at &lt;a href=&quot;http://hartwigschmidt.name/&quot;&gt;Hartwig Schmidt&lt;/a&gt;&#039;s blog.&lt;/p&gt;
</description>
 <category domain="https://diaryproducts.net/exactly/about/cms/drupal">Drupal</category>
 <category domain="https://diaryproducts.net/exactly/for/webmaster">Webmaster</category>
 <pubDate>Mon, 01 Dec 2008 01:46:55 +0000</pubDate>
</item>
<item>
 <title>Relaunch of Diary Products</title>
 <link>https://diaryproducts.net/about/cms/drupal/diary_products_relaunch</link>
 <description>&lt;p&gt;&lt;span class=&quot;meta anchor&quot;&gt;[&lt;a href=&quot;#update1&quot;&gt;02/28/2005: Update - More Changes&lt;/a&gt;]&lt;/span&gt;&lt;br /&gt;
&lt;span class=&quot;meta anchor&quot;&gt;[&lt;a href=&quot;#update2&quot;&gt;03/02/2005: Update - Still Bugs in IE&lt;/a&gt;]&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;After this site has been using the old, boring, standard Drupal theme for two years, I am now proud to present my own creation: the new Diary Products theme. It uses the phptemplate engine and is a hybrid between table-based and CSS-based layouts as I am not a follower of the pure &quot;Look Ma, No Tables&quot; approach. There are still a few glitches here and there but overall I am quite happy with it.&lt;/p&gt;
</description>
 <category domain="https://diaryproducts.net/exactly/about/cms/drupal">Drupal</category>
 <category domain="https://diaryproducts.net/exactly/about/web_servers/lighttpd">LightTPD</category>
 <category domain="https://diaryproducts.net/exactly/for/geek">Geek</category>
 <category domain="https://diaryproducts.net/exactly/for/webmaster">Webmaster</category>
 <pubDate>Tue, 28 Feb 2006 18:34:08 +0000</pubDate>
</item>
<item>
 <title>Typo3 and CSS: Style Your Pages based on their Alias or UID</title>
 <link>https://diaryproducts.net/about/cms/typo3/css_style_page_alias_uid</link>
 <description>&lt;p&gt;If you look at all the pages of a particular site, you will notice that most pages share common parts. These common parts typically include navigation, header, footer, styles and so on. Of course, you can duplicate the common part in every html file on that site. But as the site grows, making a change to one of the common parts ends up in a lot of tedious work: you need to apply the change to every single HTML file on the site. Now imagine your site has 1000 pages! You don&#039;t want to do that.&lt;/p&gt;
</description>
 <category domain="https://diaryproducts.net/exactly/about/cms/typo3">Typo3</category>
 <category domain="https://diaryproducts.net/exactly/for/webmaster">Webmaster</category>
 <pubDate>Wed, 23 Mar 2005 19:46:49 +0000</pubDate>
</item>
<item>
 <title>Typo3: The Split Site Root Syndrome</title>
 <link>https://diaryproducts.net/about/cms/typo3/canonical_home_page_split_site_root</link>
 <description>&lt;div style=&quot;float:right&quot; class=&quot;thumbnail&quot;&gt;
  &lt;a href=&quot;/node/21&quot;&gt;&lt;img src=&quot;/img_assist/gen/21&amp;amp;thumb=1&quot; width=&quot;100&quot; height=&quot;77&quot; alt=&quot;The Split Site Root Syndrome&quot; /&gt;&lt;/a&gt;
&lt;/div&gt;&lt;p class=&quot;meta&quot;&gt;[continued from &lt;a href=&quot;/about/cms/typo3/home_page_menu_navigation&quot;&gt;Typo3: Including the Home Page (Site Root) in Navigation&lt;/a&gt;]&lt;/p&gt;
&lt;h2 class=&quot;title&quot;&gt;The Problem&lt;/h2&gt;
&lt;p&gt;For months, my client&#039;s site was running fine using the above
      simple solution. Over time though, I noticed several oddities. These oddities
      were caused by the fact that the home page is accessible under two URLs, the
      canonical root &lt;code&gt;http://www.domain.com/&lt;/code&gt; and
      the non-canonical root &lt;code&gt;http://www.domain.com/home.0.html&lt;/code&gt; as
    shown in the figure below.&lt;/p&gt;</description>
 <category domain="https://diaryproducts.net/exactly/about/cms/typo3">Typo3</category>
 <category domain="https://diaryproducts.net/exactly/for/webmaster">Webmaster</category>
 <pubDate>Wed, 05 Jan 2005 23:32:19 +0000</pubDate>
</item>
<item>
 <title>Typo3: Including the Home Page (Site Root) in Navigation</title>
 <link>https://diaryproducts.net/about/cms/typo3/home_page_menu_navigation</link>
 <description>&lt;p&gt;In modern web design, it is considered good practice to have
      a &amp;quot;Back To Home&amp;quot; link on every page so that users can
      easily return to the root of the site, i.e. the home page. Because of that
      I wanted a Home button on every page of my client&#039;s Typo3-based website. Although
      this seems like a very simple thing to do, it turned out to be quite a challenge
      in Typo3, especially when trying to avoid duplicate content penalties induced
      by major search engines.&lt;/p&gt;</description>
 <category domain="https://diaryproducts.net/exactly/about/cms/typo3">Typo3</category>
 <category domain="https://diaryproducts.net/exactly/for/webmaster">Webmaster</category>
 <pubDate>Wed, 05 Jan 2005 21:30:09 +0000</pubDate>
</item>
<item>
 <title>Typo3: Different CSS styles for internal and external links</title>
 <link>https://diaryproducts.net/about/cms/typo3/css_style_internal_external_link</link>
 <description>&lt;p&gt;It&#039;s often considered convenient to decorate external links in order to indicate the distinction between links that go to a page on the same site and links that leave the site. On one of my sites I use CSS to set a background bitmap for all links. Until today the bitmap was the same for internal as for external links. I used a little hack in order to set the class attribute of internal links to some value while leaving external links untouched.&lt;/p&gt;</description>
 <category domain="https://diaryproducts.net/exactly/about/cms/typo3">Typo3</category>
 <category domain="https://diaryproducts.net/exactly/for/webmaster">Webmaster</category>
 <pubDate>Mon, 27 Dec 2004 15:14:19 +0000</pubDate>
</item>
<item>
 <title>Single-Sign-On for Zope &amp; Plone in Windows Domains</title>
 <link>https://diaryproducts.net/about/cms/zope_plone/zope_plone_sso_single_sign_on_windows_domain</link>
 <description>&lt;div style=&quot;float:right;margin:1em&quot;&gt;&lt;a href=&quot;/node/16&quot;&gt;&lt;img src=&quot;/img_assist/gen/16&amp;thumb=1&quot; width=&quot;100&quot; height=&quot;71&quot; alt=&quot;Single-Sign-On for Zope &amp; Plone in Windows Domains: SSO&quot; /&gt;&lt;/a&gt; &lt;/div&gt;
&lt;div style=&quot;float:right;margin:1em&quot;&gt;&lt;a href=&quot;/node/14&quot;&gt;&lt;img src=&quot;/img_assist/gen/14&amp;thumb=1&quot; width=&quot;100&quot; height=&quot;78&quot; alt=&quot;Single-Sign-On for Zope &amp; Plone in Windows Domains: Remote User Folder&quot; /&gt;&lt;/a&gt; &lt;/div&gt;
&lt;p&gt;One of my clients runs his own intranet for his employees. The intranet currently
  consists of a bunch of static HTML pages which are written and maintained by a
  single editor. This approach might have been sufficient five years ago but as the
  intranet grew it became apparent that the static HTML would become unmanageable
  in the near future. I therefore suggested replacing the existing solution with
  a community-oriented CMS. Due to certain requirements the set of contestants was
  cut down to two: &lt;a href=&quot;http://www.drupal.org/&quot;&gt;Drupal&lt;/a&gt; and &lt;a href=&quot;http://www.plone.org/&quot;&gt;Plone&lt;/a&gt;.
  I favored Plone because a) I am slightly disappointed with the direction and pace
  that Drupal&amp;rsquo;s development has recently taken and b) I wanted to learn &lt;a href=&quot;http://www.zope.org/&quot;&gt;Zope&lt;/a&gt; and
  Plone anyway. &lt;/p&gt;
</description>
 <category domain="https://diaryproducts.net/exactly/about/cms/zope_plone">Zope/Plone</category>
 <category domain="https://diaryproducts.net/exactly/for/webmaster">Webmaster</category>
 <enclosure url="https://diaryproducts.net/files/GroupUserFolder.py-3.3.patch.bz2" length="697" type="application/x-bzip2" />
 <pubDate>Sat, 18 Dec 2004 21:22:37 +0000</pubDate>
</item>
<item>
 <title>Typo3: Using Page Alias And Other Page Record Fields in TMENU Menus</title>
 <link>https://diaryproducts.net/about/cms/typo3/page_alias_tmenu</link>
 <description>&lt;p&gt;Problem: Your web site uses the Typo3 CMS. Your typoscript templates contains TMENU objects for navigation menus. You want to use the page alias somewhere in the &lt;code&gt;A&lt;/code&gt; tags of these TMENU menus. For example, you want to set the id of a menu item&#039;s A tag to the alias field of the page that the menu item stands for.&lt;/p&gt;
&lt;pre&gt;
&amp;lt;a id=&quot;widgets&quot; href=&quot;...&quot;&gt;Buy Widgets&amp;lt;/a&gt;
&lt;/pre&gt;&lt;p&gt;&lt;code&gt;Buy Widgets&lt;/code&gt; is the title of the page and &lt;code&gt;widgets&lt;/code&gt; is its alias.&lt;/p&gt;
</description>
 <category domain="https://diaryproducts.net/exactly/about/cms/typo3">Typo3</category>
 <category domain="https://diaryproducts.net/exactly/for/webmaster">Webmaster</category>
 <pubDate>Sun, 28 Nov 2004 21:45:50 +0000</pubDate>
</item>
<item>
 <title>Typo3: To Each Their Own - Site And Page Titles In Alternative Languages</title>
 <link>https://diaryproducts.net/about/cms/typo3/site_and_page_title_in_alternative_languages</link>
 <description>&lt;h3&gt;Problem 1: The Site Title Is Global&lt;/h3&gt;
		&lt;p&gt;Your site supports multiple languages using the &amp;quot;modern&amp;quot; single-tree aproach where one page has one or more translations in alternative languages. In Typo3 every page&#039;s title usually starts with the site title and the page title is appended to it. The page title can easily be translated by customizing the language-specific header fields. The site title, however, can only be set globally. Consider yourself lucky if your site title is universal across languages. Mine isn&#039;t. Furthermore, I like my site&#039;s title to contain main search engine keywords, i.e. the words I want my site to be found under in Google, Yahoo and so on.&lt;/p&gt;</description>
 <category domain="https://diaryproducts.net/exactly/about/cms/typo3">Typo3</category>
 <category domain="https://diaryproducts.net/exactly/for/webmaster">Webmaster</category>
 <pubDate>Wed, 08 Sep 2004 10:44:42 +0000</pubDate>
</item>
</channel>
</rss>
