http://wiki.merbivore.com/about/using_merb is a useful start on
the kinds of index pages the Merb community will need.  I'd be
happier to see more filled-in entries and a rational order for
the entries, but these are quibbles.

Although the page title is "Applications using Merb", the links
mostly go to the Web sites that _use_ the apps.  This lets users
visit the site, but leaves them without much information about
how the site was created, what problem(s) it addresses, etc.


So, I'd like to propose a set of wiki pages where developers
can present background information on Merb-based apps, sites,
etc.  I don't have a complete spec, but here are some ideas:

  -  What is the scale of the site (eg, hits, pages, users)?

  -  Who developed the site?

  -  What is the production infrastructure (eg, HW, OS, VMs)?

  -  What add-in software (eg, DBs, gems) does the site use?

  -  What interesting problems did the site present (and what
     approach was taken to solve them)?

  -  If the application itself is available for inspection,
     where can it be found, etc.

No particular content is required; just provide background
information that Merbists will find interesting...


Here's a possible page-naming approach:

  http://wiki.merbivore.com/about/site_<name>

-r


P.S.  I don't (yet :) have a site I want to present, but I'd
      be happy to help developers create their own pages, if
      that could help get things rolling (contact me off-list).
-- 
http://www.cfcl.com/rdm            Rich Morin
http://www.cfcl.com/rdm/resume     [EMAIL PROTECTED]
http://www.cfcl.com/rdm/weblog     +1 650-873-7841

Technical editing and writing, programming, and web development

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"merb" 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/merb?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to