consolidate configuration and compilation objects

[thescientist13]

Type of Change

• New Feature Request
• Documentation / Website
• Improvement / Suggestion
• Bug
• Other (please clarify below)

Summary

It might make sense to consolidate these two objects, to reduce the cumbersome nature of passing them around.

Note: this should only focus on internal configuration / refactoring. Have opened #40 for exposing userland APIs

Details

1. Consolidate config into compilation object
2. Update all references throughout the build pipeline
3. All tests should pass
4. Unify with webpack configuration per [RFC] User Workspace PoC #33 (comment)
5. A number of TODOs raised discussed in Internal dev watching/rebuilding script and commander interface #36
   • publicPath
   • userWorkspace, pagesDir in webpack configs
   • config
   • entry in webpack.config.develop.js

This will help clear a path forward for the following issues:

• As a user I would like default page template values based on filepath  #30
• As a user I would like to configure my projects metadata #5
• As a developer I should have an app template provided by default #32
• others probably

[thescientist13]

Might make sense to think of less as a configuration object, and more as a sort of internal state just for greenwood to configure itself appropriately and to provide a single source of truth (compilation) for all tasks and configurations.

So we can hoist it all to index.js or init and setup it up like

const userHasWorkspace = /* test for user's source directory */;
const userHasWorkspacePages = /* test for user's source directory */;
const rootContext = userHasWorkspace ? /* users src/ directory */ : /* internal templates */ ;
const pagesDir = userHasWorkspacePages ? userHasWorkspacePages : /* internal templates */ ;
const hasTemplates = /* etc */;
// figure out all context situations

const contexts = {
   pagesDir: path.join(rootContext, pagesDir),
   scratchDir: path.join(process.cwd(), './.greenwood/'),
   templatesDir: path.join(rootContext, '../templates/'),
   publicDir: path.join(process.cwd(), './public'),
   pageTemplatePath: 'page-template.js',
   appTemplatePath: 'app-template.js',
   default: true
}

Then have this "cascade" / passed down as needed. Then for #40 , we can just expose a single file in the user's root directory where they can pass in their own src/ directory and then all we would need to do is override rootContext . 👌