<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <title>Dennis Dam</title>
    <link rel="alternate" type="text/html" href="http://blogs.onehippo.org/dennis/" />
    <link rel="self" type="application/atom+xml" href="http://blogs.onehippo.org/dennis/atom.xml" />
   <id>tag:blogs.onehippo.org,2009:/dennis//7</id>
    <link rel="service.post" type="application/atom+xml" href="http://blogs.onehippo.org/mt/mt-atom.cgi/weblog/blog_id=7" title="Dennis Dam" />
    <updated>2006-06-01T19:53:54Z</updated>
    
    <generator uri="http://www.sixapart.com/movabletype/">Movable Type 3.35</generator>
 
<entry>
    <title>Experiences at Lostboys</title>
    <link rel="alternate" type="text/html" href="http://blogs.onehippo.org/dennis/2006/06/experiences_at_lostboys.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://blogs.onehippo.org/mt/mt-atom.cgi/weblog/blog_id=7/entry_id=35" title="Experiences at Lostboys" />
    <id>tag:blogs.hippo.nl,2006:/dennis//7.35</id>
    
    <published>2006-06-01T19:07:27Z</published>
    <updated>2006-06-01T19:53:54Z</updated>
    
    <summary>Lately I&apos;ve been sent to Lostboys to assist a team of programmers in setting up a Cocoon website for a big house corporation. It&apos;s quite entertaining to have some students under your wing and throw them in the deep :)...</summary>
    <author>
        <name>Dennis Dam</name>
        <uri>http://blogs.hippo.nl</uri>
    </author>
            <category term="etcetera" />
    
    <content type="html" xml:lang="en" xml:base="http://blogs.onehippo.org/dennis/">
        <![CDATA[<p>Lately I've been sent to <a href="http://www.lostboys.nl">Lostboys</a> to assist a team of programmers in setting up a Cocoon website for a big house corporation. It's quite entertaining to have some students under your wing and throw them in the deep :)</p>]]>
        <![CDATA[<p>It's amazing how fast they learn on the other hand. In spite of the very tight deadline we managed to set up the basis for the website quite fast. One of the main reasons for this fast progress  is a new basic structure of the site, which allows us to set up new functional parts of the website really fast: add a folder, add a sitemap, write one or two pipelines, and a little XSL: voilà that's it! And all that with a minimum amount of duplicate code.</p>

<p>One of the potential problems in this website is personalization. Visitors can login and change the way the website behaves in their "profile". Currently, this profile is stored in the session and made persistent using <a href="http://www.jpox.org">Jpox</a> and <a href="http://www.springframework.org/">Spring</a>. Our current approach is to maximize caching possibilites by deferring the visitor-dependent content (like login information and additional content which may appear anywhere in the page) to the end of the pipeline by using the session transformer in combination with the JX transformer just before serializing. We didn't have a real opportunity to test this method under heavy load yet, unfortunately.</p>

<p>Okay , so far the technical intermezzo. The differences in work environment I experience at Lostboys with respect to Hippo are mainly concerned with project management: every week there are two scheduled meetings with the whole team (in total about 8 people), there is a detailed planning (although quite optimistic) and we often have a talk-through of the current status with the site developers. In short, I feel like there are really a lot of reports back to management ;) Which is good in it's own way, to stay focused on the goals you're pursuing, but I had to get used to it in the beginning.</p>

<p>For the rest, the working atmosphere in Lostboys is a lot like Hippo. Music, a dart board, a lot of young people, and even a game machine near the coffee machine (might be an idea for Hippo (: ) .</p>]]>
    </content>
</entry>
<entry>
    <title>Schijndel Website is &quot;Drempels Weg&quot;</title>
    <link rel="alternate" type="text/html" href="http://blogs.onehippo.org/dennis/2006/04/schijndel_website_is_drempels.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://blogs.onehippo.org/mt/mt-atom.cgi/weblog/blog_id=7/entry_id=16" title="Schijndel Website is &quot;Drempels Weg&quot;" />
    <id>tag:blogs.hippo.nl,2006://7.16</id>
    
    <published>2006-04-12T09:21:21Z</published>
    <updated>2006-04-12T11:30:34Z</updated>
    
    <summary>The Municipality Schijndel website has been declared &quot;Drempels Weg&quot;, which means something like &quot;Remove All Limits&quot;. Adhering to this standard allows e.g. blind people to surf the website in an accessible way. Ofcourse an important issue for a political organization....</summary>
    <author>
        <name>Dennis Dam</name>
        <uri>http://blogs.hippo.nl</uri>
    </author>
            <category term="Hippo CMS" />
    
    <content type="html" xml:lang="en" xml:base="http://blogs.onehippo.org/dennis/">
        <![CDATA[<p>The <a href="http://www.schijndel.nl">Municipality Schijndel</a> website has been declared "Drempels Weg", which means something like "Remove All Limits". Adhering to this standard allows e.g. blind people to surf the website in an accessible way. Ofcourse an important issue for a political organization.</p>

<p>So how can this be achieved? First, take a cup of coffee. Think about how much torture you can stand before you break into tears. Then if you think you're up to it, go to the <a href="http://www.drempelsweg.nl/ ">Drempelsweg website</a> (sorry, this is in Dutch!). Basically it comes down to making your website XHTML (Transitional) compliant, and tagging HTML elements with enough information (titles / alt tags / caption / summaries), so e.g. a browser for blind people can function properly. Most of the text on the website is generated from Hippo CMS, more particularly the HTMLAreas in the Editor. This should be easy for the website developer (me), since this should move the responsibility for adding meta information to html elements to the CMS user. Alas! CMS users are no robots. They can be lazy. Unfortunately, there is currently no way to force CMS users to add accessibility information to html elements inside the htmlarea (might be an improvement?). So that means we need some backup mechanism in the frontend. This comes down to providing downloads like names like "election results.pdf" with ALT texts like "Link to election results.pdf". Does this really help the blind man, I wonder? :).</p>

<p></p>

<p><br />
</p>]]>
        
    </content>
</entry>

</feed> 

