<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7638.1">
<TITLE>Documentation notes</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->
<P><FONT SIZE=2 FACE="Arial">As an experiment last week I change the workflow for handbook pages and they no longer go into moderation. So it seems to be working nicely. Now, the edits for registered user accounts on Drupal.org are the same, they can add and edit their own pages. Book maintainers may edit any book pages. We have several new ones, please say Hi. (Site maintainers may also edit as usual.)</FONT></P>
<P><FONT SIZE=2 FACE="Arial">The handbook updates link (</FONT><A HREF="http://drupal.org/handbook/updates"><U><FONT COLOR="#0000FF" SIZE=2 FACE="Arial">http://drupal.org/handbook/updates</FONT></U></A><FONT SIZE=2 FACE="Arial">) is still valid as it shows recent activity. I've used it to spot and remove 3 spam posts and sort of track who is updating what content.</FONT></P>
<P><FONT SIZE=2 FACE="Arial">Haven't heard anyone wanting to take up the landing page challenge since my last email, though one gentleman in the forums posted a really nice series of steps he went through that if I and Boris can't convince him to contribute, I'll just canabalize for a framework and use it.</FONT></P>
<P><A HREF="http://drupal.org/node/77260#comment-142782"><U><FONT COLOR="#0000FF" SIZE=2 FACE="Arial">http://drupal.org/node/77260#comment-142782</FONT></U></A>
</P>
<P><FONT SIZE=2 FACE="Arial">I asked a friend of mine to write up the process from an amateur design point of view for a site he did. He asked me some quesitons about modules and such but the site is pretty much his work (</FONT><A HREF="file://www.woodfordscience.com/"><U><FONT COLOR="#0000FF" SIZE=2 FACE="Arial">www.woodfordscience.com/</FONT></U></A><FONT SIZE=2 FACE="Arial">). More of a design steps for amateurs type write up </FONT><A HREF="http://scratch.blkmtn.org/node/23"><U><FONT COLOR="#0000FF" SIZE=2 FACE="Arial">http://scratch.blkmtn.org/node/23</FONT></U></A><FONT SIZE=2 FACE="Arial"> . He's pretty much where I am. Both of us are professional IT Support folks so we know a lot of the theory but it's not part of our day job except in spotting where poor design may generate more support issue's. All to many people new to Drupal lack even the theory. Other view points/how to's would be good as well. Comments/suggestion, should we try and get more people to add such to the handbook?</FONT></P>
<P><FONT SIZE=2 FACE="Arial">Other future concerns…. 4.8/5.0. If you haven't been tracking the CCK framework into core… wow, it will change your assumptions about how Drupal is configured. This seems to lean into a handbook challenge if some of the items get fully implmented. (ie Story and Page nodes become CCK content types). So, feedback, suggestions, directions welcome…. JSQuery examples and how to's will also be needed and I know nothing about Jscript.</FONT></P>
<P><FONT SIZE=2 FACE="Arial">-sp</FONT>
</P>
<BR>
<BR>
<BR>
<BR>
<P><FONT SIZE=2 FACE="Arial">.</FONT>
</P>
<BR>
</BODY>
</HTML>