https://github.com/viur-framework/shop-components

A collection of Vue.js components for the ViUR shop.
https://github.com/viur-framework/shop-components

ecommerce shop viur viur-framework viur-shop vuejs

Last synced: 6 months ago
JSON representation

A collection of Vue.js components for the ViUR shop.

• Host: GitHub
• URL: https://github.com/viur-framework/shop-components
• Owner: viur-framework
• License: mit
• Created: 2024-03-27T19:54:03.000Z (over 2 years ago)
• Default Branch: main
• Last Pushed: 2026-01-28T20:36:09.000Z (6 months ago)
• Last Synced: 2026-01-29T10:57:33.626Z (6 months ago)
• Topics: ecommerce, shop, viur, viur-framework, viur-shop, vuejs
• Language: Vue
• Homepage:
• Size: 5.26 MB
• Stars: 2
• Watchers: 4
• Forks: 2
• Open Issues: 7
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

          


    

    
ViUR Shop Components

    

        

    

    

        

    

    


    A collection of Vue.js components for the ViUR

    shop.



### Structure

* **Main components** have to be exported in `./src/main.js`. Main Components should be in folder `./src/components`.

* **Ui Elements** for main components should be in `./src/components/ui` so everyone who contributes can see if there is an element/component already for their use.  

* Components should be as small as possible to make the code easier to access and understand, thats why the directory structure has importance.  

* Every logic/function according to articles/items/cart or anything else should be in the `cartStore` in `./src/stores/cart.js` - reason is as follows - all components get their data with so called props which are not "reactive" by nature. We want to trigger a rerender if we change/add/edit... items thats why anything according to that should be in the cartStore. Read the cartStore carefully and use the already existing states to grant a clean rerender/reactive process. The props all get updated as soon as the main states get updated in the `cartStore` -> rerender --> profit...

Try to understand this structure and adopt it with new components for easy implementation without much effort.

Real documentation is coming soon...