Re: Camping 2.1 and whywentcamping.com
Sorry I actually meant to say that all key content and navigation should be visible in the top 1084 pixels (and maybe less). It's not so much that we can make the page longer but you loose visitor's attention span (see http://browsersize.googlelabs.com/). On 6/30/2010 7:46 AM, Magnus Holm wrote: On Wed, Jun 30, 2010 at 14:57, Philippe Monnet wrote: Thanks Magnus! I love the idea of working on the web site for 2.1. I am still not crazy about the web site name though - as it is not easy for people to remember if they don't know the connection with _why. I personally would have preferred rubycamping.com or something linking Camping to Ruby somehow. But if everyone prefers that name I am fine with that. Sure, I don't care what's the domain name will be. A couple ideas for the site: Keep the home page simple with all content fitting within 1280 x 1024 I don't necessarily agree with this: users are used to scroll on the internet (e.g. http://vowsjs.org/) Use a catchy design (need some help here) Of course! Unfortunately, I can't really help here either. Accentuate that Camping is about Ruby (maybe also include the ruby logo somewhere) Agree. 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 Agree. I feel these kind of pages should end up at the wiki (but we might want to move away from GitHub's wiki). 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 Totally agree! 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 Interesting. We'll have to check that out. 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.)? This should hopefully be a part of the reference section How about a page about plugins with some brief description of their intent? Wiki material? I would love for us to include _why's cartoons in some of the sub pages ;-) Agree. Who would be interested in working together on the site? I'm always interested, but I'm that good at design… Could we do a couple graphic mockups of the main page? How should we exchange them? Via the mailing list? Not sure… I am ready and excited to help with that. I think it would be great to launch the site in time for _Why Day (Aug 19th)! Philippe Also, I think we should store a lot of information on a wiki; Camping is after all a pretty much "public" project. I still think we should have a separate website though (which should both work as a place where you can find Camping-related resources AND where we "advertise" to new people). ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
Re: Camping 2.1 and whywentcamping.com
>From an SEO standpoint rubycamping is probably the better choice over whywentcamping. Although changing the header to "Camping, a Ruby Microframwork" would probably be enough anyway. Dave On Wed, Jun 30, 2010 at 8:57 AM, Philippe Monnet wrote: > Thanks Magnus! I love the idea of working on the web site for 2.1. > I am still not crazy about the web site name though - as it is not easy for > people to remember if they don't know the connection with _why. I personally > would have preferred rubycamping.com or something linking Camping to Ruby > somehow. But if everyone prefers that name I am fine with that. > > A couple ideas for the site: > > Keep the home page simple with all content fitting within 1280 x 1024 > Use a catchy design (need some help here) > Accentuate that Camping is about Ruby (maybe also include the ruby logo > somewhere) > 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 > 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 > > 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 > 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.)? > How about a page about plugins with some brief description of their intent? > I would love for us to include _why's cartoons in some of the sub pages ;-) > > Who would be interested in working together on the site? > Could we do a couple graphic mockups of the main page? How should we > exchange them? Via the mailing list? > I am ready and excited to help with that. I think it would be great to > launch the site in time for _Why Day (Aug 19th)! > > Philippe > > On 6/30/2010 5:08 AM, Magnus Holm wrote: > > Hey campers! > > I think it's about time to release Camping 2.1, which features: > > * Support for other template engines (Haml, ERB, etc) out of the box > * No longer depends on ActiveRecord (this was a bug) > * Camping.options is now a Hash where you can put all sorts of > configuration stuff > * Camping::Server now uses Rack::Server (got rid of some code) > * See all changes here: > http://github.com/camping/camping/compare/2.0...master > > -- > > There's still one thing I want to improve before we release 2.1 > though, and that is the website. Currently it only redirects to the > RDoc, but I believe we can do better. > > Checkout this: http://whywentcamping.judofyr.net/ (also see the GitHub > repo for some more information: > http://github.com/camping/whywentcamping.com) > > Better? Worse? You tell me :-) > > Have a look at the issues I'm aware of > (http://github.com/camping/whywentcamping.com/issues) and please add > your own too. > > // Magnus Holm > ___ > Camping-list mailing list > Camping-list@rubyforge.org > http://rubyforge.org/mailman/listinfo/camping-list > > > > ___ > Camping-list mailing list > Camping-list@rubyforge.org > http://rubyforge.org/mailman/listinfo/camping-list > -- Dave ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
Re: Camping 2.1 and whywentcamping.com
On Wed, Jun 30, 2010 at 14:57, Philippe Monnet wrote: > Thanks Magnus! I love the idea of working on the web site for 2.1. > I am still not crazy about the web site name though - as it is not easy for > people to remember if they don't know the connection with _why. I personally > would have preferred rubycamping.com or something linking Camping to Ruby > somehow. But if everyone prefers that name I am fine with that. Sure, I don't care what's the domain name will be. > A couple ideas for the site: > Keep the home page simple with all content fitting within 1280 x 1024 I don't necessarily agree with this: users are used to scroll on the internet (e.g. http://vowsjs.org/) > Use a catchy design (need some help here) Of course! Unfortunately, I can't really help here either. > Accentuate that Camping is about Ruby (maybe also include the ruby logo > somewhere) Agree. > 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 Agree. I feel these kind of pages should end up at the wiki (but we might want to move away from GitHub's wiki). > 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 Totally agree! > 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 Interesting. We'll have to check that out. > 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.)? This should hopefully be a part of the reference section > How about a page about plugins with some brief description of their intent? Wiki material? > I would love for us to include _why's cartoons in some of the sub pages ;-) Agree. > Who would be interested in working together on the site? I'm always interested, but I'm that good at design… > Could we do a couple graphic mockups of the main page? How should we > exchange them? Via the mailing list? Not sure… > I am ready and excited to help with that. I think it would be great to > launch the site in time for _Why Day (Aug 19th)! > > Philippe > Also, I think we should store a lot of information on a wiki; Camping is after all a pretty much "public" project. I still think we should have a separate website though (which should both work as a place where you can find Camping-related resources AND where we "advertise" to new people). ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
using reststop with tilt
I'm trying to use the new Tilt integration with reststop. All the aliases and whatnot under "Implementing your own service" (http://wiki.github.com/camping/reststop/) are there and :views has been set in the options hash. I tried creating sub-directories in the views directory (html, HTML) but I still couldn't get it to work. I can get my haml template to display if I get rid of the alias for reststop_render. All the other render calls to markaby still work when I do this too. However, I'm assuming I'm loosing the second argument for render in reststop when I do this. Am I missing some other setting/configuration option to get this to work with the alias for reststop_render? -- Dave ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
Re: Camping 2.1 and whywentcamping.com
So maybe another thing we need on the main site is a "Camping Ring" feature to tie in all Camping fan sites! :-) On 6/30/2010 7:03 AM, Sean Busbey wrote: kylekyle and I have planned to use http://thelittlewheels.com/ as a showcase for camping stuff. probably even more confusing to new people than whywentcamping On Wed, Jun 30, 2010 at 13:57, Philippe Monnet wrote: Thanks Magnus! I love the idea of working on the web site for 2.1. I am still not crazy about the web site name though - as it is not easy for people to remember if they don't know the connection with _why. I personally would have preferred rubycamping.com or something linking Camping to Ruby somehow. But if everyone prefers that name I am fine with that. A couple ideas for the site: Keep the home page simple with all content fitting within 1280 x 1024 Use a catchy design (need some help here) Accentuate that Camping is about Ruby (maybe also include the ruby logo somewhere) 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 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 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 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.)? How about a page about plugins with some brief description of their intent? I would love for us to include _why's cartoons in some of the sub pages ;-) Who would be interested in working together on the site? Could we do a couple graphic mockups of the main page? How should we exchange them? Via the mailing list? I am ready and excited to help with that. I think it would be great to launch the site in time for _Why Day (Aug 19th)! Philippe On 6/30/2010 5:08 AM, Magnus Holm wrote: Hey campers! I think it's about time to release Camping 2.1, which features: * Support for other template engines (Haml, ERB, etc) out of the box * No longer depends on ActiveRecord (this was a bug) * Camping.options is now a Hash where you can put all sorts of configuration stuff * Camping::Server now uses Rack::Server (got rid of some code) * See all changes here: http://github.com/camping/camping/compare/2.0...master -- There's still one thing I want to improve before we release 2.1 though, and that is the website. Currently it only redirects to the RDoc, but I believe we can do better. Checkout this: http://whywentcamping.judofyr.net/ (also see the GitHub repo for some more information: http://github.com/camping/whywentcamping.com) Better? Worse? You tell me :-) Have a look at the issues I'm aware of (http://github.com/camping/whywentcamping.com/issues) and please add your own too. // Magnus Holm ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
Re: Camping 2.1 and whywentcamping.com
Awesome domain name! And as long as you include the image, it probably makes sense for new people too. You know, the password to the camping github account was actually "littlewheels" :-) // Magnus Holm On Wed, Jun 30, 2010 at 15:03, Sean Busbey wrote: > kylekyle and I have planned to use http://thelittlewheels.com/ as a > showcase for camping stuff. probably even more confusing to new > people than whywentcamping > > On Wed, Jun 30, 2010 at 13:57, Philippe Monnet wrote: >> Thanks Magnus! I love the idea of working on the web site for 2.1. >> I am still not crazy about the web site name though - as it is not easy for >> people to remember if they don't know the connection with _why. I personally >> would have preferred rubycamping.com or something linking Camping to Ruby >> somehow. But if everyone prefers that name I am fine with that. >> >> A couple ideas for the site: >> >> Keep the home page simple with all content fitting within 1280 x 1024 >> Use a catchy design (need some help here) >> Accentuate that Camping is about Ruby (maybe also include the ruby logo >> somewhere) >> 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 >> 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 >> >> 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 >> 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.)? >> How about a page about plugins with some brief description of their intent? >> I would love for us to include _why's cartoons in some of the sub pages ;-) >> >> Who would be interested in working together on the site? >> Could we do a couple graphic mockups of the main page? How should we >> exchange them? Via the mailing list? >> I am ready and excited to help with that. I think it would be great to >> launch the site in time for _Why Day (Aug 19th)! >> >> Philippe >> >> On 6/30/2010 5:08 AM, Magnus Holm wrote: >> >> Hey campers! >> >> I think it's about time to release Camping 2.1, which features: >> >> * Support for other template engines (Haml, ERB, etc) out of the box >> * No longer depends on ActiveRecord (this was a bug) >> * Camping.options is now a Hash where you can put all sorts of >> configuration stuff >> * Camping::Server now uses Rack::Server (got rid of some code) >> * See all changes here: >> http://github.com/camping/camping/compare/2.0...master >> >> -- >> >> There's still one thing I want to improve before we release 2.1 >> though, and that is the website. Currently it only redirects to the >> RDoc, but I believe we can do better. >> >> Checkout this: http://whywentcamping.judofyr.net/ (also see the GitHub >> repo for some more information: >> http://github.com/camping/whywentcamping.com) >> >> Better? Worse? You tell me :-) >> >> Have a look at the issues I'm aware of >> (http://github.com/camping/whywentcamping.com/issues) and please add >> your own too. >> >> // Magnus Holm >> ___ >> Camping-list mailing list >> Camping-list@rubyforge.org >> http://rubyforge.org/mailman/listinfo/camping-list >> >> >> >> ___ >> Camping-list mailing list >> Camping-list@rubyforge.org >> http://rubyforge.org/mailman/listinfo/camping-list >> > > > > -- > Sean > ___ > Camping-list mailing list > Camping-list@rubyforge.org > http://rubyforge.org/mailman/listinfo/camping-list > ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
Re: Camping 2.1 and whywentcamping.com
kylekyle and I have planned to use http://thelittlewheels.com/ as a showcase for camping stuff. probably even more confusing to new people than whywentcamping On Wed, Jun 30, 2010 at 13:57, Philippe Monnet wrote: > Thanks Magnus! I love the idea of working on the web site for 2.1. > I am still not crazy about the web site name though - as it is not easy for > people to remember if they don't know the connection with _why. I personally > would have preferred rubycamping.com or something linking Camping to Ruby > somehow. But if everyone prefers that name I am fine with that. > > A couple ideas for the site: > > Keep the home page simple with all content fitting within 1280 x 1024 > Use a catchy design (need some help here) > Accentuate that Camping is about Ruby (maybe also include the ruby logo > somewhere) > 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 > 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 > > 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 > 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.)? > How about a page about plugins with some brief description of their intent? > I would love for us to include _why's cartoons in some of the sub pages ;-) > > Who would be interested in working together on the site? > Could we do a couple graphic mockups of the main page? How should we > exchange them? Via the mailing list? > I am ready and excited to help with that. I think it would be great to > launch the site in time for _Why Day (Aug 19th)! > > Philippe > > On 6/30/2010 5:08 AM, Magnus Holm wrote: > > Hey campers! > > I think it's about time to release Camping 2.1, which features: > > * Support for other template engines (Haml, ERB, etc) out of the box > * No longer depends on ActiveRecord (this was a bug) > * Camping.options is now a Hash where you can put all sorts of > configuration stuff > * Camping::Server now uses Rack::Server (got rid of some code) > * See all changes here: > http://github.com/camping/camping/compare/2.0...master > > -- > > There's still one thing I want to improve before we release 2.1 > though, and that is the website. Currently it only redirects to the > RDoc, but I believe we can do better. > > Checkout this: http://whywentcamping.judofyr.net/ (also see the GitHub > repo for some more information: > http://github.com/camping/whywentcamping.com) > > Better? Worse? You tell me :-) > > Have a look at the issues I'm aware of > (http://github.com/camping/whywentcamping.com/issues) and please add > your own too. > > // Magnus Holm > ___ > Camping-list mailing list > Camping-list@rubyforge.org > http://rubyforge.org/mailman/listinfo/camping-list > > > > ___ > Camping-list mailing list > Camping-list@rubyforge.org > http://rubyforge.org/mailman/listinfo/camping-list > -- Sean ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
Re: Camping 2.1 and whywentcamping.com
Thanks Magnus! I love the idea of working on the web site for 2.1. I am still not crazy about the web site name though - as it is not easy for people to remember if they don't know the connection with _why. I personally would have preferred rubycamping.com or something linking Camping to Ruby somehow. But if everyone prefers that name I am fine with that. A couple ideas for the site: * Keep the home page simple with all content fitting within 1280 x 1024 * Use a catchy design (need some help here) * Accentuate that Camping is about Ruby (maybe also include the ruby logo somewhere) * 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 * Encourage people to try it by capitalizing on some of Camping's strengths: o Fast to learn - requires only basic Ruby skills o Much simpler than Rails but more structure than Sinatra/Padrino o Lightning fast and memory efficient allowing fast and efficient sites o Can evolve from simple file to organized directory structure o Can layer in more features later using persistence and choice of view engines * 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 * 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.)? * How about a page about plugins with some brief description of their intent? * I would love for us to include _why's cartoons in some of the sub pages ;-) Who would be interested in working together on the site? Could we do a couple graphic mockups of the main page? How should we exchange them? Via the mailing list? I am ready and excited to help with that. I think it would be great to launch the site in time for _Why Day (Aug 19th)! Philippe On 6/30/2010 5:08 AM, Magnus Holm wrote: Hey campers! I think it's about time to release Camping 2.1, which features: * Support for other template engines (Haml, ERB, etc) out of the box * No longer depends on ActiveRecord (this was a bug) * Camping.options is now a Hash where you can put all sorts of configuration stuff * Camping::Server now uses Rack::Server (got rid of some code) * See all changes here: http://github.com/camping/camping/compare/2.0...master -- There's still one thing I want to improve before we release 2.1 though, and that is the website. Currently it only redirects to the RDoc, but I believe we can do better. Checkout this: http://whywentcamping.judofyr.net/ (also see the GitHub repo for some more information: http://github.com/camping/whywentcamping.com) Better? Worse? You tell me :-) Have a look at the issues I'm aware of (http://github.com/camping/whywentcamping.com/issues) and please add your own too. // Magnus Holm ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
Access to github.com/camping
Hey, I've converted the camping account into an organization (see http://github.com/blog/674-introducing-organizations), which means that it's a lot easier to manage it. There's currently two teams at the moment: Owners: These have full admin access (can create repos etc.) - Magnus - Philippe Developers: These can push to all the repos at github.com/camping - Magnus - Philippe - busbey - Dave Everitt - zuk - zimbatm I'm *very* open to add more users to the developers team. Just say what you intend to do (on the mailing list), and I'll add you. If you have a Camping related project which you would like to host under github.com/camping, just ask on the mailing list and we'll create a repo for you. (This should be added to the wiki in the near future) // Magnus Holm ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
Camping 2.1 and whywentcamping.com
Hey campers! I think it's about time to release Camping 2.1, which features: * Support for other template engines (Haml, ERB, etc) out of the box * No longer depends on ActiveRecord (this was a bug) * Camping.options is now a Hash where you can put all sorts of configuration stuff * Camping::Server now uses Rack::Server (got rid of some code) * See all changes here: http://github.com/camping/camping/compare/2.0...master -- There's still one thing I want to improve before we release 2.1 though, and that is the website. Currently it only redirects to the RDoc, but I believe we can do better. Checkout this: http://whywentcamping.judofyr.net/ (also see the GitHub repo for some more information: http://github.com/camping/whywentcamping.com) Better? Worse? You tell me :-) Have a look at the issues I'm aware of (http://github.com/camping/whywentcamping.com/issues) and please add your own too. // Magnus Holm ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
