• 09/30: Secure site, tiny but backed by admin aids and beta training forum
• 10/31: Event pages announce site to all Groups; tout planned options
• 11/30: Training SIGs & uploaders let each MEMBER adjust free booth
• 12/31: JUG projects add booth searching & feedback by public visitors

ShadowCats, LLC will license MESDA its template-based page producer, and the admin aids supporting it.  This combination lets *.htm templates within a /webpages/ folder record all the dynamic page bodies for a booth.  A special case _layout.txt file and arbitrary graphics files, both in that same folder, handle all page headers and footers for the MEMBER in a consistent manner.  (Try it out as "guest").

As part of its license, MESDA gets needed custom "tags" for this release (to be jointly enhanced by Lexikos code and MESDA data) which support at least these planned dynamic pages for a USER Registry:

1. Cookie-sensitive USER login page(s), capturing/checking UID+PW
2. Default splash page - simple listing of all/USER's/other MEMBER pages
3. MEMBER description page - with bi-modal [(DE)REGISTER] button

• To help render /webpages/, a DepotAPI tag for online data modeling MEMBERS and USERS will read attribute values on them.  Mechanisms for value updates (and most concurrency issues) stay separate
• To support a UserAPI tag for page A.1, a "data depot" (co-folder to /webpages/) will be built holding data on USERS.  Its access logic is compatible with stated EJB/DB requirements.
• To support the other two pages, a LogAPI tag registering persistent Log data associated with centralized MEMBER data  will collect and (de)register UIDs and other data, along with time suitable stamps. 

These involve secure pages and some may be stubbed in the first release.  They will take additional work for beta-2 and beta-3, to make them work self-sufficiently as low-tech "wizards". I'm now seeking SIG volunteers on the revised page body templates, as special ShowCase-support Projects.

1. USER self description and data entry page (special, like cloning)
2. Dated log dump on USERs who are/were registered (like JugNews)
3. Administration pages for MEMBERS, USERS, and other depots
4. Sales-support pages on buying options - custom /webpages/, etc.

Page B.1 is seen and used only by each USER, who creates a data element and UID at initial registration, then may later edit it.  Its logic extends the UserAPI tag used by A.1, based on "cloning" support in B.3.  All changes it makes get logged for recall by a MESDA supervisor - a special use case of page B.2.

Page B.2 is seen only by USERS who get marked (via B.3) as a "supervisor" for some related MEMBER.  It takes the needed MEMBER-ID as a parm, and lists UIDs whose registration has changed since any given time.  A special parm also lets  MESDA supervisors get all the recent or changed USERS for the whole site.  This is an extension for the LogAPI tag used for pages A.2-3.

Administrative HELP.  The "project" here is learning how it works, then adding paragraphs and or pages to the TRAINING pages which act as an on-line guide for other staff (MESDA's or MEMBERS').  Its readers will know neither Java nor FTP, but must administer data depots for one or more booths.

B.4 Customer Service and Promotions. Separate "training" pages offer each supervisior-USER of B.2 special instructures on how to customize /webpages/.  In released versions, they should also explains their benefits via details and examples, give help on ordering, and explain how to add multimedia support, and post page revisions by using our anticipated file uploader.

Walk-in sales pages will be at the main MESDA site, but B.2 privately aids those people most likely to buy new options - current booth adminstrators.  If it and B.4 work together, the latter can be a good tool for sales as well as support.