You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I just thought I'd throw this out there but I was wondering for a future version of wikijs
If there had been any thought over using nuxt as a framework.
For the client side of things there's a feature called layers https://nuxt.com/docs/getting-started/layers
You can just create a layer that sits on top and replaces the existing vue components as a sort of override
As an example With they're docus setup - https://github.com/nuxt-themes/docus which is a thing intended for static docs
Adding a layer to that mean you can just create custom themes by selectivley replacing individual vue components.
Which is handy for creating custom or branded themes or layouts.
I can see just being able to create custom layout overrides or themes for wikijs by end users as a handy thing.
From the server point of view I'm not sure if there'd be any benift with respect to the API part of the framework.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
I just thought I'd throw this out there but I was wondering for a future version of wikijs
If there had been any thought over using nuxt as a framework.
For the client side of things there's a feature called layers
https://nuxt.com/docs/getting-started/layers
You can just create a layer that sits on top and replaces the existing vue components as a sort of override
As an example With they're docus setup - https://github.com/nuxt-themes/docus which is a thing intended for static docs
Adding a layer to that mean you can just create custom themes by selectivley replacing individual vue components.
Which is handy for creating custom or branded themes or layouts.
I can see just being able to create custom layout overrides or themes for wikijs by end users as a handy thing.
From the server point of view I'm not sure if there'd be any benift with respect to the API part of the framework.
Beta Was this translation helpful? Give feedback.
All reactions