New 1.5 blog example

[Magnus Holm]

While I can't have a look at it at the moment (no Internet access),  
it's very nice of you! Maybe we can merge them and get an even better  
blog.rb in v2.

As for the documentation ideas, I've already implemented the templates  
in RDoc, so "rake docs" builds all the three parts (the book is simply  
files in the book directory). I still need to make a way to link book  
chapters from the reference, but at least it's working. A Camping app  
can be useful when you want to edit it, so you don't need to run the  
rake task all the time.

I guess we could also implement it as a wiki, which might be better.  
Then we can't have it on camping.rubyforge.org (unless we can change  
the DNS-settings) though since it only allows static files. What do  
you think? I prefer having everything in files, and I think those who  
really want to contribute to the book wouldn't mind a "git clone"...

Right now I'm on vacation, but I'll try to push it out when I return.  
Feel free to write some paragraphs if you're really keen, I only have  
a bare skeleton.

//Magnus (written 28th July in offline mode)

On 27. juli 2009, at 16.57, Dave Everitt <deveritt at innotts.co.uk> wrote:

> Hello Campers...
>
> I've just finished a (hopefully) nicer-looking Camping 1.5 blog  
> example, adapted from one of the originals:
> http://pastie.org/560295
>
> Things I've done:
>    added a delete class,
>    combined the add/edit/delete method into one,
>    made a little 'cooked up while camping' logo,
>    tweaked the CSS so it looks kind-of-ready for deployment,
>    called it 'tentpole' because it's so simple (that's a joke).
>
> I know there's the clean, new example for v2 on Github, but I don't  
> have Camping v2 up and running yet (I will, soon), so this is for  
> anyone who needs to point to a simple, working a 1.5-ready example  
> with minimal setup requirements.
>
> Still keen on Magnus' documentation ideas (below) and happy to  
> start... I think the book should be a Camping app :-)
>
> Dave Everitt
>
>> Right now there is an example at camping.rubyforge.org showing a  
>> blog skeleton (with controllers, models and views). It might be  
>> better to rather have a tiny, fully functional one (to get the feel  
>> of Camping), and a link to blog.rb (which should be simplified even  
>> more, and actually work). The book could then take it from there  
>> and slightly expand into the blog.rb (or maybe even totally  
>> different; we should at least end up with something)
>
>
> Magnus' documentation proposal:
>
>> What if we split the documentation into three parts?
>>
>> - README.txt should be the first you see and should contain basic  
>> info and links.
>>
>> - API-reference. A one-page reference to the whole Camping API  
>> which gives you short descriptions/explanations and might also give  
>> a link to the book (see below) for more detailed thoughts.
>>
>> - A "book" or tutorial which guides the user from A-Z, starting  
>> with installation and how to use The Camping Server, through basic  
>> MVC and HTTP/REST to how to use service-overrides or middlewares.  
>> It would be really nice if this could be a clean, short and concise  
>> guide to both Ruby and web development.
>
>
> _______________________________________________
> Camping-list mailing list
> Camping-list at rubyforge.org
> http://rubyforge.org/mailman/listinfo/camping-list