I can see your point about long term maintenance. But drupal isn't hard. In fact, it is pretty darn easy and there are lots of sites that contain information about the software. <br><br>As for decoupling the parts, I have problems with this too. If you want a rich, dynamic site, the first priority should be ease of use. Drupal and phpBB provide a streamlined mechanism for this. When you go to create an article or a blog post you get a single consistent interface. When the time comes to change the theme to the site then it is a simple change and you don't have to expect people to know the in's and out's of particular browser CSS support. <br>
<br>As for the email component, here are my thoughts. The mailman web interface, as far as I can tell, is a batch of CGI scripts and probably doesn't lend itself well to integration. Considering the complexity of a maillist, I agree that these should not be closely integrated as an update to one could easily break the other.<br>
<br>Dan Kulinski <br><br><div class="gmail_quote">On Fri, Jan 27, 2012 at 5:02 PM, rex evans <span dir="ltr"><<a href="mailto:rexfordevans@yahoo.com">rexfordevans@yahoo.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<table border="0" cellpadding="0" cellspacing="0"><tbody><tr><td style="font:inherit" valign="top"><br>I agree with Paul Webb, consider simlifing by using HTML, which is a very easy language,<br>even for non-technical people. Keep the actual Web Pages simple, so any volunteer,<br>
years from now, can take over.<br><br>Decouple both the Mailing List and the Forum from the web page, and from each other.<br>Make every effort to keep all 3 as simple as possible and well commented.<br>If each of the 3 were on different platforms, that would be even better.<br>
<br>The actual Web Page(s) do not need to be interactive. They need to be accurate and up to date.<br><br>When saying "decouple" I mean eliminate uneeded linkages, for example Programatic<br>linkages; I, of course, did not mean ordinary, common, simple internet linkages.<br>
<br>When you ask for volunteers that must have Drupal experience, or php, or Javascript, or<br>Servlet exprience, you really cut down on
your pool of possibile volunteers.<br><br>Rex<br><br>--- On <b>Fri, 1/27/12, M Paul Webb <i><<a href="mailto:hsechmvt@yahoo.com" target="_blank">hsechmvt@yahoo.com</a>></i></b> wrote:<br><blockquote style="border-left:2px solid rgb(16,16,255);margin-left:5px;padding-left:5px">
<br>From: M Paul Webb <<a href="mailto:hsechmvt@yahoo.com" target="_blank">hsechmvt@yahoo.com</a>><br>Subject: Re: [clue] Website software<br><br><br><div><div><div style="font-size:12pt;font-family:verdana,helvetica,sans-serif">
<div><span>One thing about reading these e-mails I do not understand, and I wish someone would make it clear. Why does your website have to be Drupal? Why not just a simple CSS and HTML? <br></span></div></div></div></div>
</blockquote></td></tr></tbody></table><br>_______________________________________________<br>
clue mailing list: <a href="mailto:clue@cluedenver.org">clue@cluedenver.org</a><br>
For information, account preferences, or to unsubscribe see:<br>
<a href="http://cluedenver.org/mailman/listinfo/clue" target="_blank">http://cluedenver.org/mailman/listinfo/clue</a><br></blockquote></div><br>