Mobile first web design was the worst decision ever in the history or web design.

If you know, you know. I’ll die on this hill.

FYI - this section is made from a reference image i found on pinterest.

I haven't built any WordPress sites in a while, and years ago I used Elementor as my page builder. Is it still the best page builder for WordPress today? Or are there better alternatives?

i built this website for a real estate agent. designed and completed in ±2 weeks. its minimal but not low tier

Hey Guys!

I just published a Free and open source alternative to Google docs that runs entirely local (or in browserDB) that also has AI feautures like: Fix grammar, improve text, real time document analysis, format etc.

It also has themes and dark mode.

• ✍️ Rich text editor (TipTap) — headings, lists, quotes, code, links, emoji, images, page breaks
• 🤖 AI review — grammar fixes, style suggestions, highlights, and circled passages you accept or dismiss
• 🖊️ Human markup tools — highlight, colored underline, circle, all as real document marks
• 💬 Notes — Google-Docs-style comments anchored to text, in a right-side panel
• 🖼️ Images — insert, paste, or drag-and-drop; stored on disk beside your docs
• 📄 Pages & typography — continuous or paginated (A4/Letter), free-form width, four document fonts, text-size control
• 📁 Folders & library — a Home dashboard and a card-grid /documents view
• 📤 Export — Markdown, Word (.docx), HTML, plain text, and PDF
• 📥 Import — Markdown, text, HTML, and Word (.docx)
• 🌗 Themes — light, dark, midnight, reading, forest — all token-driven

If you have the time to check it out, i would love some feedback

I recently got a freelance opportunity to help someone redesign their website. Since I don't have a lot of availability I asked some friends for help and split the money.

But I might have asked too many, a now a lot of desperate people want to play a part.

This is my first project so I will keep the rate the bare minimum like idk 1k for the entire site? But is 4 people a good number for max?

Really don't need a full app landing page to much but something that shows people what the app is about and I did finish the web yesterday. Would like anyone to give feedback on it what to improve and and how to get more users to see. Thanks for the feedback!

https://murkd-landing.vercel.app/

Why Figma-to-Code Projects Fail QA (And How to Avoid Launch Problems)

A Figma design can look perfect. The code can compile. The demo can impress the client. And the project can still fail QA before launch.

This is becoming more common with AI-assisted development and faster design-to-code workflows. Teams can move from idea to prototype incredibly quickly, but the gap between a visual prototype and a production-ready product is where most problems appear.

The question is no longer "Can we turn Figma into code?" The better question is "Can the generated code survive real users, devices, browsers, and future updates?"

Here are the biggest reasons Figma-to-code projects run into QA problems.

1. The design looks complete, but the system behind it is not

One of the biggest mistakes is treating Figma as the entire product specification.

A design file shows colors, spacing, layouts, and components. But it usually does not define:

• Error states
• Loading behavior
• Edge cases
• Accessibility requirements
• Responsive logic
• Content variations

A page can match the design perfectly and still fail when users enter unexpected data, screens resize, content becomes longer, or integrations return errors.

Good QA starts before development, not after it.

2. AI and rapid coding tools create fast prototypes, not always production systems

Tools like Lovable, v0, Bolt, and similar platforms are excellent for exploring ideas. The problem starts when teams assume the prototype is already a finished product.

Common gaps include:

• Inconsistent components
• Missing reusable architecture
• Weak CMS structure
• Poor SEO foundations
• Limited testing coverage

The prototype answers "What could this look like?" Production requires answering "Will this still work six months after launch?"

3. The design-to-code handoff is where quality often breaks

A strong Figma file does not automatically create a strong frontend. The most common issues:

• Developers interpret components differently
• Spacing changes between pages
• Mobile layouts are treated as an afterthought
• Reusable elements become duplicated code
• Animations and interactions are inconsistent

Without a proper design system, every new page increases maintenance costs.

4. QA should validate the foundation, not just find visual bugs

Many teams define QA as "Does it look like Figma?" That is only one part. A proper production review should check:

Functionality - Do forms work? Do interactions behave correctly? Are error states handled?

Performance - Does the site load quickly? Does it work on slower devices?

Accessibility - Can users navigate with keyboards? Are semantic structures correct?

Technical stability - Is the code maintainable? Can future developers safely extend it?

