Use nuxt-layers for easy frontend component distribution

Created on 16 February 2025, 3 months ago

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 the gitpod setup when an environment variable is set (via URL parameter).

E.g. the optional variable FRONTEND_NUXT_LAYER=github:StirStudios/stir_nuxt_base#release/nuxt-ui-lupus could add the respective nuxt-layer to a nuxt-based frontend.

πŸ“Œ Task
Status

Active

Version

1.0

Component

Code

Created by

πŸ‡¦πŸ‡ΉAustria fago Vienna

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @fago
  • πŸ‡ΊπŸ‡ΈUnited States glynster

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

    How do you propose I can help here?

  • Status changed to Needs work 9 days ago
  • πŸ‡¦πŸ‡ΉAustria fago Vienna

    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?

Production build 0.71.5 2024