Assemble's highly modular nature makes it difficult to discover methods that are added via mixins or inheritance. For example, .use and .define are provided by Base and implicitely added through Templates.

It would be a huge help to have some basic, generated JSDocs that incorporate all of the default packages. JSDoc provides the @mixinand [`@mix

To avoid warnings by people who knows nothing about alphabet, I suggest to write grunt-task/small tool wrapped with task, that will sort out all properties in css in alphabetical order.

moreover, we can add indentation check and fix etc.

Any thoughts on this? It's not just for me but for anyone that comes in the future, and I'd like them to have somewhere to start instead of trying to backtrace what's left. Things like coding standards, naming, tags, making PRs, Issue formats, etcetc. All in one place.

I'd just like to hear what the other devs think is "ideal documentation" before actually going round doing mass changes.

See #423

Using the wrap: true option results in the module being wrapped in

(function(angular, undefined) {
    ...
})(angular);

Passing undefined as an argument conflicts with best practices and the no-shadow-restricted-names rule in ESLint. This should not be the default behavior of wrap: true in my opinion.

https://eslint.org/docs/rules/no-shadow-restricted-names

A worka

The options.encoding setting is only used in the function generateFileHash

The documentation tells that it will be used when reading and writing the files.

You should pass the encoding setting to the grunt.file.read and grunt.file.write calls in the function replaceInFile

Webpack/Grunt Configuration (webpack.config.js, webpack part of Gruntfile.js)

Same as in #153

// Gruntfile.js

const webpackDevConfig = require('./webpack.dev')({environment: 'dev'});

'webpack-dev-server': {
      options: {
        webpack: webpackDevConfig,
        host: 'dev.mysite.com', // does not work if this is specified in webpack config devServer instead
        p

The documentation of the PlotOptions object at http://www.jqplot.com/docs/files/jqPlotOptions-txt.html is garbled. I don't know if this is an error in the source file or in the code which converts it to HTML, but it means that there is currently no easy way to access the PlotOptions reference data.

As I understand video-upload-on-pass: false is extra-deprecated and now we should use recordVideo: false.

It would be good to update all docs and examples with actual config params.

The WordPress project has switched to using wp i18n make-pot (docs). It'd be great if this package switched over too, for two specific advantages:

1. Full PHP 7 support.
2. Also parses JavaScript files.

cc @schlessera @swissspidy

The current sequence for install by database load is:

• sql-drop
• load database
• update database

In order to safely load databases from alternate environments, we should add a cache clear after database load and before database update. If registry-rebuild is present, we might want to run that as well.