Ready to Go Nuxt Template

Presently for each new site I create, I'm cloning an existing project and modifying some variables...

I've reached a good point with this where most of the variables I'm changing are in the same place, and can also be set as ENV variables...

...but the Entities and custom fields do differ, which means some template modding and that's a little more work.

Desired Outcome

I should have an Open Source template here on GitHub which features:

Template agnosticism
Field agnosticism

...where in each case, the site can be built from a schema available via the API endpoint.

This schema should feature:

All publishable Templates
Template fields
- Template field types

E.g.

{
  id: 1,
  slug: 'posts',
  fields: [
    {
      title: 'String',
      image: 'Upload',
      content: 'Rich Text',
    }
  ]
}

This is already highly achievable as it is the exact form of the data we currently store.

IF first field is 'String', treat it as a title class for display. 'Upload' should yield an img (we should add an 'Image' type as distinct, but have not yet). 'Rich Text' should yield a div with HTML content.

We also have 'Long Text' and 'Date' types to consider, and this doesn't offer us any help with consideration of created_at, updated_at and published_at... but we know they're there.

I do have plans to allow the user to mod the API JSON response... but... well, this won't be designed to work with that necessarily. It should be built to work specifically with default output...

Question: How do we know if an image is a post's featured image? Maybe title = first of 'String' type and img = first of 'Upload' type. Sounds reasonable to me. ... Anything else?

Additional Nuxt Features

The dynamically created pages and routes should also be present when nuxt generate is run. This shouldn't be too difficult to achieve.

thombruce / helvellyn

Ready to Go Nuxt Template #91

Desired Outcome

Additional Nuxt Features