Phoenix but IS Phoenix

Cosmetic look of components or your whole site
User avatar
Kofod95
Senior Contributor
Posts: 766
Joined: Sat Feb 06, 2021 7:38 pm
Phoenix Version: 1.0.8.21
Has thanked: 103 times
Been thanked: 188 times

Re: Phoenix but IS Phoenix

Post by Kofod95 »

Something with the layout on mobile here.
Screenshot_20260324-201215.Chrome.png
//Daniel
You do not have the required permissions to view the files attached to this post.



Join The Code Co-op to get access to your library in the Code Co-op Forum
PiLLaO
Contributor
Posts: 131
Joined: Thu Nov 05, 2020 9:28 pm
Phoenix Version: v1.1.0.6
Has thanked: 65 times
Been thanked: 17 times

Re: Phoenix but IS Phoenix

Post by PiLLaO »

In my opinion, on desktop, slider is too big, on my 23" monitor at 1920x1080 only see the slider, products are "hidden" until make scroll down.

on mobile slider looks ok, but hamburguer button, logo and cart are not inline, looks like:

button
logo
cart

azpro
Contributor
Posts: 192
Joined: Fri Nov 06, 2020 8:25 am
Phoenix Version: v1.1.0.7
Has thanked: 38 times
Been thanked: 45 times

Re: Phoenix but IS Phoenix

Post by azpro »

burt wrote: ↑Tue Mar 24, 2026 5:48 pm OK, maybe asking tolook at whole site is too much? TYVM to those who did take time, much appreciated. You helped me make decisions.

Let's instead concentrate solely on Product Page, anyone have thoughts, ideas, feedback. Be as critical as ya like.

https://phoenixcart.org/demo/product_in ... ducts_id=4
The breadcrumb might need some modernization IMHO .... and closing the off-canvas by clicking outside the menu might be a good idea

User avatar
burt
Core Team
Posts: 4736
Joined: Tue Oct 29, 2019 9:37 am
Phoenix Version: v1.1.0.8
Has thanked: 279 times
Been thanked: 467 times

Re: Phoenix but IS Phoenix

Post by burt »

TY guys, appreciated. I have made some more changes based on last 3 posts which, I think, looks alright ?

PiLLaO
Contributor
Posts: 131
Joined: Thu Nov 05, 2020 9:28 pm
Phoenix Version: v1.1.0.6
Has thanked: 65 times
Been thanked: 17 times

Re: Phoenix but IS Phoenix

Post by PiLLaO »

On mobile, now looks great

User avatar
burt
Core Team
Posts: 4736
Joined: Tue Oct 29, 2019 9:37 am
Phoenix Version: v1.1.0.8
Has thanked: 279 times
Been thanked: 467 times

Re: Phoenix but IS Phoenix

Post by burt »

Footer Area, where the Card Logo's are.
https://phoenixcart.org/demo/conditions.php

Better as grey tones (as seen above), or better with a few more colours ?

EG make the Paypal Logo blue. Something like;

lkjh-f2.jpg
You do not have the required permissions to view the files attached to this post.
I am not here to build for you.
I am here to build with you. Let's help each other.

User avatar
tessthepup
Certified Developer
Posts: 416
Joined: Mon Mar 01, 2021 5:55 pm
Phoenix Version:
Has thanked: 64 times
Been thanked: 66 times

Re: Phoenix but IS Phoenix

Post by tessthepup »

burt wrote: ↑Sat Apr 04, 2026 11:27 am Footer Area, where the Card Logo's are.
https://phoenixcart.org/demo/conditions.php

Better as grey tones (as seen above), or better with a few more colours ?

EG make the Paypal Logo blue. Something like;


lkjh-f2.jpg
@burt It is definately starting to take shape :+1:

My personal choice would be to have the footer logos as there respective colours as it is another thing the end user does not have to change

Dan Cole
Senior Contributor
Posts: 548
Joined: Fri Oct 25, 2019 2:14 pm
Phoenix Version: 1.0.8.21
Has thanked: 77 times
Been thanked: 68 times

Re: Phoenix but IS Phoenix

Post by Dan Cole »

My personal choice would be to have the footer logos as there respective colours as it is another thing the end user does not have to change
I agree.

Dan

artfulweb
Contributor
Posts: 215
Joined: Thu Oct 29, 2020 12:34 pm
Phoenix Version: v1.1.0.6
Has thanked: 30 times
Been thanked: 14 times

Re: Phoenix but IS Phoenix

Post by artfulweb »

Hi and thanks for all this hard work.
As accessibility is now an obligation for websites please take note of the errors relating to the buttons as observed by Accessibility Insights run, as an example, on Ignus template which going forward will eliminate accessibility on some templates:

Automated checks Step 1 of 3
Automated checks can detect some common accessibility problems such as missing or invalid properties. But most accessibility problems can only be discovered through manual testing. The best way to evaluate web accessibility compliance is to complete an assessment.
Failed instances 3 failures were detected.
Failed instances
3
3 Failed
Visual helper

Resources for this rule
More information about button-name
WCAG 4.1.2
Path
.btn-secondary
Snippet
<button type="submit" class="btn btn-secondary btn-sm btn-search"><i class="fas fa-magnifying-glass fa-fw fa-xl" aria-hidden="true"></i></button>
How to fix
Fix ONE of the following:
Element does not have inner text that is visible to screen readers
aria-label attribute does not exist or is empty
aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
Element has no title attribute
Element does not have an implicit (wrapped) <label>
Element does not have an explicit <label>
Element's default semantics were not overridden with role="none" or role="presentation"

Highlight visible
Resources for this rule
More information about color-contrast
WCAG 1.4.3
Path
.cm-footer-text > a[rel="noopener"][target="_blank"]
Snippet
<a href="https://github.com/CE-PhoenixCart/PhoenixCart" target="_blank" rel="noopener">GitHub</a>
Related paths
.mt-2
How to fix
Fix the following:
Element has insufficient color contrast of 4.26 (foreground color: #0d6efd, background color: #f8f9fa, font size: 13.5pt (18px), font weight: normal). Expected contrast ratio of 4.5:1Element has insufficient color contrast of 4.26 (foreground color: #0d6efd, background color: #f8f9fa, font size: 13.5pt (18px), font weight: normal). Expected contrast ratio of 4.5:1
Use foreground color: #0c68f0 and the original background color: #f8f9fa to meet a contrast ratio of 4.68:1Use foreground color: #0c68f0 and the original background color: #f8f9fa to meet a contrast ratio of 4.68:1
Or use background color: #ffffff and the original foreground color: #0d6efd to meet a contrast ratio of 4.50:1.Or use background color: #ffffff and the original foreground color: #0d6efd to meet a contrast ratio of 4.50:1.

Highlight visible
Resources for this rule
More information about list
WCAG 1.3.1
Path
.navbar-nav:nth-child(1)
Snippet
<ul class="navbar-nav">
Related paths
form
How to fix
Fix the following:
List element has direct children that are not allowed: form



Join The Code Co-op to get access to your library in the Code Co-op Forum
Post Reply