The Long description field is just a renamed default body field and the Specifications long text field is added at about 5:50 of this video. For that field, I had previously created the same field for another product type, so instead of creating a brand new field for the same thing I just reused the existing field. The important thing to know if you're trying to set up a similar product is just that these fields are "text (formatted, long)" fields so that they include the WYSIWYG editor.

Hi Kush, thanks for the support. Unfortunately we're not planning to new tutorial videos any time soon, but I think I can still help you out some. This video is the last in a 5 part series, so check out the other parts for more configuration setup. 1 - kzbin.info/www/bejne/naWppIOmjb1qrLs (product attributes) 2 - kzbin.info/www/bejne/eHa3oIdjrM6nock (rendered product attributes - i.e. colours) 3 - kzbin.info/www/bejne/pWi2dIWqqtV7bdE (product variations setup) 4 - kzbin.info/www/bejne/mYHLpZ9uicR2gNE (product type setup) For additional help, you can reference the demo site this is built on by logging in to commerceplus.acromedia.com/ using username and password 'demoadmin'. There's also a link in the footer to the codebase on GitHub where you can view the code for the theme (sass, js, templates, etc.). Finally, you can check out the official Drupal Commerce documentation at docs.drupalcommerce.org/commerce2/getting-started . It has a lot of good information plus additional ways to seek community support.

Hi there. Commerce for D8 is quite a bit different. Now, Product Types are the main entity (not a Content Type) and Product Variation Types are the purchasable variations added to the product. They're all managed within the separate top level Commerce menu system. We have a blog/video series that goes over this in detail. It might be a little bit dated now, but should still be accurate for the most part. Check it out here: blog.acromedia.com/drupal-commerce-2-how-to-set-up-product-attributes

Acro Media Got it, thanks! That’s sort of what I figured but wanted to make sure I wasn’t doing it wrong. For the most part that makes sense.

Hi! For each tab, the tab title is a plain text field and the content is a long text field. Then, in the product page template, we're printing out the fields using the tab system from the Bootstrap framework (getbootstrap.com/).

Hi Jhonatan, We don't have a specific video, but you can check out the templates and code base at github.com/AcroMedia/commerce-demo . You can even clone the repo and use the provided database to set up the demo site locally, then login and view configuration too. Hope this helps and thanks for watching!