mvktsk
commented
3 years ago Task https://virtocommerce.atlassian.net/browse/VP-6910 has been created
Closed CKGrafico closed 3 years ago
mvktsk
commented
3 years ago Task https://virtocommerce.atlassian.net/browse/VP-6910 has been created
tatarincev
commented
3 years ago Hi @CKGrafico, I'm glad that you consider this theme for your projects, and I'm happy to answer all of your questions:
Q: Why MPA and not NUXT?
A: The main reason why we chose MPA is the ability to continue to use existing storefront functionality and have mixed mode to inject JS components into pages that are rendered on the server-side along which the many useful features that are difficult to reuse in other frameworks. Also, here are other things that influenced our decision:
Q: Do we have to modify the code of the template or we can extend the template (like wordpress themes for example)? A: The starter theme is designed for do any customization via direct theme code changes, you can feel free to edit any theme resources within your solution.
Q: Is vue 3 and hooks in your roadmap? A: Not in this year.
Q: We will probably need to do a lot of custom things in our app, is better to start from scratch communicating to the API from Virto or extend this template? A: To answer this question need to dive into your context in more detail. Anyway if you have a plan to build eCommerce the many eCommerce domain things can be reused and be taken from the existing theme.
I would like to recommend you to use these project branches for your new project: Keep in mind that these projects are under development.
Recommended storefront version:
vue-starter-theme/dev - The next generation of starter theme that located in dev branch. This version is absolutely different from the version in the master that built with using https://www.storefrontui.io/ semantic UI components and new composition-API VueJS instead of vuex state management.
https://vst-storefront.develop.govirto.com/ - live theme demo
Storefront 6.0 (beta) - The version of a storefront that fully adapted to work with VirtoCommerce xAPI (graphQL) and doesn't contains any eCommerce business logic (host for themes with crosscutting things) and can be used as binary without direct code changes in the custom projects.
CKGrafico
commented
3 years ago Hello @tatarincev first thanks for your quick and super useful reply, I know that you have probably better things to do and you have used your time to reply all my questions.
Q: Why MPA and not NUXT? Thanks, clarified and totally understood.
Q: Do we have to modify the code of the template or we can extend the template (like wordpress themes for example)? It's clear, that means that there is not something like "child templates" I mean if you update the template will be difficult to update our theme or do you have the "child like system".
Q: Is vue 3 and hooks in your roadmap? Ok, thanks 👍
Q: We will probably need to do a lot of custom things in our app, is better to start from scratch communicating to the API from Virto or extend this template? Its ok with all the info you have provided
I would like to recommend you to use these project branches for your new project: Keep in mind that these projects are under development. Amazing tip, thanks!!
OlegoO
Hello se are starting a new project with Virto and this seems the most relevant theme. We can manage with different Front technologies and we are happy with vue but we have to be sure that this is your recommendation before start.
Additional questions: