Template Manager - Help, Ideas, Suggestions Needed

[burt]

Added Message for feedback when shopowner changes TPL.

tpl_add_message.png

[Omar_one]

• Feature Tags: like "Mobile First," "Dark Mode Support,".... etc

• Last Updated Date: Shop owners want to know if a template is actively maintained. Adding a "Last Updated" date next to the version number builds trust.

• Author Links: The creator's name should be a clickable link to their website or profile.

• use icons to show what the template includes:
  - CSS Only (Lightweight)
  - Includes Modules (Requires configuration)
  - Uses Hooks (Automatic layout changes)

• If someone hasn't downloaded any other templates yet, a "Find more templates at the phoenixcart Addons Library" link or button would be a great .

• The "Pre-Install" Modal: When a user clicks Install, instead of an immediate action, pop up a modal. This modal should parse the README or a specific instructions.html file included in the zip.

Or

• Instruction Icon: Add a small "Info" or "Document" icon next to the version number that allows the user to read the instructions .

[ArtcoInc]

@burt

(just thinking out loud )

1) Does/can a template add functionality (installing add-ons), or just change the overall look-and-feel of the entire shop?

I can see where adding an add-on might suggest/require a look-and-feel adjustment too.

2) Can multiple templates be installed on a shop? Perhaps one for the overall look-and-feel, and another for specific pages (perhaps as needed for an add-on?).

- OR -

perhaps ... a common framework (dare I say ... API?) be established so that any add-ons use the same look-and-feel framework, so that any template can/will apply to all additional add-ons?

(I have seen add-ons that use their own look-and-feel layout for their specific code)

(again, just thinking out loud)

M

[burt]

...

Some great ideas there to hopefully get other members interested!

The one about the button back to a Template Marketplace is already done, just haven't taken a screenshot.

[burt]

I can see where adding an add-on might suggest/require a look-and-feel adjustment too.

I guess it depends on the template maker. EG in Ignis template ( https://phoenixcart.org/demo/ ), there are a couple of new modules to install, and some core ones to uninstall. Mostly to get rid of that horizontal menu.

2) Can multiple templates be installed on a shop? Perhaps one for the overall look-and-feel, and another for specific pages (perhaps as needed for an add-on?).

I wouldn't entertain that idea in Core Code - too complicated.

perhaps ... a common framework (dare I say ... API?) be established so that any add-ons use the same look-and-feel framework, so that any template can/will apply to all additional add-ons?

Again, it rather depends on the template maker, and the addon maker.

Phoenix (the software) is agnostic, meaning TPL and addon makers can do as they please, and shopowners can do as they please. Sometimes all that will gel, other times not.

[burt]

Thanks for replying all - appreciated
Hopefully we get some more ideas and conversations from other interested parties.

[burt]

Does anyone else have comments, ideas, suggestions for the page, or what
each `template card` in the page might show.

Many thanks to all who have replied in the thread, so far, I really appreciate you taking the time.

[artfulweb]

Hi Burt, I love the idea... reminds me of WordPress where we can delve into free and paid templates which makes designing our website easier and is an essential reason many people go with Wordpress.

Many of us I imagine can not easily see what we could change to really modify the appearance of Phoenix cart. We would also need the designer to do updates as Phoenix updates. So definitely interests me.

[bonbec]

I understand how you feel.

I just want to address two points:

The average Phoenix user is probably:
* running a live store
* focused on selling products
* not actively thinking about themes/templates

* He uses the forum like a customer service. He comes to it ubiquitously when he has a problem or doesn't know how to do something.
Other thing : The number of views of a subject is skewed by scanning robots.

## Hidden danger
There's one danger nobody discusses explicitly.
### Template lock-in
Suppose a template:
* installs modules
* removes modules
* changes hooks
* alters layouts
Then switching templates becomes harder.

This is a thing I've already considered, and it worries me a bit because I experienced it myself as a moderator on the French-speaking Osc forum.

Some people were buying templates for the MS2 version from templatesmonster or similar sites. However, these templates seriously modified the code. When a user installed the purchased template from the existing site, nothing worked anymore. Hence the SOS messages on the forum. And the answer was always the same: "Contact the template provider." And the template provider's response: "Contact the creator of Osc." As a result, we lost users, or those who remained had to start all over again, having lost money.

In fact, only templates uploaded to the add-ons area should be able to be installed, not others. A key system would probably allow verification of the template's origin and prevent the installation of illegal templates.
Another security measure, but one that would take time: the template must be checked by the team before being validated on the addons website.

[burt]

v1.1.0.8 will introduce this in a limited way.
The new page will evolve over the next few versions as we learn what Template Creators want/need, and what Template Users want/need.

https://github.com/CE-PhoenixCart/Phoen ... 3681465dbe
and
https://github.com/CE-PhoenixCart/Phoen ... 09bc266407

TY to the few who got involved in this discussion, I really appreciate you all taking the time. Chapeau!