assemble / generator-assemble

Yeoman generator for Assemble, the static site generator built on Grunt.js. Kickstart new Assemble projects in just a few seconds, including templates, data, layouts, and a theme.

Home Page:http://assemble.io/docs/Resources.html

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Why are the options passed under pages parameter in gruntfile ?

fpoirier1 opened this issue · comments

I'm trying to understand assemble's architecture. Why are the options passed through the pages parameter. Like this :

   assemble: {
      pages: {
        options: {
          flatten: true,
          assets: '<%= config.dist %>/assets',
          layout: '<%= config.src %>/templates/layouts/default.hbs',
          data: '<%= config.src %>/data/*.{json,yml}',
          partials: '<%= config.src %>/templates/partials/*.hbs',
          helpers: '<%= config.src %>/templates/helpers.js',
          plugins: ['assemble-contrib-permalinks','assemble-contrib-sitemap', './grunt_tasks/menu.js'],
        },
        files: {
          '<%= config.dist %>/': ['<%= config.src %>/templates/pages/*.hbs']
        }
      }

pages is a grunt "target", so the options are related to that target, not "assemble pages" per se, although I can now see how that might be confusing.

fwiw we did that a couple of years ago when we had no idea what we were doing lol

I see ! Thanks !