Refinement of Magento 2 layout: CSS, RTL, mobile, minicart

Hello. I can assist with specific frontend adjustments: CSS/LESS, mobile, RTL, minicart hit-area, and layout shift. A format without local Magento is acceptable: diagnostics through DevTools, edits in the theme's source files, followed by a clear diff/commit for your build.

I have worked with RTL at the level of dir/direction/logical properties, overflows, numbers/prices/SKUs in LTR within RTL. I usually check CLS through Performance/Layout Shift Regions, image sizes, fonts, lazy/render timing, and CSS that changes geometry after loading. I can start with specific URLs and a list of bugs.

Show original

Translate

Hello.

I am ready to join the task of fine-tuning the frontend part of Magento 2.

From the description, I see that the task is not just about "simply fixing CSS," but about careful diagnosis of frontend defects: responsive design, RTL, minicart, hit-area, layout shift/CLS, and edits in the theme's source code with a clear diff/commit. This format works for me.

From my experience: I have worked with e-commerce projects and frontend enhancements for existing websites: HTML/CSS/LESS, responsive layout, Flexbox/Grid, fixing visual bugs, issues with margins, overflows, clickable areas, z-index, and element behavior on mobile/desktop. I am ready to work with Magento 2 specifically within the frontend part of the theme: CSS/LESS, layout/frontend templates if necessary, without interfering with the backend.

I am familiar with RTL layout: I understand the specifics of dir="rtl", direction, unicode-bidi, mirroring margins/positioning, overflow of badges/counters, as well as cases where certain elements are better left in ltr, such as numbers, prices, SKUs, emails.
…
I usually look for the cause of layout shift / CLS through Chrome DevTools: Performance, Lighthouse, Network, slow 3G/CPU throttling, checking image sizes, late-loading CSS, webfonts, lazy-load, placeholders, gallery/slider initialization, and the absence of width/height or aspect-ratio. After that, I fix not the symptom, but the source of the shift.

I can work without a local deployment of Magento if I have access to the necessary theme source files and the ability to check behavior through DevTools on a live/staging URL. I can provide edits in the form of a clear diff/commit. The static build and deployment, as you indicated, will be handled by your side — that’s fine.

Regarding cost: I would initially estimate such a task in the range of 6–12 hours, but I will provide a more accurate estimate after reviewing the URL and the list of specific defects. If it turns out that the minicart is related not only to CSS/hit-area but also to Magento JS/customer-data/cache, I will specify this separately before making any edits.

I can start in the near future. I suggest we first have a brief call to review the problematic URLs, document the list of bugs, and then prioritize them: minicart, RTL, mobile/desktop visual defects, followed by CLS/layout shift.

Show original

Translate

Hello How are you today?

Yes I have worked with Magento 2 frontend tasks and similar e commerce projects including custom themes responsive fixes minicart behavior and checkout related UI issues

I also have experience with RTL layouts including direction handling logical CSS properties overflow issues mirrored positioning and mixed LTR RTL elements

For CLS and layout shift issues I usually start with Chrome DevTools Performance and Rendering tools to identify which elements shift during initial render
After that I check image sizing async fonts delayed CSS dynamic blocks lazy loading and JS that changes dimensions after hydration

… For unstable minicart behavior I normally inspect event listeners z index overlapping elements pointer areas and dynamic DOM updates because in Magento these issues are often connected to theme overrides or deferred scripts

Working without local Magento deployment is not a problem
If DevTools access and theme source files are available I can diagnose and prepare precise LESS or CSS fixes with clean diffs or commits

Thank you

Good day! 1. Certified Magento front-end developer with 9 years of experience. 2. Yes, I have experience with RTL. 3. How do you usually look for the cause of layout shift / CLS? – inspector and experience. 4. Styles and even scripts can be edited without deployment, just in the admin panel using the code addition feature in the theme config. 5. The rate is negotiable. 6. Available for projects, ready to start.

Show original

Translate

I worked on strefaluster.pl — an e-commerce store on Shopify, where I implemented a responsive frontend, fixed cart behavior at different resolutions, and eliminated layout shift on product pages.

CSS/LESS debugging without a local environment is my standard — I diagnose through DevTools (Performance → Layout Shifts, Event Listeners on minicart, Network for FOUC), write pinpoint fixes in the theme sources, and provide a clear diff/commit. I worked with RTL at ou-uv.com — a multilingual CMS with text direction: dir=rtl, margin-inline-start instead of margin-left, unicode-bidi, positioning flex elements upon direction change. I look for CLS through Chrome Performance: I check which element changes the bounding box on the first render — most often an image without width/height or font swap before FOUT. I haven't worked directly with Magento 2 as a fullstack, but the Magento 2 theme is LESS + Require.js + XML layout — pinpoint CSS/LESS fixes are identical to any other e-commerce project. Working through DevTools and theme sources without a local environment — this format suits me.

