One problem is that our docs are too fragmented at present. Perhaps
we should undertake a central wiki and bring all of the other content
into it. A single wiki could handle:
-- AlterEgo documents
-- Appliances
-- the current Wiki
-- important articles such as the Auth page on web2py.com
-- a repository for the next book -- written by ALL of us!
It could be based on web2py or not, but it should have the standard
wiki revision control. I find the current wiki less useful without
it.
It needs an overall "directory" to start with. I'd like to see
branches on:
-- reference docs (APIs, etc)
-- tutorial docs (such as "examples" page on web2py.com)
-- cookbook examples (AlterEgo?)
-- applications/appliances
-- internals
"Further out" ideas:
-- patterns
(I'm already starting to see common patterns in use but we're not
documenting them)
-- blog for Massimo and other key developers (Yarko, etc.)
-- timeline/futures
-- web2py con announcement and registration ;-)
-- Joe B.
On Feb 24, 8:55 am, mdipierro <[email protected]> wrote:
> Excellent points
>
> On Feb 24, 10:49 am, vihang <[email protected]> wrote:
>
> > - I had seen the wiki
> > athttps://mdp.cti.depaul.edu/web2py_wiki/default/wiki/main
> > earlier, but it seemed like a non-starter because it did not come out
> > as a wiki we all are used to seeing typically... format-wise. Also, we
> > should start by focusing just on Web2py and keep it simple (refering
> > to T2, T3).
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"web2py Web Framework" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/web2py?hl=en
-~----------~----~----~----~------~----~------~--~---
