Among the purposes for DaurrilPages that ought be recounted are the circumstances prompting this online workbook (presently accessable only thru the resume¹), for which there are primarily two. First, this workbook was moved to publication anticipating an 11th site to be targeted in a ad campaign selling my services as a website developer, and I especially needed a catalogue of my "current" work (none has sufficiently retired to be called "previous"). Curiously, that campaign is meant to suggest diversity, which as indicated elsewhere is only superficial. Secondly, as an offline workbook, this page may be thought of as "1-25-02b," a continuation of the 2nd sheet in this collection. That is, for not having a specific on-site object dedicated to the management per se of site invenvtory , I was losing control of the collection's developmental archive (esp the parts not uploaded ie that stay on the ground). Presumably, this new approach would be manditory to any commercial venture (reason one again).

Overview Security: While it was obvious from the first that the column showing passwords would not go to publication, it seems also prudent that the section of rows expressing policy need also to be inviolate. Also the second sheet here called "1-29-02a." In fact, "intro" might only be retained in the set because the audience needs a "universal" site-neutral page to hit on.

for the particular sites / pages:

action plans: This section brings general action to the plane of each individual website, which at first than describes its particular theater of action and the (external) alters expected to be encountered there. A place in this model also needs to identify "media of exchange." Likewise, each site needs to describe its relation to other action in the daurril collection.

Site-specific Security. In the course of their (and my) "evolution," a variety of issues pertaining to "differentiation" have arisen. Running from HTML does put source on-line, and apparently we cannot both publish and yet privately retain materials whose content we are not entirely prepared to dosclose. Or can we? The IE Browser seems unable to penetrate source packaged in frames. Or source may be packaged for "stagewise" (ie some progressive) revelation, depending on the access "class" of its anticipated audience.

One perhaps non-security item of differentiation is the mechanical separation of generative materials from what actually needs to be posted with the host. This is a late distinction pertaining mainly to my wysiwyg use of MS Excel / Word to develop: contributing materail being in separate folders also tends to eliminate an selection process at upload time, and avoid using the host to store artifacts.

Three classes of current DarrilSite require protection. Infrastructure-oriented public sites designed to eventually display the minutes (or closed captioning) of meetings should not service (or at least not prematurly advise) the present opposition to our purpose. Kin to that sense of preservation, the Comstands site cannot go prematuely public at any level below its present index-page. Finally, sites featuring OCR output from bound text (ie books) requre a progressive (if any at all) display at this time.

integration and differentiation.

chronology of the collection development

For most of this development, some version of HomeSite has been the html-editor of choice. The earliest problem was to find a development tool to lay out "complex" pages (which was at first thought to be via Frontpage, then Dreamweaver). It was not until the table-intense indices of parsons and comstands that I came to use the web-publishig component in MS Office (Excel and Word) to do the pages. Discovering the proper use of booksmarks and the hyperlink tool made the transition complete. Since then, the earlier sites are being progressively refitted for regeneration from Exel/Word, with minor htlm correction (in post) from HS. (Thus the column here called "developed from".)

We may also notice that these sites are all "static," ie the server does nothing but display pages already created. Some of these pages would be better represented as interactive with an online database. All the technology I need to implement that is already locally operational on my Win2000 system: it is only a matter of some funding from a commercial venture to relocate to an appropriate server.

footnotes:

¹ now 10:36 AM 2/3/02: