Skip to content

Commit

Permalink
Merge branch 'release/0.5.1'
Browse files Browse the repository at this point in the history
  • Loading branch information
tylerbutler committed May 28, 2014
2 parents b35bf42 + fc83b26 commit b068d16
Show file tree
Hide file tree
Showing 4 changed files with 29 additions and 11 deletions.
13 changes: 10 additions & 3 deletions engineer/docs_source/changelog.rst
@@ -1,9 +1,16 @@

.. _changelog:

=========
Changelog
=========
=============
Release Notes
=============

version 0.5.1 - May 28, 2014
============================

- Fixed issue with precompiled LESS files.
- Updated documentation.


version 0.5.0 - April 10, 2014
==============================
Expand Down
19 changes: 14 additions & 5 deletions engineer/docs_source/cmdline.rst
Expand Up @@ -55,13 +55,22 @@ folder structure, a :doc:`settings file <settings>`, and optionally some sample

**Usage**::

engineer init [-h] [-v] [-s CONFIG_FILE] [--no-sample] [-f]
engineer init [-h] [-v] [-s CONFIG_FILE] [-m {azure}] [--sample] [--force]

.. option:: --no-sample
.. option:: -m, --mode

By default, the ``init`` command includes some sample content to provide a starting point for a new site. By
passing this option, however, no sample content will be created.
Initializes a site structure designed for deployment to a specific hosting service such as Azure.
See :ref:`deployment` for more details. Valid options:

- ``azure``: Initializes a site for deployment to Azure.

.. option:: --sample

By default, the ``init`` command does not create sample content to provide a starting point for a new site. By
passing this option, however, sample content will be created.

.. versionchanged:: 0.5.0
Replaced the ``--no-sample`` option with this, effectively reversing the default.

.. option:: -f, --force

Expand Down Expand Up @@ -137,7 +146,7 @@ implemented.
.. _engineer emma:

``engineer emma``
------------------
-----------------

.. program:: emma

Expand Down
2 changes: 2 additions & 0 deletions engineer/docs_source/deployment.rst
@@ -1,4 +1,6 @@

.. _deployment:

========================
Deploying Engineer Sites
========================
Expand Down
6 changes: 3 additions & 3 deletions engineer/docs_source/dev/theme_creation.rst
Expand Up @@ -228,8 +228,8 @@ LESS

In addition to CSS, Engineer can automatically compile LESS stylesheets during a site build,
so you are free to use LESS rather than CSS for your styles. When linking to your LESS stylesheet in your templates,
you should use the ``render_less_link`` `macro <macros>`_. This will ensure that the stylesheet is compiled as part
of the site build process if needed.
you should use the ``render_less_link`` :ref:`macro <macros>`. This will ensure that the stylesheet is compiled as
part of the site build process if needed.

Starting with Engineer 0.5.0, themes can include a 'precompiled' version of the LESS stylesheets they need. This is
useful since in most cases users of your theme will not be making modifications to your LESS files. Thus,
Expand All @@ -238,7 +238,7 @@ referencing a pre-built version of the stylesheet makes for faster builds.
In order to include a precompiled version of your stylesheets, simply add it alongside your regular stylesheet and
append ``_precompiled`` to the name. For example, if your stylesheet is called ``dark_rainbow.less``,
then your precompiled version should be called ``dark_rainbow_precompiled.css``. As long as you are referencing your
stylesheet from your templates using the ``render_less_link`` `macro <macros>`_,
stylesheet from your templates using the ``render_less_link`` :ref:`macro <macros>`,
the precompiled version will automatically be picked up during a site build. No other changes are needed.


Expand Down

0 comments on commit b068d16

Please sign in to comment.