Hotfix/block styles template

[khleomix]

Closes

Hotfix

Link to test

Test Locally

Description

• Block Template Update: Updated block templates for better consistency and structure.
• Desktop Menu Cleanup: Removed unnecessary code and streamlined the desktop menu functionality for improved performance.
• Responsive Mixin Update: Enhanced responsive mixin with range functionality for better control across different screen sizes.
• Menu Style and Header Markup Fixes: Fixed issues with the styling and markup of the navigation menu and header, ensuring consistency across different devices.
• SVG Markup Support for Logo: Added support for SVG logos, along with additional improvements to the header styles.
• Mobile Navigation Styles Update: Improved the mobile navigation styles for a more user-friendly experience.
• Icon Placement and Padding Fixes: Addressed minor alignment and spacing issues for icons and overall layout refinements.

Related Tickets & Documents

Mobile &

Core-Widgets-Blocks-.-WDSBT.mp4

Desktop Screenshots/Recordings

Added to documentation?

• 📜 README.md
• 📓 Confluence
• 🙅 No documentation needed

Added tests?

• 👍 Yes
• 🙅 No, because they aren't needed
• 🙋 No, because I need help

Testing Instructions

---

Reviewer's Testing Checklist

As a reviewer, please verify that the relevant testing criteria are fulfilled and confirmed before approving this Pull Request.

• Visual Regression Testing: Ensure that existing functionality is not negatively impacted by the changes.
• Cross-Browser Compatibility: Test on major browsers (Chrome, Firefox, Safari) to ensure compatibility.
• Mobile Responsiveness: Confirm that the changes are responsive and functional on various mobile devices.
• Theme Compatibility: Ensure that the changes do not adversely affect the site's theme and styling.
• Linting: Check that the code passes all linting checks (PHPCS, ESLint, SassLint). Check if PR passes code quality check.
• Accessibility Testing: Validate that the changes comply with accessibility standards. Run npm run a11y.
• Security Best Practices: Ensure that the code follows WordPress security best practices. Check if PR passes security check.
• Documentation: Ensure that any new features or changes are appropriately documented in the README.md or Confluence.
• Post-Deployment Tasks: Check if there are any tasks that need to be performed after deployment.

[optional] Additional Reviewer Notes or Considerations?

[thatmitchcanter]

Looking great. Thanks, and approved!

[lswilson]

This all looks really good @khleomix - good to go!