Motivation

Various functionality needs additonal vue components to work. For example, Drupal CMS integration needs vue-components for that, or a some frontend-admin-menu also.

By allowing the optional addition of layers the layers could add or even overwrite lots of frontend functionality on a flexible basis. It can do that without replacing the main frontend repository + it allows re-using the layers in projects when desirable as well.

Proposed resolution

Optionally add a nuxt-layer to github codespaces setup, so layers like
- https://github.com/drunomics/nuxt-drupal-cms-layer
- github:StirStudios/stir_nuxt_base#release/nuxt-ui-lupus
can be easily added.

Comments

fago created an issue. See original summary.

glynster’s picture

glynster commented

@fago, this makes total sense and the entire reason behind Nuxt layers.

How do you propose I can help here?

fago’s picture

fago
Primary language German
Location Vienna
commented
Status: Active » Needs work

I've created a new layer for drupal-cms and starting to test it via:

> npm create nuxt@latest -- -t layer

> How do you propose I can help here?
How is your layer coming along? Do you have some usage instructions, on how it can be installed on top of e.g. the naked or some other setup? Seeing necessary steps there would help me.

I'm wondering whether we want to locally clone the layer into ~/layers/ directory and have it registered that way, or whether we want to use the extends + github:repo.. syntax. I guess for working with it + discoverability the manual clone would be a bit better. Any preferences / opinions on that?

Repo: https://github.com/drunomics/nuxt-drupal-cms-layer

fago’s picture

fago
Primary language German
Location Vienna
commented
Issue summary: View changes
fago’s picture

fago
Primary language German
Location Vienna
commented

as commented in the parent issue, the approach seems to work good for https://github.com/drunomics/nuxt-drupal-cms-layer
-> what's left here is the codespaces setup