replacing the cookbooks recipes & questions

[Bryan Larsen]

One of the tasks that we'd like to do for the 2.0 release is to
replace hobocentral.net and cookbook.hobocentral.net with a single
site based on the bootstrap theme.

I've started on it here: http://staging.hobocentral.net/. It's in
the bootstrap branch of https://github.com/Hobo/hobocookbook if you
want to help out. The task items are here:
https://trello.com/b/fvuauN0Q

Some of the task items are straight forward, some of them require discussion.

One of the items that requires the discussion is "what should we do
about Questions and Recipes".

Let's table the discussion about "questions". It's really a small
part of a larger discussion about what to do with the "community"
section of the web site.

But "recipes" is a genuinely useful and different from "community".
Currently, it has problems with discoverability (searching, browsing),
it doesn't really have a great mechanism for updates by anyone other
than the author. It was also severely crippled when I introduced a
half-baked moderation scheme to deal with the spam issues we were
having.

The following solutions have been proposed:

1) fix up the current mechanism. Add better browsability (tags?), add
editing capability, improve the moderation scheme.

2) add a user-editable page that contains an organized list of links
to hobo-users, since that's the primary place where people post
problems & solutions

3) build something around the github gist system, gists can have
comments, syntax highlighting, editing through forks. We already use
Github for our other user-editable pages, so requiring a user account
there instead of at hobocentral.net is not a big imposition. I
presume that Github has already dealt with the spam issue.

4) stackoverflow. Although more suited to "questions" than "recipes",
stackoverflow raison d'etre matches up very closely with what we need,
and they do it well.

5) use a wiki of some sort

6) merge with the current tutorial section. RIght now any of our
tutorials may be edited by anybody with a Github account (although
editing agility is a little more difficult due to it's extra
features). Perhaps we can migrate existing recipes here and create an
"create a recipe" link that edits a template on Github.

thoughts,
Bryan

[Owen]

Thanks for your thoughts about options going forward.  Will contemplate and provide my input soon...

I am really excited about having the complete site in Hobo and using Bootstrap....

Eating our own dog food is imperative...

-Owen

[Bryan Larsen]

My current preference is for #6. Here's the plan in more detail.
We'll migrate existing recipes into the tutorial section of the
cookbook and create a button that will allow anybody to add a tutorial
to the cookbook.

When pressed, the button will create a popup asking for the tutorial
name. The github API will then be used to create a template for the
tutorial in the hobodoc repository, and then the site will redirect to
the "edit this file" link on Github.

Once the user has submitted the tutorial to github, I will manually
review the tutorial, add a link to the tutorial on the tutorials index
page, merge the hobodoc repository into hobo and redeploy the
cookbook.

Yes, there's a lot of manual steps, but it's very similar to what
happens whenever anybody edits any other manual page. It would be
nice if it became overwhelming, but for now it's very from it.

thoughts?

Bryan

[Ignacio Huerta]

Hi,

I like option #6 too, merging tutorials and recipes into just
"tutorials" makes the information look less fragmented.

Regards,
Ignacio

El 21/11/12 17:40, Bryan Larsen escribi�:

--
Ignacio Huerta Arteche
http://www.ihuerta.net
Tel�fono: 0034 645 70 77 35
Email realizado con software libre