bellycard / napa

A simple framework for building APIs with Grape
Other
329 stars 72 forks source link

Documentation generator #122

Closed shaqq closed 10 years ago

shaqq commented 10 years ago

Here's what the generated README would look like

I wanted to auto-generate the Endpoints from rake routes, but Thor doesn't seem to load the ApplicationApi

shaqq commented 10 years ago

@danielmackey @ckampfe @jdoconnor @darbyfrey @umtrey @ajself @kevinreedy

umtrey commented 10 years ago

When we generate a new napa service, a README is generated that's just really basic. Is there any reason we wouldn't want that to be replaced by the new README from here?

umtrey commented 10 years ago

Generating a readme in a non-root path will create a spec folder in the given path as well - probably need to make sure we put the test file in there.

shaqq commented 10 years ago

@umtrey I think the idea is to replace the default README with this one (though maybe we would tone down the pooping a bit) - it's not too hard to move this over to the scaffold generator.

Originally I had plans of making something more rdoc-y that would auto-generate certain parts of the README. But, that's a little further down I think.

shaqq commented 10 years ago

I think there's also the danger of yelling at the user too fast - the readme generator creates a breaking test right off the bat. Sometimes people fill out README's a little later on, and this is somewhat of a more guided process.

umtrey commented 10 years ago

Let's add in a note in the quickstart about making sure they generate a readme (and also update the base gem readme too with the new command), then it's on their terms.

shaqq commented 10 years ago

@darbyfrey do you think adding a spec for the README might be too much?

heymackey commented 10 years ago

Can we make it a pending spec?

umtrey commented 10 years ago

@danielmackey image

darbyfrey commented 10 years ago

a pending test seems like a good solution to me

shaqq commented 10 years ago

So, what does everyone think about the :poop:? I thought it was funny at first, but it might be a little on the nose for someone who doesn't work at Belly.

shaqq commented 10 years ago

@darbyfrey @danielmackey @umtrey I'll switch that test to pending, and update the quickstart & gem readme

umtrey commented 10 years ago

@shaqq just one poo very early in the README would be cute, but no need for more than that - they very well could gut the rest of the README.

shaqq commented 10 years ago

Check out the toned-down version

ckampfe commented 10 years ago

"Diagrams and pictures are :angel:"

heymackey commented 10 years ago
     /(|
    (  :
   __\  \  _____
 (____)  `|
(____)|   |
 (____).__|
  (___)__.|_____
heymackey commented 10 years ago

The other alternative is to use the :x: emoji, if we want something more 'corporate'

shaqq commented 10 years ago

@darbyfrey @jdoconnor wanna do a quick look on the nicer version of the docs?

https://github.com/shaqq/readme-example/blob/master/README.md

umtrey commented 10 years ago

@shaqq make sure to put a note in the napa readme about the new readme generator

darbyfrey commented 10 years ago

Looks good. Please add this to the CHANGELOG as well.

+:bow:

umtrey commented 10 years ago

+1 so excite