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.
Related
Creating Modified Blog Entries
I am new to React, and very much to Docusaurus, however, I've managed to get a decent looking DS site going. I am trying to capture some simple snippets to as "blog entries", just small factual snippets, etc. simple project summaries. I’ve hit the limit of the Docusaurus.config options and not sure how to expand the out of box components.
How do I begin to alter and edit Docusaurus to change the Blog page to be like "Cards" in component-speak? Ive seen some example in Infima, but not sure how to bridge that gap?
How can I easily replicate the Announcement Bar to also be at the bottom, like a Banner?
Thank You!
One possible arena for you to use is Bootstrap — specifically React-Bootstrap. They have a card component you could use where you link individual blog entries to that card. If you're comfortable with JavaScript, there's probably an automation you can build there, but hand-coded text is somewhat part and parcel with static-site generators.
If you want a different solution with the CSS code in your src file outright, CSSCodeLab has a React Card layout entry with an attached source code file. Some hand-coded text required, and not automatically integrated with a separate blog setup, but YMMV.
Otherwise Docusaurus' Showcase page does provide the card formatting. The source code for the page (coded at index.tsx) as well as the components are available.
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.
I've enabled stencil themes for my store, and am trying to use "Cornerstone" as my theme. However, the whole reason for opting in and trying out new stencil themes is their built in support for multiple languages. I need my store to at least be available in Swedish, and if possible, English as well.
I've followed the documentation adding a "sv.json" file to the langs folder, and uploaded the modified theme to my store and applied it. No changes. I've ensured my browser is setting the "Accept-Language" header to "sv".
https://stencil.bigcommerce.com/docs/the-schema
I've also tried modifying the default en.json file, but I still can't see any changes in my store...and that seems a bit strange to me?
What am I missing, is this feature not really implemented yet, or am I screwing something up with the "upload zipped theme to store admin and apply"?
https://support.bigcommerce.com/articles/Public/Custom-Theme-Upload
Any pointers are very appreciated!
I am looking for a particular div in the Shopify Liquid files of a large-ish site I am new to and that I did not build. However, I have to check the files one by one to find if the div is there, which is unefficient. The PHPStorm editor has the ctrl+shift+F option to search the file arborescence for a specific string in any file. Does Shopify have an equivalent, and what is it?
Not to be confused with:
Adding a search bar on a Shopify site
Searching Shopify store admin (I need to look at the Liquid code, not the store)
Tried already:
Googled 'shopify equivalent of phpstorm ctrl+shift+F'
Googled 'shopify keyboard shortcuts'
Googled 'shopify find in path'
Googled 'shopify search code'
Found no relevant result.
I'm afraid I have never seen such feature on the Shopify Editor. What I usually do, however, if you're not working with the theme locally already is:
Export the theme via Download Theme File
Download the .zip and extract it.
Open it with your favourite Editor (I personally use Sublime)
Use Find in Folder or your text-editor equivalent to search for the string on the whole theme.
Sadly, there's no better workflow as of now. You should consider however, setting up your theme locally so you can take advantage of version control and a more organized workflow that could help maintenance and new updates on that site.
2 options:
1) download locally (many devs work locally now using theme kit or another tool)
unzip theme and do a search either with text editor or with file manager
2) you can also use screaming frog to scan sites in detail - may be more useful though in cases where the div is not actually technically in theme but say in a metafield or added by an app.
I fell into a project where my task was develop some widgets in Sitefinity 4.4. I've found a lot of documentation on how to create the widgets using the Site Manager and all that has gone really well.
Now, I have the widgets set up in a test environment and working well with some test pages. I'm trying to figure out how to deploy the widgets to the production server without re-doing all the work there. I just want to move the widgets over - I don't need or want the pages. I have gone through a lot of the Telerik documentation, but have been unable to find anything about deploying like this. Has anyone done this before?
Thanks!
did you develop these widgets as compiled controls (dll) or simple user controls (.ascx)?
The process is mostly the same for either. the dll goes in the bin folder whereas a user control gets uploaded to the website folder somewhere. then you simply register the widget in the toolbox.
here is the documentation for how this is done: http://www.sitefinity.com/documentation/documentationarticles/adding-controls-to-the-toolbox
The only difference for a compiled dll widget is to use the fully qualified name for the ControlType instead of the path to the user control.
After registering the widget it should be available to drop onto any page.
Hope this is helpful!