Ok I would really like to get the promo site going so that we have
something up and running before Why Day (Aug 19th per
http://whyday.org/). I propose the following:
1. I can go ahead and buy the ruby-camping.com domain - should
someone also buy the .org equivalent? I think the promo site has to have
a straightforward name related to ruby and camping (similar to
ruby-lang) to make it easy for people to remember the site or search for
it. (We can use whywentcamping.com for something else like either the
doc site or the site focusing on learning and hosting simple apps - see
Jenna's ideas on this)
2. Until we know what other things we want to do with
ruby-camping.com in terms of showcasing apps and all, I can either host
the site:
a) at my host (1&1 - ok for now with straight content only -
the downside is I will be the bottleneck for updates
b) or deploy it on Heroku - we can have multiple collaborators
to push content via git. This would also give us more flexibility in the
long run (like diff versions of Ruby, db, plugins, etc - and maybe we
can get sponsored
3. For the time being I will leave the site as straight HTML and
Javascript (we can switch it to Camping+Tilt later)
4. I will create a ruby-camping.com project under camping in GitHub
and upload the content. This way anyone can contribute to the design -
wink wink uh-hmm Jenna/Dave/Matt/... ;-)
Let me know if you're ok with this or provide alternatives.
I'd like to get this done this week-end.
Philippe (@techarch)
On 7/8/2010 1:55 PM, Magnus Holm wrote:
Hey guys,
Philippe had some interesting points about the website:
1. Keep the home page simple with all content fitting within 1280 x 1024
2. Use a catchy design (need some help here)
3. Accentuate that Camping is about Ruby (maybe also include the ruby
logo somewhere)
4. Have a brief note about the connection to _why and a link to a page
explaining the history of Camping with further links to _why's other
sites
5. Encourage people to try it by capitalizing on some of Camping's strengths:
- Fast to learn - requires only basic Ruby skills
- Much simpler than Rails but more structure than Sinatra/Padrino
- Lightning fast and memory efficient allowing fast and efficient sites
- Can evolve from simple file to organized directory structure
- Can layer in more features later using persistence and choice of view engines
6. How about using some kind of an animated (auto advancing) slideshow
to highlight some of the benefits? See an example at:
http://blog.monnet-usa.com/?p=276
7. How about a page on learning with a link to the book as well as a
list of links for other tutorials or short explanations on key topics
(e.g. how to do migrations, how to use include/extend, how to use
different view engines, etc.)?
8. How about a page about plugins with some brief description of their intent?
9. I would love for us to include _why's cartoons in some of the sub pages ;-)
Now, the more I look at this list (and my own thoughts about the new
camping site) I realize that we're talking about two different things:
* A site to attract new users
* A site to inform regular users
It looks like my attempt (http://whywentcamping.judofyr.net/) tries to
target the latter, while Philippe targeted the former
(http://rubycamping.monnet-usa.com/). Both sites serves a purpose and
I believe both are equally important.
--
Here's what I propose: We split the site into two parts. We turn what
I've created into a wiki. Everyone are welcome to edit and add their
own content.
Then we take Philippe's ideas/design/site and turn it into
ruby-camping.com or whywentcamping.com or whatnot. It probably doesn't
need to be more than a single page.
What'd ya think?
// Magnus Holm
_______________________________________________
Camping-list mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/camping-list
_______________________________________________
Camping-list mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/camping-list
