I'm trying to think of the best approach to reuse my components for different brands,
In the pages folder in my Nextjs application, I want to create pages for different brands, each brand has a primary color and others characteristics. How can I change the the SASS and reuse the components?
Thank you!
[1]: https://i.stack.imgur.com/9ahHJ.png
Related
I am using Vue all over the place in my Laravel project. I have a couple of views, and a dozen components inside these views that I have registered in app.js. Inside these components I have more components. Now the fun part starts when I want one component to communicate with another. What is the most efficient way to exchange information between different Vue components given that these are seperated by different laravel views (via include)?
The proper way for many components across your project to update when there are state changes would be to use VueX.
VueX moves your entire app state, methods, etc. to a centralized location that your components can leverage.
https://vuex.vuejs.org/en/intro.html
How to update data in multiple places without reloading the page in Vue.js?
This is my example.
When I add a new application, a new reminder is created. How to use this data in different places on the page?
Important: all elements are in different components.
Use Vuex or a global event bus depending on the complexity of your application.
If your application is starting to become more enriched with Vue components that need to communicate beyond simple child/parent and parent/child communications, then Vuex should be a good fit.
I am not going to go into depth about the technicalities because that information can be found in the documentation. Good luck.
I want to make an MVC 5 app that will allow users to customize views/pages, create new ones. On the custom pages they can set-up widgets and be able to save the views. Also they should be able to setup the default view that will be loaded by default.
Any ideas how can I achieve this? I believe the views should be saved in the database.
EDIT:
I found this template engine RazorEngine. This seams to be what I am looking for. Anybody has any experience using RazorEngine?
I think you should try some CMS like dotnetnuke etc. other wise build your own framework for all the things so that it can save and fetch your details to and from database.
I have a Magento site with one domain, one store and a store view for each language. I need to add a mobile version of the site and have that in all the languages.
If I add another store for the mobile version then store views for each language, I land up duplicating all the languages in the admin area.
The only solution I can see is to have 2 instances of Magento. One with all the store structures (acting front end – install A) and one with all the product (acting backend – install B)
Install A would have two stores and all languages per store and install B would have one store and store views for each language so we only manage each language once.
We would then need to connect these two Magento instances using the API (xml with SOAP). This way we manage each language once and the front end can have as many variations of that language as we like.
Does this look like a workable solution or is there a simpler way to achieve this functionality?
You don't need 2 magento versions.
Magento supports different themes on the same store view for different devices.
All you need to to is to configure a different theme.
For this go to: System->Configuration->Design, select each store view from the top left selector, or Default config if you want to use the same theme for all languages.
In the Theme section you can click on the Add Exception button under the field you need changed (most probably all that support exceptions) and fill in the following.
Matched Expression - iPhone|iPod|BlackBerry|Palm|Googlebot-Mobile|Mobile|mobile|mobi|Windows Mobile|Safari Mobile|Android|Opera Mini
Value - The name of your mobile theme.
I am wondering how to manage my product catalog for Magento efficiently. I keep one stock of products and sell them through multiple websites, those websites are in turn all in multiple languages.
The most common advice is to create a store for each website and a different store view per language, in which you can translate the product description. This doesn't seem very efficient to me. For example, if you have 4 different websites, each offering products in English and in Spanish, you have to do the same translation 4 times for each website. This becomes very cumbersome for multiple websites in multiple languages and a lot of products.
What I ideally would do, is maintain one translation per language and keep track of my product stock centrally (ie. still be able to manage the product globally). How can this be achieved in Magento?
Update: after digging around some more, asking in IRC channels, posting on forums, and searching the heck out of Google and the Magento Connect extension repository, I am starting to realise this is one of Magento's short comings. I am going to develop my own solution for this. Please leave a message here if you are interested in the same functionality, if there is enough response I will see if I can make it available for others.
Unfortunately there is no good answer to this question. Product texts are typically entered on the store view level, like you already discovered. Having multiple store views in the same language (but under different websites) will create a burden and overhead to configure.
If this was my store, I would pick one of these routes:
Load data from an external source, where product data is already nicely managed. Managing product data in Magento can be a pain.
Or, if you MUST do it in Magento, create a custom module to update all the relevant fields across multiple websites. You could create an event listener "on product save", that updates all texts for store views with the same language.
or, you can override the product resource model, so product names, descriptions and some other texts are loaded differently from the database (but this would definately be the most complicated route).
In App/Locale/ Directory this is Global locale directory you can read it in all your websites managed from one back-end !
And you can set the local directory for each storeview from
system->configuration->design->Translations
so basically you can use the same locale for different themes as long as you maintain the files updated with all the variables !
I was running 9 websites with different store views from one backend i never had issues with translations !