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
Right now vuestic-admin is pretty much a project boilerplate encased in repository.
But landing is selling page for vuestic-admin itself. So it's great idea to separate them. We still want to keep Vuestic landing open source, so that users can use it to create similar landings or observe best practices.
We want to reuse vuestic ui docs project as much as possible. Most of the design from vuestic landing page is taken for admin design.
Keep placeholders for documentation pages. At first - we don't need any pages, but at engine level these will be needed somewhere in the future (i.e. you can leave several pages in docs, but no navigation from admin page, so you would be able to only go there by url).
We would need to change domain. admin.vuestic.dev - would go to landing. admin-demo.vuestic.dev - to admin project itself (currently admin.vuestic.dev). We can do this after implementation.
Bonus points for abstracting away (maybe using as a dependency) vuestic docs logic that's common across ui and admin docs.
We want to move analytics (tag manager) from vuestic admin here. Demo should have no analytics.
The text was updated successfully, but these errors were encountered:
Right now vuestic-admin is pretty much a project boilerplate encased in repository.
But landing is selling page for vuestic-admin itself. So it's great idea to separate them. We still want to keep Vuestic landing open source, so that users can use it to create similar landings or observe best practices.
Other
admin.vuestic.dev
- would go to landing.admin-demo.vuestic.dev
- to admin project itself (currently admin.vuestic.dev). We can do this after implementation.The text was updated successfully, but these errors were encountered: