How exactly does the VirtoCommerce platform work for building a custom website?

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.