Mike-E-angelo
commented
11 months ago I am completely in agreement here. I totally out-visioned myself with my direction from the outset.
Initially I planned a true publishing system. Think of it like an angelfire or GeoCities where you can create your own templates and publish products from those templates. Templates can have numerous media parts and the template organizes them and is used to display it to the user.
I gave it a shot but really this is v4 or v5 stuff. 😅 And really we need a team of people to develop this. It has also proven challenging from a performance viewpoint because the template system is way more complicated than it needs to be as well. We have dodged a few bullets here because it's really only in the issuance that we make the intensive queries.
For the Subscriptions story, I am going to get rid of definitions and make this way simpler as you suggest. I will then attempt to integrate the simpler workflow back into the existing Markets and better organize stuff.
BTW these screens are four years old now and were one of the very first things I developed 🤪
Creating a defintion of audio/video/text/etc is pretty counterintuitive. People will not read the manual and they would think that only images can be uploaded. In my opinion selecting the type of the attachment (content template) should be visible above the assign part. Also it is technical term "content template", it's more like "content type". (I do understand why it's a template on programming side, but from the user perspective it's not a template, it's just a type). Also simple mode should be forgotten and have one page, all the neccessary fields visible, and optional fields grouped under tabs or the current approach