9d45644e6c
With gem-based themes being bundled in the new site via the `Gemfile`, we should ask folks to use Bundler wherever possible. This should lead to more successful installations and getting the base site setup properly. The only trouble this introduces is it puts a dependency on Bundler. That said, I'm totally fine with requiring everyone use Bundler for this site. How could we best install bundler in these instructions? /cc @jekyll/documentation
994 B
layout, title, permalink
| layout | title | permalink |
|---|---|---|
| docs | Quick-start guide | /docs/quickstart/ |
For the impatient, here's how to get a boilerplate Jekyll site up and running.
{% highlight shell %} ~ $ gem install jekyll ~ $ jekyll new myblog ~ $ cd myblog ~/myblog $ bundle install ~/myblog $ bundle exec jekyll serve
=> Now browse to http://localhost:4000
{% endhighlight %}
If you wish to install jekyll into an existing directory, you can do so by running jekyll new . from within the directory instead of creating a new one. If the existing directory isn't empty, you'll also have to pass the --force option like so jekyll new . --force.
That's nothing, though. The real magic happens when you start creating blog posts, using the front matter to control templates and layouts, and taking advantage of all the awesome configuration options Jekyll makes available.
If you're running into problems, ensure you have all the requirements installed.