Add "sculpin new" command.

[opdavies]

I've created this as a proof of concept, to quickly create the base directories and files needed for a new Sculpin site using a "sculpin new" command.

I wasn't sure if the Filesystem class was already available or being injected in automatically. If so, I'd be happy to refactor the code to incorporate this.

I also wasn't sure how much to create by default. At the moment I've just added app/config/sculpin_site.yml and source/index.md with minimal information.

[TomasVotruba]

Like this!

What needs to be done here?

[opdavies]

I've cleaned up some of the things that I wanted to from the initial version.

The main remaining things for me are:

• What do we want the default structure and content to be when generating a new site?
• How interactive do we want this to be? We could use the Console component to prompt the user to enter which content types they want, what they want the site title to be etc, but it's a case of this is needed.

These are probably questions for @simensen to answer.

[beryllium]

I think this would be a great feature to have in Sculpin. A while ago I started working on a similar command (which I called "init"), but this PR is further along than my attempt.

As a sculpin user with several sites, and a tendency to want to quickly spin up simple sites, I would like to see the following functionality put in place by the "new" command (but the visual stylings of it can be completely spartan):

source/index.html
source/blog.html
source/blog/categories.html
source/blog/categories/category.html
source/blog/tags.html
source/blog/tags/tag.html
source/_posts/initial-post.md
source/_views/default.html
source/_views/post.html

That, to me, is a solid sampling of the basic functionality of a Sculpin blog. It's OK (to me) if it looks like 1996's Yahoo or 1991's first web page on first run. Themes or Templates can come along later as an additional feature.

Also, if I decide I want to use it as a site or a landing page or something other than a blog, it's easy to strip out the bits I wouldn't want.

[opdavies]

I wondered about using https://github.com/sculpin/sculpin-blog-skeleton as the starting point. I tend to start with a blank site and add the files I need (hence the minimal approach at https://github.com/opdavies/sculpin-minimal), but I can see how this may not suit everyone.

I guess that it's a question for @simensen to make, and I'm happy to implement it.

[simensen]

@beryllium @opdavies very old versions of sculpin had the concept of generating a skeleton. it shipped two two skeletons stored within the package itself. you can get an idea here:

• https://github.com/sculpin/sculpin/tree/1.0/src/sculpin/Resources/skeleton

if you want to implement something along these lines (shipping a skeleton) i'm all for it.

[opdavies]

@simensen Awesome. I'll take a look at that. :)

[simensen]

@opdavies sure thing. the command was called init and it was pretty simple:

• https://github.com/sculpin/sculpin/blob/1.0/src/sculpin/console/command/InitCommand.php

I can't remember why it was removed. Might just be that I decided to try and ship skeleton repositories instead. And I also wanted to focus on Embedded Composer.

[Xerkus]

Common way to provide project setup functionality currently is via composer create-project
I am going to close this PR as it is no longer relevant.

Should you want to resume this feature, https://github.com/sculpin/sculpin-blog-skeleton would be the correct place to do so.

[simensen]

@opdavies If we pick this up again, I'd be happy to consider it. In the meantime, we're trying to clean up the repository so that we can get a better idea where things stand WRT actionable issues & PR's.

[Xerkus]

Created issue to track this topic at sculpin/sculpin-blog-skeleton#47