One case I saw recently: a product startup had AI-generated concepts that helped explore ideas quickly, but the output lacked the structure needed for production - consistent design logic, reusable components, CMS architecture, and SEO-ready implementation. A dev team transformed the prototype into a production website with a Figma design system, Next.js frontend, Sanity CMS, and launch preparation completed within five weeks.

The important takeaway: the problem was not creating the prototype. The problem was turning the prototype into something reliable.

For those shipping Figma-to-code projects: what's the most common QA issue you keep running into before launch?

Disclosure: I'm the developer, so read this as "here's a thing I made," not an unbiased review.

If you've ever gotten a brief that's basically "make it look like this" with a link and nothing else, you know the drill — click through DevTools element by element, write hex codes down by hand, guess at the fonts, eyeball whether the text passes contrast. I got tired of that and built PeekCSS to shortcut it.

It's a Firefox/Chrome extension: hover any element for its full computed CSS, or run a page-wide scan that pulls the whole color palette and every font in one pass, each tallied by usage so you can tell the primary brand color from a one-off accent. Every color pair gets an AA/AAA contrast badge automatically, so accessibility issues show up while you're looking, not after a client complaint. Palettes export to CSS variables, SCSS, JSON, or Tailwind.

Free tier covers hover inspection and contrast checking with no account. The full palette/font scan needs a free account; export and bulk asset download are the paid part (for the day-to-day heavy lifters xD)

For the devs here who do a lot of "recreate this reference site" work — what's usually the most annoying part of that process for you? Curious if I'm missing something obvious.

Support is out for most browsers, if you wanna check it out, i'd be forever grateful for some feedback and improvement suggestions: https://peekcss.com

Community based wireless carrier review & forum.

I've always been frustrated that cell coverage maps don't match what you actually experience.

A neighborhood can have great service on one street and terrible service two miles away, but the official maps usually show everything as "covered."

So I built a baseline version ofCellIntel (https://getcellintel.com), a community-driven wireless coverage map where people can leave real reviews for their exact location.
I have recently made some UI enhancements.

Current features:

- Search by ZIP code or city

- See community ratings for AT&T, Verizon, and T-Mobile

- Leave location-specific reviews

- Active discussions in community forums.

- Compare real experiences instead of carrier marketing

It's still an early version, so I'm looking for honest feedback.

- Is this something you'd actually use before switching carriers?

- What features would make it more useful?

- Anything that's confusing or broken?

-Opinions or overall design?

No pressure to sign up—I'm just trying to build something that helps people make better decisions about wireless service.

Any feedback would be greatly appreciated. Thank you for your time!

Thanks to vibecoding, landing pages nowadays are almost identical.

Did you see any creative design not so AI tasting landing pages?

I’ve been building Routeveil, an open-source React + TypeScript transition engine for React Router.

The goal was to keep transition state and animation timing out of individual route components.

Routeveil coordinates the full navigation lifecycle:

1. animate the current route out

2. commit the navigation

3. wait for the next route to render

4. animate the new route in

5. restore interaction and clean everything up

The basic setup looks like this:

<RouteveilProvider>

<Header />

<RouteveilView>

<Routes />

</RouteveilView>

<Footer />

</RouteveilProvider>

Then transitions are selected per navigation:

<RouteveilLink

to="/docs"

transition="slide"

transitionOptions={{ direction: 'left' }}

>

Documentation

</RouteveilLink>

It currently includes:

- 8 page transitions

- 12 full-screen overlay transitions

- typed transition-specific options

- declarative and programmatic navigation

- transition playback without navigation

- cursor-aware origins

- reduced-motion handling

- custom transition definitions

- safe recovery when a transition fails or navigation changes unexpectedly

For overlapping Routeveil requests, I currently use an ignore-while-active policy rather than trying to cancel and replace the running transition.

Live demo:

https://routeveil.dev

GitHub:

https://github.com/milkevich/routeveil

I’d appreciate feedback on the API and lifecycle, especially around interrupted navigation, focus handling, and whether this abstraction would actually be useful in a real React Router app.

Responsive is pending please view in desktop

Hey all! Any advice for a beginner? I can do basic things and really want to learn the right way the first time. Any advice, videos or anything you’re willing to share I’d appreciate.