v0.5.1

Bug fixes

• I18n now works correctly for pages (created via harmonic new_page). (@viniciusdacal)
• Fixed a dependency issue which was breaking published packages¹ (es20xx). (@UltCombo)

¹ This means previous releases of Harmonic may not be working anymore. From now on, the releases are more future-proof. Please update your Harmonic installation (npm i -g harmonic).

This is because Harmonic used to depend on the latest backwards-compatible babel-runtime version, which in turn used to do the same with the Regenerator runtime, whose changes were not actually "backwards-compatible" with code generated with any previous Regenerator version. The compiled code which Harmonic ships always stays the same, and thus could be broken whenever a new Regenerator version was published. This is all sorted out now, though.

Docs

• Fixed typo. (@brenopolanski)

Internal

• Fixed linting errors. (@viniciusdacal)
• Improved deploy automation (es20xx). (@UltCombo)

---

Huge thanks to @viniciusdacal for making this release possible. 😄

v0.5.0

Enhancements

• harmonic build is now up to 40% faster.
• harmonic build now logs the time it took to generate the build. Each build in harmonic run's watch mode will also log the build time.

Docs

• Finished rebranding (ES6 Rocks -> JS Rocks).
• Fixed Gitter room link.

v0.4.2

Bug fix

i18n wrong behaviour fixed

v0.4.1

Bug fixes

• Fixed the front-end harmonic.js file. It previously contained extraneous CommonJS syntax.

v0.4.0

Breaking changes

• The CSS preprocessing output is now written directly to the public/css directory (removed the intermediary write to the theme's resources/css directory). In case your theme uses preprocessing, make sure your theme's resources/css directory does not contain an outdated compiled CSS file, otherwise it will overwrite your theme's newer preprocessed CSS.

Improvements

• Watch, rebuild, reload! harmonic run will now watch all files in the src directory and in the currently selected theme, triggering a new build and reloading the opened pages when changes are detected.
• Harmonic commands can now be run from subdirectories of a Harmonic site. (@soapdog)
• Improved promises and async functions error handling -- this fixes the main source of silent fails and makes Harmonic's code cleaner.
• Harmonic will now throw an error when it fails to copy files (e.g. in harmonic init, harmonic build). Previously, it would fail silently.
• Updated Less preprocessing logic. (@robsongajunior)
• Cleaned up Stylus and Less preprocessing logic to use async functions.
• Updated README's badges.

v0.3.0

This release adds a user defined resources folder that is copied to public during build. This folder is copied after the theme's resources are copied so it can be used to overwrite files as well.

If there is no resources folder present then Harmonic displays a warning saying that no user resources were copied during build. This happens if the folder is not present or if there was an error in the copying process.
The copyResources function was splitted into two functions called copyThemeResources and copyUserResources.

PS: All credits for @soapdog in this release.

v0.2.0

Breaking changes

• The config file of a theme is now named config.json. Previously, Harmonic would look for a file named harmonic.json inside the theme.
• The harmonic.json's template property has been renamed to theme.
• If the currently selected theme contains a config.json file and the contents of this file is not valid JSON, Harmonic will now throw an error instead of silently ignoring the invalid config file.
• Errors in the CSS preprocessing will now throw an error in the build process. Previously these errors were silently ignored.

Improvements

• harmonic init will now automatically install the site skeleton's necessary dependencies.
• You can now disable CSS preprocessing by setting "prepocessor": false in the theme's config.json or site's harmonic.json.
• Added an useful error message when specifying an unsupported CSS preprocessor.
• Improved harmonic config success message.

Internal

• Harmonic no longer pollutes the global scope.
• Started making use of async functions and promisification utilities.
• Overall refactoring.

v0.1.0

This release introduces harmonic-themes.
You can check it out the Themes page to see full spec of this feature.

v0.0.11

New features

• Added Node.js 0.10, 0.12 and io.js support.
• harmonic run now opens the site in the default browser automatically, and new_post/new_page open the created markdown file(s) in the default editor automatically as well (unless the --no-open flag is passed).
• All harmonic commands now accept an optional project path argument, which (still) defaults to the CWD.
• Added Less preprocessor support to templates (this will be moved to a Harmonic plugin in the future).
• Added useful error message when running Harmonic commands in a non-Harmonic project directory.
• Added useful error message when running unrecognized Harmonic commands.

Bug fixes

• Many fixes regarding Promises and race conditions.
• Fixed crash when posts/pages directory contains non-markdown files (e.g. .DS_Store).

Internal

• Build: all Node.js .js files are now compiled with Babel.
• Build: Grunt.js -> gulp, based on the slush-es20xx workflow.
• ES.next: all the CommonJS syntax has been replaced with ECMAScript Modules syntax.
• Development: fixed npm link in Unix-based OS's.
• CI: added unit tests.
• CI: use container-based infrastructure on Travis.
• Streamlining internal functions for soon-to-be-implemented API's consumption.
• ES.next: make use of many more ECMAScript 2015 features.
• Lots of general code refactoring and cleanup.

Miscellaneous

• Docs: added Contributing Guide.
• Docs: updated the Wiki's Installing page.
• Docs: revamped the repository's README header.
• Added Harmonic Gitter room.

0.0.9 release

• Fully multi-platform support (Linux, Mac, Windows)
• Removed old trash
• Better bootstrap with init command
• i18n support
• Basic documentation
• Create page command
• Bind pages to the browser API

A special thanks to the awesome contributors for this release:
@leobalter, @UltCombo, @rssilva, @soapdog