My (100 and) 2 cents

chadlly2003:

balihr:

Honestly, this design feels like a step back when compared to my proposed design (https://zencart.zenexpert.com). The font sizes are exaggerated, and merging the section backgrounds and using non-contrasting colors makes the whole thing lose its impact. Those "Tailor-Made" boxes? That style was popular years ago and it feels outdated now.

Balihr,

Why not use both sites? You could take the header’s HTML and CSS from your design and integrate it into the current site. That might resolve the header issues while allowing you to keep the existing site intact. It could be a simpler solution.

I am here if you guys need help ... just pm me

I think you're confusing me with someone who has any saying in how the site looks. 😄 Keep in mind I'm a user just like you, with the same access/privileges that you have. It's not my call and I can't make any changes, I can only discuss them here in the forums and give my opinion.

But, the PM that you sent me - I respect your choice, although I think that should be posted publicly in the forums. The more opinions we have, and the more people agree with one thing, the more chance we have of getting it adopted by the team.

Once again, I want to thank everyone for their feedback, especially Leo(@balihr) who created the original vision for the new site.

I know that the current site design has drifted from that and initially those changes were purely my choice, although somewhat advised by wcag/lighthouse etc.

We keep iterating the design based on your feedback, so keep it coming.

However I am minded to close this thread, not to suppress your feedback, but because there are just too many different "threads" to the advice being offered which makes it painful to track from my point of view.

My suggestion is that I create a bunch of new threads that track the individual complaints presented here, logos/font sizes/colour palette, static page design etc
So we can focus those discussions, not silence them.

wilt:

Once again, I want to thank everyone for their feedback, especially Leo(@balihr) who created the original vision for the new site.

I know that the current site design has drifted from that and initially those changes were purely my choice, although somewhat advised by wcag/lighthouse etc.

We keep iterating the design based on your feedback, so keep it coming.

However I am minded to close this thread, not to suppress your feedback, but because there are just too many different "threads" to the advice being offered which makes it painful to track from my point of view.

My suggestion is that I create a bunch of new threads that track the individual complaints presented here, logos/font sizes/colour palette, static page design etc
So we can focus those discussions, not silence them.

Wilt the way this site is built this is not that hard

wilt:

Once again, I want to thank everyone for their feedback, especially Leo(@balihr) who created the original vision for the new site.

I know that the current site design has drifted from that and initially those changes were purely my choice, although somewhat advised by wcag/lighthouse etc.

We keep iterating the design based on your feedback, so keep it coming.

However I am minded to close this thread, not to suppress your feedback, but because there are just too many different "threads" to the advice being offered which makes it painful to track from my point of view.

My suggestion is that I create a bunch of new threads that track the individual complaints presented here, logos/font sizes/colour palette, static page design etc
So we can focus those discussions, not silence them.

Wilt,

If you could send me the source code for just the header in a PM, I can work on getting everything looking just right and have it ready for you to simply copy and paste.

It shouldn't take too long, since the header itself isn't overly complicated. For a site like this, getting the color scheme right, making sure everything looks clean and professional, and ensuring it meets accessibility standards should be fairly straightforward. I'm confident I can have the header completed within a very short time frame. That's also including learning the way tailwind utilities are set up.

I don’t want to step on anyone’s toes, but this is really my area of expertise, and it’s something I specialize in.

Hey, just an FYI — when I updated my plugin template, I had to remove the spacing for it to be accepted. This has never happened in the past.

One final note — this is just a personal pet peeve of mine, but can we please remove the blurriness from the logos? It’s such a simple fix, and having them look crisp and clear would make a noticeable difference.

chadlly2003:

Hey, just an FYI — when I updated my plugin template, I had to remove the spacing for it to be accepted. This has never happened in the past.

One final note — this is just a personal pet peeve of mine, but can we please remove the blurriness from the logos? It’s such a simple fix, and having them look crisp and clear would make a noticeable difference.

This is the error i get when i try and upload my template plugin. I changed everything t to be correct but getting same error

The uploaded ZIP archive contains a path with a space ("zencart_responsive_classic_redesign-main/zencart_responsive_classic_redesign-main/CSS_For_One_Page Checkout_Optional/") — rename it to use underscores or hyphens and re-upload

@chadlly2003, the upload check only reports the first path with a space that it finds, so fixing one name just moves the error to the next one. In the name it quoted, CSS_For_One_Page Checkout_Optional, there's still a space between Page and Checkout.

Your GitHub repo still has three top-level names with spaces:

CSS For One-Page Checkout - Optional
Image Gallery - Optional
demo_images - optional.zip

If you rename them in the repo itself (for example CSS_For_One_Page_Checkout_Optional, Image_Gallery_Optional and demo_images_optional.zip), the Library upload and GitHub's "Download ZIP" are both fixed at once. The README and readme.html refer to those names, so they'll need the same change.

To catch any you've missed before zipping, run this in PowerShell from the extracted folder: Get-ChildItem -Recurse | Where-Object Name -like '* *'. If it prints nothing, the zip will pass this check.

The path in your error also shows the folder twice (zencart_responsive_classic_redesign-main/zencart_responsive_classic_redesign-main/). That happens when GitHub's zip is extracted and the outer folder is zipped again. It's not what the error is about, but zipping the inner folder gives a cleaner package.