 | Can local visual regression testing help your coding agent move faster and save you money? I took some time to explore how to set up playwright properly, which pitfalls to avoid, and the tradeoffs with common visual regression tools like Percy and Chromatic. Check it out and let me know what do you think! [link] [comments] |
Hi guys!
I'm a web dev enthusiast. And I was learning web dev initially from a yt course and from that, I learned html and css.
But later, I did some research and found that the odin project is a better learning resource for web dev. I started learning js from it and skimmed some initial portions as well.
Later, I realised that odin's teaching style and pace isn't suitable for me. It isn't that I don't like reading docs, I have no problem with that. But, Odin is too slow & long, and takes days to cover just one module. But, I wanted a thing which would teach me things fast but still, covering good depths. I only wanted to learn js as I realised that the full stack open course by University of Helsinki, is a better option than Odin.
According to what I've read - it's not only faster but covers good depth, is industry relevant and covers different frameworks as well. But, it requires js knowledge.
So after wasting some more days, I got to know about the Scrimba full stack path. So far, I completed only the js path from it which I did almost 2-2.5 hrs. I'm really enjoying their way of teaching and understanding the concepts being taught there. Gonna make some projects and things on my own to see if I actually got the things and I'm not just stuck in tutorial hell.
So, I was thinking of doing the Scrimba path for completing js and some other relevant/imp part. Later, I'm gonna move to the full stack open course - starting React and so on then.
So, is my decision right?
Actually, I have access to the Scrimba pro subscription (due to github student developer pack) for 1 month and thought of utilizing the pack by getting the 30 days free trial of scrimba pro.
If you have any tips, correction or better approaches etc. Please do lmk.
Thank you!
 | Hi everyone, long time ago i was messing around with this effect done over glassmorphism, which gives the cursor some luminescence that reflects on the html elements, i am always obsessed on making stuff with pure css, so i did just that :D well except for the mouse tracking but that just puts the x/y of the mouse as a css variable, the rest of the painting is just CSS you can verify yourself go on to https://nabous.dev/lab/lumenmorph/ and mess around, im open for contributions and forking if you are interested as well [link] [comments] |
