Example of a good guide

This is another example of a good guide: http://www.jstherightway.org/

Can’t remember if I shared this before:

What do you like about it? I like the colorful layout, but the content does not strike me as a particularly good example of a guide.

Yes, not a 100% fit. I like the way that it curates a bunch of resources in a more interesting way than simply a list of links. It makes you think that the links might actually be worth following and that the person who compiled the resources actually cared.

I’m not 100% fond of the colors, a little too bright and stimulating for me :slight_smile:

@vanessa, I know you probably have a bunch of examples that you like, please share

I like the simplicity, and the concise, useful statements, but not a huge fan of the single scrolling page for a detailed how-to.

Format aside, I think the key is punchy but helpful content, which these do have - not just a checklist but an opinion expressed on each of them.

But I think if it’s a guide that you’re going to read more than once, jump in and out of, leave and come back to, it needs to be more navigable / more clear discrete sections.

As previously mentioned (not on thepeople) - I quite like School of Data’s ‘guide on being a guide’: whether or not you think the format is exciting enough I think they do a good job on the hardest bit - distilling wisdom re creating a learning experience down to a series of pithy lessons learned and issues that must be addressed. I think this is the hard bit and should be where the majority of any time we put into guide-building should be spent.

(here as a web guide: http://schoolofdata.org/data-expeditions/guide-for-guides/ / here as a PPT: http://schoolofdata.org/data-expeditions/online-expedition-guide/)

Not denigrating the power of good design, but think any guide we create should be content-led not design led.

@Carl the two linked guides from school of data differ in content. I like the guide in the first link, it seems complete and gives a good overview. The second link seems to be the presentation used to present the contents in the first link.

I think we have lots to say, but that we should deliver it in a way that makes it easy (and exciting) to get an overview, but also easy to drill down on the points of interest - and to discuss those. I think speaking.io does a good job at this, have a look at: http://speaking.io/plan/an-idea/

But I agree - we should work on something like http://speaking.io/plan/an-idea/ before we work on the http://speaking.io/ part of it.

Agreed. I do like that one.