Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update quickstart instructions with `new` command #966

Merged
merged 1 commit into from Apr 13, 2013

Conversation

Projects
None yet
3 participants
@benbalter
Copy link
Contributor

benbalter commented Apr 13, 2013

Quickstart instructions as written would serve an empty directory.

They instruct the user to install Jekyll (馃), cd to a directory that may not exist, and then run jekyll serve (:hurtrealbad:).

Instead, lets have them run jekyll new to stand up a scaffold site, so they can see how things work and poke around a bit.

It's one more command, but IMHO a better user experience for someone just getting started.

Update quickstart instructions with `new` command
Quickstart instructions as written would serve an empty directory.

They instruct the user to install Jekyll (:metal), `cd` to a directory that may not exist, and then run `jekyll serve` (:hurtrealbad:).

Instead, lets have them run `jekyll new` to stand up a scaffold site, so they can see how things work and poke around a bit.

It's one more command, but IMHO a better user experience for someone just getting started.
@parkr

This comment has been minimized.

Copy link
Member

parkr commented Apr 13, 2013

馃憤

parkr added a commit that referenced this pull request Apr 13, 2013

Merge pull request #966 from benbalter/quick-start-scaffold
Update quickstart instructions with `new` command

@parkr parkr merged commit 10c2445 into jekyll:master Apr 13, 2013

1 check passed

default The Travis build passed
Details

@benbalter benbalter deleted the benbalter:quick-start-scaffold branch Apr 13, 2013

parkr added a commit that referenced this pull request Apr 13, 2013

@jekyll jekyll locked and limited conversation to collaborators Feb 27, 2017

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can鈥檛 perform that action at this time.