To be more extensible on the template level, it would be good to have something like “extends” and “block”.
The Erlang CMS Zotonic is using erlydtl, which have the extends and block tags.
Zotonic Template Inheritance
We are using Shopware (PHP-Ecommerce System) and it works really nice with template inheritance.
Shopware Template Inheritance
I have worked in the begin of my career as a freelancer with the Prestashop ecommerce platform, and I used to do a lot of work for a top 10 store in my country, and when they introduced checkout as guest, they increased a lot the sales figures, for the complete surprise of the owner, not mine ;).
So my recommendation is to make it easy as possible for people to buy without the need to login, because after the first purchase you can get them to transform the guest account in a real account with a good discount voucher or any other kind of promotion.
Keep coming back to this topic from time to time because I still think Elixir would be a good base for Ecommerce.
For theme development you would need something like blocks that the theme developer can extend.
How could something like that be approached or is there possibly a more “functional” solution?
In Shopware you have really hundreds of blocks that you can specifically overwrite in your own theme.
Are there possibilities in Phoenix 1.6 with heex Template’s?
Hi everyone, sorry to re-kindle an old thread, but, almost 5 years later, I managed to update my article series on writing your own E-Commerce:
https://medium.com/@ideatocode/a-gentle-introduction-to-elixir-phoenix-part-4-53f84ef441ce
As for the dynamic theme selection, I managed to make something you can just pass a folder name at build time for the application to pick up. The other alternative was using Shopify style Liquid templates, which Phoenix/Elixir has very good (100%) support for.
Hope you find this useful!
Cheers.