Free and Beautiful Vue 3 Admin Template

Add found bugs as comments behind this issue. One comment - one bug. Thanks.

Testing strategy is described in #610.

Check current staging here: http://vuestic-epicmax.asva.by

❗ To note

• if you finished working on post - make a notice in header (such as "addressed in release"),
• make sure to increment the № of your bug submit so that it can be easier to track, group and fix them.
• Please leave a notice if bug reproduces only on safari or something obscure.
• P5 in header means highest priority (must be done till release). P1 - means we can ignore. 2-4 - in betweenish. When fixing, select items with higher priority.

Conventions

:rocket: means that the bug is fixed, checked and approved :eyes: means that somebody's already working on the bug report and you should pick another one

TODO

Not fixed, but in progress

Update bootstrap and boostrap-vue dependency to 4.0.0-beta3 and 1.1.0

• Fix import call (need bottstrap's functions now in scss import)
• Fix some variables
• Fix Dropdown directive
• Fix Progress Bar/Circle Progress Bar scss
• Remove Bulma-vue-expand and bulma and replace it by B4's Collapse

• transform relative node_modules @import in scss part of vue files of vuestic component to ~[node_modules] form (cf commit dc25a63 )

• Proposal for not relative JS imports for vuestic-components ( cf commit 25ab85a )

1. Internationalization (i18n)
2. Theme switch (dark/light)
3. Forms like typeforms [https://www.typeform.com/]
4. UI Blocker (during form submissions)
5. Route-change animations (like what nuxt does)
6. Keyboard navigation

The feedback (please check it!) on reddit was great. But some of the users indicated that the colors are too bright for them.

The idea is to provide a theme that's less bright (@smartapant: more calm) but generally the same. Might be more dull, so enterprise/corporate guys could use it.

You can play with color pickers on https://vuestic.epicmax.co/, then pass @asvae or @smartapant these variables with a couple screenshots.

I'm developing our site with vuestic-admin. It is very powerful framework.

I found it is upgraded 1.5.0.

How can I upgrade my 1.4.0 based project ? ? ?

Please help ~

This task is a continuation of #616

Add found bugs as comments behind this issue. One comment - one bug. Thanks.

Testing strategy is described in #610. (Reserved for vasily issues: https://docs.google.com/document/d/1S3-QwgYSouDCc1n24hXM27zAdxsp0KK8-HBAhGxyjOo/edit#)

Check current staging here: http://vuestic-epicmax.asva.by

❗ To note

• if you finished working on post - make a notice in header (such as "addressed in release"),
• make sure to increment the № of your bug submit so that it can be easier to track, group and fix them.
• Please leave a notice if bug reproduces only on safari or something obscure.
• P5 in header means highest priority (must be done till release). P1 - means we can ignore. 2-4 - in betweenish. When fixing, select items with higher priority.

Conventions

:rocket: means that the bug is fixed, checked and approved :eyes: means that somebody's already working on the bug report and you should pick another one

TODO

Now there are no correct statuses about problems below

Hi,

For my project, there will be multiple roles, say student and company. So, what I thought is entirely having two set of things in components and store modules.

So, inside src/components, I created two folders src/components/company and src/components/student and kept the related components under that.

Like that, I wanted to have multiple modules for both as the sidebar items will have different things. So, I changed /src/store/modules/menu/ into two: /src/store/modules/company/menu/ and /src/store/modules/student/menu/.

I changed the store file and all accordingly. But, I receive an error from Layout.vue due to breadcrumbs, as I am stuck and confused about how to change that in getters.js

Errors:
1. Cannot read property 'menu' of undefined | studentMenuItems (getters.js?c729:3)
2. TypeError: Cannot read property 'menu' of undefined |  VueComponent.breadcrumbs (Layout.vue?9bde:51)

below is my getters.js, please direct me how to make this work or is there a better way to solve my use-case. Please let me know.

import utils from 'services/utils'

const studentMenuItems = state => state.student.menu.items
const companyMenuItems = state => state.company.menu.items
const sidebarOpened = state => state.app.sidebar.opened
const toggleWithoutAnimation = state => state.app.sidebar.withoutAnimation
const config = state => state.app.config
const palette = state => state.app.config.palette
const isLoading = state => state.app.isLoading
const breadcrumbs = state => {
  return (keyword) => utils.findInNestedByName(state.menu.items, keyword)
}

export {
  studentMenuItems,
  companyMenuItems,
  toggleWithoutAnimation,
  sidebarOpened,
  config,
  palette,
  isLoading,
  breadcrumbs
}

I created a component here: src/components/landing/Landing.vue. I set up the route for it and when I viewed that component in the browser, it's surrounded by navbar and sidebar. Whereas, I want to achieve a page with my own design. Please suggest how would I do that?

Also, if I add an item to the sidebar, the item is displayed as if it's active. But it's not, what class I should use. Please suggest.

Hi,

I'm using vuestic-wizard in a vertical manner, the navigation buttons back and confirm are aligned in separate lines instead of being it in a single line.

Please refer the below screenshot.

Router is used only for main section, not for header or footer

What's the problem? - not possible to make pages without footer and header (required for demos) How to fix? - app root should be empty page with router view Estimate - 3 hours

1. Prepare css class to make sidebar/navbar either fixed or static
2. Make it possible to control the state of navbar/sidebar type via vuex

Quick and dirty styles might be found in #116

Interface

Fixed layout is default.

Static layout (header and navbar scoll with page)

<layout static/>

Fixed layout (header and navbar are pinned, content is scrolled independently)

<layout/> 

Right now vuestic-admin is off by a number of points:

• Number and quality of pages is way off from current competition.
• UI Elements pages do not make much sense given we have vuestic.dev.
• Dependencies are outdated

What can we do

• Priority analysis - figure out where vuestic-admin can be best across similar types of products. We probably can rely on Epicmax strengths there.
• Simplify support by introducting automated smoke testing (maybe visual testing as well).
• Add more pages (discuss which ones).

Fixed navbar and navbar menu on mobile screens. Should be applied alongside this PR: https://github.com/epicmaxco/vuestic-ui/pull/2835

Types of changes

• [x] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [ ] Improvement/refactoring (non-breaking change that doesn't add any feature but make things better)

I see that when we download the vuestic from github and build it, in the mobile version, the side bar wont work. no modifications done in the code. there is some overlap in mobile version. if i make the visibility hidden for the va sidebar then the visible links are clickable.

https://stackoverflow.com/questions/tagged/vuestic

We have multiple places where users can ask questions, let's discuss whether we wan to support any of them.

• I'm submitting a ...

  • [ ] feature request

• Do you want to request a feature or report a bug?

  • feature request

• What is the current behavior?

  • There are no Bangla language option on language drop-down

• What is the expected behavior?

  • Expect Bangla option on language drop-down

• What is the motivation / use case for changing the behavior?

  • Language localization for Bangla language

• Other information

  • I am interested to develop the feature

That's a research topic generally.

Here's a case:

• New user wants an app, that has a backend part. Let's say they come from PHP world, but that might be different frontend technology.
• They want a somewhat working boilerplate with all strings attached, where they can easily expand functionality as they figure out the basics of frameworks.

Curious if that's possible to handle from our side as well as valuable.