As a user I would like default page template values based on filepath

[thescientist13]

Type of Change

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

Summary

Front matter for a give page may look something like

---
path: '/hello'
label: 'hello'
template: 'page'
---

### Hello World

This is an example page built by Greenwood.  Make your own in _src/pages_!

I think we could easily infer from defaults from the file name / path

• Label
• Path
• Template (page is default)

Details

Allow Greenwood to provide defaults for the following, given a file path of
src/pages/blog/2019-03-31/index.md

• Label: index
• Path: /blog/2019-03-31/
• Template: 'page'

[hutchgrant]

label is still required because we use it for the web component element name e.g. <wc-md-helloworld></wc-md-helloworld> .

Although, we could use the file's name plus randomly generated string e.g. <wc-md-helloworld-dgfhj23re></wc-md-helloworld-dgfhj23re> However, if we do that, it would be impossible to guess the element name of a component pre-build. There's a chance someone wants to re-use a generated component(don't have an example, but it's possible?). Perhaps that should be an exception not the rule.

The path var can be removed and is fixed in #35. If no template, we could assume default page-template yes. Also fixed in #35.

edit: this problem of using labels isn't that simple. wc-md-loader requires a label to export the markdown to a generated component. IF we had wc-md-loader randomize the label, we wouldn't be able to retrieve the generated variable for our writePageComponentsFromTemplate function.

We can certainly use everything in this project with a generated label name, but the wc-md-loader will not bundle properly without it :(

[thescientist13]

Actually, this one seems a little ambition for a Sprint 1, maybe it should get put aside for a later sprint I think?