This sounds like very sound advice to me. It seems it might be best to keep things as simple as possible for now.
The HTML can be edited by hand by for a while, sticking to a simple style sheet.
We can deploy with zero setup to an Amazon S3 bucket configured to act as a web server and easily configure a CDN and DNS service there if necessary.
Something packaged as a plain Apache file structure is also easily mirrorable by others in case things get hairy ala wikileaks.
A lower tech solution with a simple human based work flow may be what we are looking for here to get started
I also second the sending out of the working summary (or posting it on the site..;) so the working groups can know if the timelines support their needs or if they need to work on alternate methods of getting their messages out.
Any how thats what it looks like from here and Keep on Truckin...
On Tue, Oct 11, 2011 at 12:12 AM, Todd Grayson <email@example.com>
There needs to be a general understanding from the people participating in online operations and web development, that the consideration of "how many users are going to be accessing this service" must be a consideration before design starts on a solution.
In the requirements gathering phase of any project, the interview process should work to understand the target audience and project its size and usage/access patterns. How users will be provisioned (if a private services) or how self provisioned users will be managed/self manage within a site. The documentation of this should be maintained throughout the project (it becomes a non-functional requirement that must be met).
If something is going to be expected to be able to be viewed at massive scale, it should be static html, with limited images that are optimized so it can be placed on many web servers and balanced by geo-dns services like http://edgedirector.com/ while running as simple static content from hosted sites around the world.
It would be worthwhile to go through now and start clarifying by domain and service being brought online who the target audiences are for groups working on projects.
Announcements to the world type content that will have global appeal should be static HTML sites announcing agenda, publishing a few key static articles and that is it. Attempting to build applications that will require interaction between multiple components (such as wordpress with its db, the plugins with the DB, etc) are much more expensive as an operation and really should be reserved to registered non-hostile parties that are part of the movement. You can reach the public with your message, it doesn't have to be a heavy content set to get you message out.
It would be a good idea at some point to get a working summary of the services online now, the services about to be launched and the services that are being planned.
Services that will operate at a smaller scope can have a much higher level of interaction.
Please consider these things as you plan to bring services online.
T: 212 864 4294
M: 646 286 5371