Always output into its own directory

[FWeinb]

Moving issues from SassDoc/gulp-sassdoc#8

Quote @ben-eb

.
├── README.md
├── assets
│   ├── css
│   └── js
└── sassdoc
    ├── assets
    └── index.html

This is a clearer, more intuitive way of running the software. Not only do the force and interactive operations become obsolete, but we tell the user that their documentation by default creates a folder for itself, and subsequent runs will update that folder.

And @hugogiraudel :

If we are willing to do this, make the folder name customisable, and chose a secure default (i.e. not sassdoc).

JsDoc is doing it this way too.

[KittyGiraudel]

@SassDoc/owners Who takes this?

[valeriangalliat]

I can, but probably not before next week.

[pascalduez]

I can, but probably not before next week.

Would be nice if @valeriangalliat could tackle this, and I would prefer to land the stream refacto before, so I don't have to rebase/redo that another time :) It's already been too much sliced till now.

[KittyGiraudel]

Alright. @valeriangalliat, your move.

[valeriangalliat]

Why not sassdoc as default? There's little chance such a folder already exists, right?
Otherwise, we can name it out like JSDoc maybe?

I'm going for out now. We can change it later.

---

Also I'm realizing this issue is way more straightforward than I thought. While it's entitled "Always output into its own directory", practically, it's just "Make <dest> an option instead of an argument, give it a default value, and remove --interactive and --force".

[FWeinb]

I am all for sassdoc. But what we want is always append the folder sassdoc. Even if the user has supplied a path.

[valeriangalliat]

From what I understood, there's no more dest argument, it's rather an option defaulting to out.

So sassdoc src will create out in the CWD, and sassdoc src --dest doc will put the documentation in doc.