Hey r/Frontend,
Over the weekend, I fell down a surprisingly deep Unicode rabbit hole while building a client-side text styler (creating Fraktur, double-struck, circled, and aesthetic bio glyphs) with zero external libraries.
I wanted to share two specific technical traps I ran into and how to solve them properly on the front end:
When engineers try to convert standard ASCII characters (e.g. A-Z) into styled Unicode variants like Double-Struck (𝔸, 𝔹, ℂ) or Fraktur (𝔄, 𝔅, ℭ), the naive instinct is mathematical offset calculation: js // ❌ Naive implementation: breaks on specific glyphs const targetCodePoint = 0x1D538 + (char.charCodeAt(0) - 65); return String.fromCodePoint(targetCodePoint); Why this breaks: Unicode's Mathematical Alphanumeric Symbols block (U+1D400..U+1D7FF) has several historical "holes". Characters like Double-Struck C (ℂ, U+2102), H (ℍ, U+210D), N (ℕ, U+2115), P (ℙ, U+2119), Q (ℚ, U+211A), R (ℝ, U+211D), and Z (ℤ, U+2124) were already codified years earlier in the Letterlike Symbols block (U+2100..U+214F). If you rely on mathematical offsets, those letters either display as undefined tofu blocks (``) or completely unrelated symbols.
The Solution: Rather than writing messy conditional gap logic, an explicit static glyph map compiled ahead-of-time keeps the client runtime O(1) and guarantees 100% stable rendering across iOS, Android, macOS, and Windows.
One huge UX oversight with "aesthetic font generators" is accessibility. Screen readers do not pronounce these glyphs as normal English letters; VoiceOver and NVDA pronounce 𝔄 as "Mathematical Fraktur Capital A". If users plaster this all over body text, it renders their profiles completely unusable for visually impaired users. We added an explicit accessibility notice right under the input reminding creators to reserve these purely for short bio tags/titles rather than body paragraphs.
If you'd like to test the real-time conversion and inspect the client-side implementation: 👉 Live site: https://fonts.100emoji.shop
Would love to hear how other frontend devs approach Unicode normalization and rare symbol handling!
I made this doc for a friend of mine who just started college and wanted to know basic frontend for starter, everyone keeps saying claude or gpt can code that easily and you gotta learn the tougher topics but you need to code a bit without any ai aid to build that curiosity and for once experience the joy of first time coding a site on your own.
PFA : here is the doc
![[AI] UI/UX & CSS Feedback Request for a Coffee Shop POS System (JSF + PrimeFaces 14)](https://preview.redd.it/q59vah4v7uyh1.jpeg?width=140&height=63&auto=webp&s=1134edaed69825631cb86c2d518b3c1eb27ff5b5 "[AI] UI/UX & CSS Feedback Request for a Coffee Shop POS System (JSF + PrimeFaces 14)") | Hi everyone! 👋 I'm developing a web-based POS & Coffee Shop Management System built with JSF (Jakarta EE 11) + PrimeFaces 14. I'm sharing screenshots of several management and administration views (Roles, Employees, Discounts, Products, and Characteristics). I would love to get your honest feedback on UI design, visual hierarchy, layout, and UX. 💡 Project Context This platform handles core store operations: Menu & Product Management: Items, types, categories, prices, and dynamic attributes. Discounts & Promotions: Flexible discount rates, date-range offers, and rule triggers. Staff & Security: Employee records, custom roles, and access control. Daily Operations: Cash registers, order processing, and invoicing (not shown in these specific shots). 🛠️ Tech Stack & Frontend Architecture View Layer: Jakarta Server Faces (JSF / XHTML) using modular facelets templates. UI Components: PrimeFaces (v14.0 - Jakarta edition) + custom CSS stylesheet (estilos.css). Backend: Jakarta EE 11 running on Open Liberty + PostgreSQL (JPA). Localization: Native i18n support (Spanish, English, Chinese). 🔍 Comprehensive UI/UX Feedback Checklist I'm looking for feedback on any of the following aspects: 1. 🎨 Visual Hierarchy & Layout (UI) Form & Table Balance: Does the vertical split between the upper form (Inputs) and the lower datatable look clean, or does it feel cluttered? Buttons & Actions: Are primary action buttons (Guardar / Save) clearly distinguishable from secondary ones (Limpiar / Clear)? Toast Notifications: You'll notice PrimeFaces growl/alert messages in some shots. Are floating toast messages appropriate here, or would inline banner alerts be better UX? 2. ⚡ Usability & Data Density (UX) Readability: Are datatable columns, badge statuses (ACTIVO), and action icons (Edit/Delete) clear and easy to scan for administrative staff? Form Field Spacing: Is the padding and margin between input fields, dropdowns, and checkboxes comfortable for desktop use? 3. 🖌️ Modernizing PrimeFaces & CSS Styling Default Theme Polish: What specific CSS tweaks (shadows, border-radius, background grays, typography) would you recommend to give the default PrimeFaces theme a cleaner, more modern look? Any suggestions, CSS snippets, or constructive critiques are highly appreciated! 🙌 [link] [comments] |
 | This is simply a starter template that I use and I thought of sharing
I encourage you to check and share your opinion [link] [comments] |
 | I write a weekly newsletter for senior frontend engineers. The picks for this week: - CSS-Tricks has a new owner and is independent again after 12 years. Geoff Graham made the announcement, and Mat Marquis wrote about what it looked like from inside DigitalOcean. - Design systems should be fast by default: Den Odell opened the same 249-country dropdown in ten popular design systems. One opens in 61ms, another in 1,266ms. - TanStack Redact: a smaller replacement for React and React DOM in the browser. Tanner Linsley says it cut a sample Vite app's client bundle by 70% without changing app code. - Reylo by Colin McDonnell (creator of Zod): import a .sql file into TypeScript and get the query types from a live database, no codegen step. Full edition with all the links: https://neciudan.dev/newsletter/34th-edition [link] [comments] |
Please post your comments in the original thread in r/Websites as I'm not OP:
https://www.reddit.com/r/Websites/comments/1xii9yw/glassmorphism_beautiful_or_horrendous/
Most of my apps/websites/projects are made by myself, the core functionality and most concepts, but i still struggle with the style and designing of the UI so i use AI for that part, most of the time only for the styling.
Is it bad ? Am i becoming lazy or would you consider it okay to cheat a little ?
Please post your feedback and comments in the original thread in r/Websites as I'm not OP:
https://www.reddit.com/r/Websites/comments/1xhnqj3/looking_for_feedback_on_web_analytics_ui_landing/
Login
