2.0.1

Patches

• Show badge for coding style: 770562c
• Use xo for linting: e5e3738
• Use a single plugin for transpilation: 51fae6c
• Don't use extensions for binaries: e60ce85
• Clean temporary directory before building: 5247f5f
• Removed beerpay badge & include all the languages: 2586ba3
• Also no need for Gitter anymore: 644991e
• Removed command line indicators: af4705c
• Suggest opening help instead of listing commands: 28f14b5
• Lowercased text files: 5b4bd58
• Deprecation notice added: 126c64b

v2.0.0

Major Changes

• Removed "cory deploy": We highly recommend using now instead. For node projects, it's just as easy as using GH's service and the advantages are even bigger: Free & instant SSL, independent deployment with a single command and having the ability to run Node.js code (not just static sites): c50dc19

Minor Changes

• Defined more scripts for deploying properly: ee43e5a
• Added default license to template (MIT): 15a1a5f

Fixes

• The server now stops running after the process was cancelled: abffd0a
• Updated all dependencies to the latest version (no idea with greenkeeper didn't do that, will definitely look into it): 8b624cc
• When automatically building your site, cory will now inherit the stdio of the parent process. That means if an error occurs while generating the site, you'll get the error printed out: f2d83b1
• Switched over from commander to args: 6e44ce4

v1.2.0

New

• Improved design of boilerplate
• The source code is now all ES2015. Before publishing a new version, it'll gets transpiled completely.
• Broccoli is now being used to build assets. This decreases the initial build time to just a few milliseconds and re-enables transpiling for client-side scripts
• The boilerplate now includes a README.md file
• After generating a new site, cory will automatically install all missing dependencies for you

Updated

• "browser-sync" to 2.12.3
• "nodegit" to 0.12.2
• "fs-extra" to 0.27.0
• "front-matter" to 2.0.7
• "update-notifier" to 0.6.3

v1.1.0

This update adds support for update-notifier. This basically means that you'll get notified if there's a new version of cory available when running one of its commands.

Updated

• "chokidar" to 1.4.3
• "nodegit" to 0.11.6

v1.0.0

According to SemVer, a package should already be 1.0.0 if it's stable and being used in production. And since that applies to cory, here's the release! 🙈

Also

• Small tweaks within the README.md file
• New, improved description
• Auto-generated badge for license added (MIT)
• Code style fixed
• Instead of telling npm to ignore certain files, it will now be told to only include the necessary ones

Updated

• "nodegit" to 0.11.3
• "uglify-js" to 2.6.2
• "front-matter" to 2.0.6

v0.4.0

New

• Good looking URL structure: Generated pages will now be accessible through /<page_name> instead of /<page_name>.html. This also means that they're nestable. Posts will also be available on /posts/<post_name>, rather than on /posts/<post_name>.html
• When using the serve command in combination with the --watch option, cory will now use BrowserSync's built in server and watching functionality. This improves the speed of the whole process and makes the command line output much prettier and easier to understand.
• The deploy command now respects your scripts defined in package.json. And if there's one called "deploy", it will execute that, rather than deploying to GitHub Pages.

Fixed

• When running serve oder build using the --watch option, cory will now skip watching .git folders.
• The deploy command is now listed unter "Options" within the README.md file

v0.3.0

New

• Command deploy added: Handles all the steps for deploying to GitHub Pages for you. Read more about how it works here.
• Running npm start in a site's directory will now start cory's development server.
• When checking if the current folder is a site, cory will now examine if one of its commands is being used within package.json, rather than simply checking for the existence of config.json.

Fixed

• Decreased time for initial build from ~2000ms to ~200ms by replacing the JS transpiler (Babel) with a simple minifier. Transpiling might be re-added as an optional feature later.
• Node modules and .git files will now be ignored when building. Decreases the build time heavily.

v0.2.0

• Posts: Markdown files located in the posts folder will now be compiled, wrapped into the default handlebars template and then outputted as HTML files in the posts directory located in the outputDir.
• Front Matter: All pages and posts can now contain Front Matter properties, which will allow developers to read certain values directly in the template. Besides that, it also allows people to set a different layout for each page/post. Read more about this feature here.
• The default layout can now be specified using the config property defaultLayout.
• All config properties are now available to be used in pages, posts or templates. If you want to output their value, just use their appropriate template tag. As an example: You can output the port on which the site is running by using {{port}}. And the best about this is, that you can add whatever you want to the config.json file and it will be available in your templates.

v0.1.3

• When serving the site while watching, the correct port (specified in the config.json) will be used again (the module that does the livereloading used its own number before this change)
• Sourcemaps are now enabled by default and can be controlled using the sourceMaps property
• README.md now shows all config options and their defaults
• If an error occurs while using init, it will now be logged
• Improved the message that shows up when the server started running (while using --watch)

v0.1.2

• When using --watch while letting cory serve your site, it will now directly reload files within your browser if they change.
• The external URL is now being outputted beneath the local URL when using serve
• Static, uncompiled files will now simply be copied over to the output, too.
• The --watch option can now also be used in combination with the serve command.
• Pages will now be rebuild if their layout changed
• There's now a Gitter Room for discussing things related to the project or asking questions