What I will do:
- Diagnosis and repair of layout defects (desktop + mobile)
- RTL fixes: text direction, margins/paddings, overflow of counters and buttons
- Fix minicart: analysis of Event Listeners, repair of the shifted click area
- Repair CLS on the product card (image shifting on first load)
… - Fixes in CSS/LESS sources of the theme + clear diff/commit ready for deployment by your site

--- OPTIONS ---

A) Standard: 200 EUR (7 days) — all points from the brief, diff/commit ready for deploy
B) Extended: 320 EUR (7 days) — additionally, an audit of other visible CSS/UX defects on the site and optimization of CLS score for key subpages — best scope/price ratio
C) Premium: 420 EUR (7 days) — full frontend audit, Lighthouse report, proposals for further performance optimizations

Execution time: 7 days. I need a set of URLs with defects and access to the theme sources.

- strefaluster.pl — Shopify e-commerce, custom CSS, responsiveness, cart UX
- poseidon.codezerogroup.com — complex web application, React/Next.js, enterprise systems
- ou-uv.com — multilingual CMS Flask/Python, RTL, API integration

5 years in frontend development — from landing pages to complex e-commerce systems.

Provide the URL of the site and a list of defects — I will start with a DevTools audit and return with a repair plan before starting the transaction.

Show original

Translate

Hello! I will be happy to help with the edits on your project. I have experience working with Magento, although I worked with it a long time ago, but I specialize in e-commerce (Opencart, Woocommerce, MODX, custom solutions on frameworks). I have experience with all of the above, it's not a problem, the main thing is that for convenience I will need the source files for css and js. I indicated the minimum cost, I will be able to give an estimate when I see the website. I think I can handle it quickly, feel free to write.

Show original

Translate

Good day!
I am responding to your list:

1. Experience with Magento 2 / e-commerce Magento 2 as such - basic experience at the frontend level: theme structure, LESS compilation, understanding how the theme works and where to find the necessary files. More experience with WooCommerce and custom e-commerce solutions - catalogs, product cards, carts.

2. RTL layout
Yes, I have experience: dir=rtl, logical properties (margin-inline-start instead of margin-left), unicode-bidi, checking the positioning of flex elements when changing direction.

3. How I search for the cause of layout shift / CLS
… Chrome DevTools → Performance tab → I look for Layout Shift records, see which element is shifting and at what moment.
Most common causes: images without specified width/height, fonts that load later (FOUC), dynamically inserted content on top.
For minicart hit-area - Event Listeners in DevTools to see which element the click is actually attached to.

4. Working without local Magento
Yes, this format suits me.
DevTools + access to the theme source files - enough for precise CSS/LESS edits.
Diff or commit - no problem.

5. Cost
From 50EUR for the entire list of tasks - depending on the actual volume after reviewing specific URLs and sources.
I am ready to discuss a fixed price after a short call.

6. Start
I can start tomorrow after a short call and receiving access.

—
I create websites and web applications that deliver results · Denys Ivanchенко

Show original

Translate

Hello.
I have over 6 years of experience in frontend development: HTML, CSS/LESS/SCSS, responsive layout, Flexbox/Grid, working with existing e-commerce projects, and pinpointing UI/UX defects without "breaking" the structure.
I have worked with Magento 2 not as a fullstack developer, but I have experience with similar e-commerce projects where I needed to make frontend adjustments to an existing theme, work with DevTools, analyze the DOM, CSS cascade, the behavior of interactive elements, and provide a neat diff/commit.
I also participated in the development of the project:
https://takamolholding.com/
There, I gained experience working with RTL direction, responsiveness, proper spacing, positioning of elements, and interface behavior for the Arabic version.
I understand the nuances of RTL and know practical implementation and fixes.
I usually look for layout shift / CLS issues through Chrome DevTools: Performance.
I can work without local Magento deployment: through DevTools + access to the necessary LESS/CSS/template files of the theme. I can diagnose the problem in the browser, find the root cause, and prepare pinpoint fixes for your build and deployment.
… I can approximately start after a brief discussion and review of the URL/list of defects. Regarding pricing — it depends on the number of bugs, but for a one-time task, I can offer hourly payment or a fixed rate after assessing the scope.

Show original

Translate

Hello Vladimir Solovev! I will be glad to cooperate with you.
Successful experience in developing web applications on Magento2 and SEO optimization.
The cost and timeline are indicated preliminarily, precisely after familiarization with the admin panel and website templates.
Portfolio: Freelancehunt

Show original

Translate