I've search for many hours now on the internet,
I'm developing Prestashop website for clients, and do you think I should use a Theme builder like Prestabuilder, a theme with a builder like Warehouse & elementor or a pre-made theme that i will custom through code. What's the better for performance, page speed ?
How do you feel about that ? Do you always develop from scratch for client or just install a theme ?
Thanks for your feedback.
No need to reinvent the hot water...
Start with a premium theme e.g. Warehouse which has about 15 different layouts you can choose from each of them can be further changed if you want.
For the price you get clean responsiveness, a bunch of very useful modules (only the megamenu if bought separately costs more than half the theme's price).
It has the famed Elementor page builder and it shortens the development tine 10x.
Related
Well, Our company has bought shopify theme and was happily using it. now we like make changes to this theme, mostly cosmetic changes, like changing card colors add some background images, then some layout change.
My question is/are:
1) Can we use bootstrap with existing theme?
2) Does making change to css of existing theme get replace if there is theme update, like WordPress?
3) How can we set it up so we can develop new design locally but our store stays live with old design until we're done developing new one?
Can we use bootstrap with existing theme?
ANS: Yes you can use bootstrap in your theme. You just need to include the bootstrap in your new templates and you are ready to go.
Does making change to css of existing theme get replace if there is theme update, like WordPress?
ANS: Suppose you'd added some CSS or custom code in your theme then new update will not replace your code. What will happen is you need to add the updates code manually in your theme. For reference you can read this article Updating themes.
How can we set it up so we can develop new design locally but our store stays live with old design until we're done developing new one?
ANS: You can use theme kit for local development. To stay live with old theme, you just need to make copy of the theme and used its ID in your theme kit.
When you start learning theme Kit then you will know what is theme ID.
Hope this information will help you.
Best of luck.
I am new to working with a CMS-platform and building an ecommerce website so please bear with me if my questions aren't spot on..
While I understand the concept behind a CMS-platform, I am trying to understand how I can build a custom website using the Liquid Theme Engine and VC. I have the platform and storefront both up and running locally (the electronics example store), and have even played around with extending a model and generating the new API endpoints for it(adding a wishlist type to the shopping cart) - this part is cool, I understand this is how the data is accessed.
However Liquid is new to me and I have a little understanding of how Angular works but not in a platform framework like VC, and Google searches are diluted with Shopify documentation which doesn't help me understand how a Liquid Theme fits into VC. If I spend the time to understand Liquid more, is my end goal to build a website theme in Liquid, and then reference that in the platform as the websites theme?
Are there any resources out there, besides what is listed on the VC website that could help connect the dots for me? (I think I've tried all the documents on the VC site and there are a lot of missing gaps)
Thanks
What the questions exactly you have? We have a large readme file for default theme. Also, here is a link to our docs about theme development. This topics describe theme structure, bundling & minification, localization and liquid language reference. Here is also a little explanation how theme work:
In Storefront, you have Controllers, which return View
ASP.NET view is template in Shopify terms. So LiquidThemeEngine try find this view in templates folder
Template may include snippets from snippets folder
Template have layout (usually header, body & footer) from layout folder (theme.liquid is default layout)
Templates and snippets may include angular components & controllers from assets/js folder and other static files (like images required by theme design) in root of assets or subfolder.
Now that Rally has changed the default UI for their ALM product, I have noticed that the UI components in my apps don't fit the same styling characteristics as the default UI elements. I think it would look a lot cleaner if I could use Ext's "Neptune" theme: http://docs.sencha.com/extjs/4.2.2/extjs-build/examples/build/KitchenSink/ext-theme-neptune/#basic-panels
Is there a way I can use this theme by default? If it is hosted anywhere within Rally, I think it would be as easy as including the CSS file in the App.html, but I could be wrong.
2.0rc1 is built on Ext 4.1.1a, so I'm not sure if the neptune theme is included or not. You'll be happy to know that 2.0rc2 is hot off the presses though, and should incorporate most of the new look and feel.
https://rally1.rallydev.com/apps/2.0rc2/sdk.js
https://help.rallydev.com/apps/2.0rc2/doc/
On my FBpage I wish to add custom tabs, within these tabs/iframes I want to external link my website (html/css, hosted on One.com, no SSL) so to achieve a fancy design, kind of like these:
http://bit.ly/YX1Vpr
http://on.fb.me/14NITT5
Tried the app "Static HTML" and added three tabs (Info, Contact, Biography) and I found two interesting options:
1) "Static HTML
A simple HTML editor allowing you to create static HTML content"
2) "Website
Use a page from your website. Includes resizing functionality."
Tried option 2 and linked an external page hosted on One.com, but it doesn’t seem to work on tablets/phones.
BOTTOM QUESTION: Any way to get around the SSLrestriction, ie by apps such as Static HTML, Woobox etc - or do I just need an SSL either way?
You cannot have a custom layout on Facebook pages OR profiles. You can add custom tabs via adding applications to your facebook page. Below are a few good pre packaged Facebook application providers. The list is ordered by perceived quality vs price (some are free, some are paid, and some allow you to white label your application after paying X dollars per month). Note that this ordering is completely subjective to my experience.
http://www.wildfireapp.com/plans (specific for promotions)
http://www.votigo.com/corp/features-and-pricing.php (specific for promotions)
http://www.shortstackapp.com/ (white label $30 and up)
https://www.socialappshq.com/home/pricing (white label $99 and up)
http://northsocial.com/pricing/ (SRM, white label $79 and up, also pricey)
http://www.agorapulse.com/pricing/ (white label $145 and up)
http://www.pagemodo.com/pricing (white label $30 and up)
http://thrusocial.com/index/subscribe (white label $20 and up)
http://www.tabfusion.com/pricing.php
http://www.faceitpages.com/pricing.php (white label $125 and up)
http://www.tabsite.com/pricing.php
Besides the above, you CAN develop Facebook applications and host them on your OWN server. This is a much more complicated setup, and I recommend you start with one of the options above. If you decide to use this method you will need to purchase an SSL certificate for the domain under which you are hosting your FB app, EVEN if your app is only static content. Find a suitable SSL sert provider via a simple search.
For plone 4.2.5 is there a non-complicated way to set up theme switching between desktop/mobile versions based on visitors screen size?
Something like "if less than 640x480 then" serve the mobile version ?
Talking about 2 non-Diazo themes for instance?
What is ++skin++ for skin switching, may it work?
I am quite new to plone and not really a programmer so a "sane" solution would be really appreciated !
Take a look in portal_css (via the Zope Management Interface) and search for "mobile." In the ""CSS Media" field, you'll find:
handheld, screen and (max-device-width: 480px)
This sets up a media query that causes browsers to use the mobile.css stylesheet if they know (admit) they are a handheld device or if they have a screen width of 480px or less. This is all done through completely standard CSS, and you may use the same principles to achieve completely different page designs for different screen widths. There are several great books on responsive design ("responsive" is the magic word). You may customize this stylesheet, or add your own media query style sheets.
You can also see a thorough and popular use of media queries and responsive design in "Twitter Bootstrap," which provides all sorts of class selectors that you may use to change designs at various screen widths. A bootstrap example is included with the newer version of plone.app.theming that is included with Plone 4.3.
Note, if you want design to change when you reduce a window size (not just the screen size), use "max-width" rather than "max-device-width."
I don't think so. However, you should look into responsive design and media queries. I suspect you can achieve what you want using standards compliant CSS in a single theme.
http://plone.org/products/collective.themeswitcher/
This is an alternative implementation you can use. From the description:
This addon has been designed to easily support new switcher. At the moment the only switcher that is implemented is the "mobile switcher" based on user agent from http://detectmobilebrowsers.com/ (python version).