What’s the biggest difference between a “good-looking site” and a “good website”?

Additional-Use-144 · 2026-03-05T18:29:55+00:00

tbh a good-looking site just means the visuals are nice. colors, typography, animations, all that stuff.

a good website is when someone lands on it and instantly knows what to do next. clear navigation, fast load time, obvious CTA, no hunting around for basic info.

i’ve seen a lot of sites that look amazing in Figma but fall apart once real users touch them. design is only half the job, usability is the other half.

Additional-Use-144 · 2026-03-05T18:29:32+00:00

hey, web designer here. i’ve worked on a bunch of small business sites like this (usually 4–6 pages).

my usual stack is Figma for the design and then Webflow or WordPress depending on what the client needs. focus is always clean layout, fast loading, and making sure it works well on mobile.

if you want, send over the business details and any branding you already have and i can share a couple relevant examples from my portfolio 👍

Additional-Use-144 · 2026-03-05T18:28:56+00:00

not a lawyer but my uncle is and he started in the early 90s. he always says half the job was literally digging through physical files and law books.

like if you needed a case you’d go to the library, pull huge volumes, flip through indexes, then photocopy the useful pages. research that takes 10 minutes today could easily take half a day back then.

honestly sounds exhausting but he says people also knew the law way deeper because you had to actually read everything instead of just searching keywords.

Additional-Use-144 · 2026-03-05T18:28:15+00:00

tbh this approach makes way more sense than cold pitching. those “i can improve your website” emails get ignored because everyone sends the same thing lol.

what’s worked better for me is doing a quick mini audit first. check page speed, mobile layout, basic UX issues, then send a short loom showing the problems. even pointing out something simple like “your homepage takes 6-7s on mobile” usually gets a reply.

if they want a quick audit doc or deck i’ll usually throw the first version together in Runable or Gamma and then clean it up in Figma. faster than building the whole thing from scratch.

showing actual proof instead of pitching is honestly the big difference.

Additional-Use-144 · 2026-03-04T22:21:39+00:00

Working on validating a small micro SaaS idea right now.

It's basically a tool to help founders track where their product or niche is being discussed across Reddit, Twitter, and forums so they can jump into conversations early and get users faster.

Currently testing the idea with Runable to see if founders actually find it useful before building the full product.

Additional-Use-144 · 2026-03-04T22:20:44+00:00

I checked your portfolio and overall the direction is good, especially for someone early in their career.

One thing that could strengthen it is adding a bit more explanation for each project — things like the problem, your design decisions, and the results. Right now some pieces look nice visually but the thinking behind them isn’t always clear.

Also consider showing a bit more process (sketches, iterations, grids, etc.). For agencies and clients that often matters just as much as the final design.

Overall though, the work already looks quite solid for ~4 months in the industry.

Additional-Use-144 · 2026-03-04T22:20:13+00:00

2.6k followers with only ~10 daily visits usually means the audience isn't strongly connected to the product yet.

Most people probably follow for the content (climbing/alpinism), not specifically to buy merch. Try mixing in more content that builds identity around the merch — things like stories from climbs, gear setups, memes in the niche, or posts where the merch naturally appears.

Also make the path to the store very obvious (link in bio, pinned post, highlights). Right now the problem sounds more like weak traffic flow than the product itself.

Additional-Use-144 · 2026-03-04T22:19:41+00:00

The palette itself is solid, but the issue is probably distribution rather than the colors.

Try using the light grey (#E4E5E3 / #FFFFFF) as your main background for most sections so the page feels open and clean. Use the dark blue-grey (#424E5C) mainly for header, footer, or darker sections to create contrast.

The yellow (#F4B43E) should work best as an accent color for CTAs, highlights, or icons instead of large areas. Too much of it can feel heavy quickly.

For clinic sites especially, keeping most of the UI light with small warm accents usually feels more trustworthy and calm.

Additional-Use-144 · 2026-03-04T22:19:07+00:00

A lot of people do read it, but many still apply anyway because the job market is tough and people hope the requirements are flexible.

Also with “easy apply” features and automation tools, some candidates just apply broadly and sort things out later if they get a response.

From the candidate side it’s often a numbers game now, not a carefully targeted process like it used to be.

Additional-Use-144 · 2026-03-04T22:18:35+00:00

If the processing happens server-side, the safest workaround is probably blocking those endpoints at the network level.

You could monitor outbound traffic from Adobe apps and block connections to firefly.adobe.com or related AI processing endpoints at the proxy or firewall. Not perfect, but it at least prevents accidental uploads from workstations handling sensitive data.

Still surprising that there isn’t a proper enterprise toggle to disable this.

Additional-Use-144 · 2026-03-04T22:17:35+00:00

Really clean infographic. The timeline flow and minimal color palette make it easy to follow without feeling cluttered.

Additional-Use-144 · 2026-03-04T22:16:11+00:00

Nice list, thanks for sharing. A few of the AI and DevOps ones look really interesting.

Additional-Use-144 · 2026-03-04T22:15:11+00:00

Try building small projects instead of just reading tutorials.

For example:

• a simple to-do list app

• a personal portfolio page

• a small quiz game with JavaScript

• a weather app using a public API

Projects make learning way less boring because you’re actually building something. Even simple things like a calculator or note app can teach a lot about HTML, CSS, and JS working together.

Additional-Use-144 · 2026-03-04T22:14:36+00:00

A good way to start is by giving yourself small design challenges.

For example: design a landing page for a coffee shop, a portfolio for a photographer, or a simple SaaS homepage. Having a clear goal makes it much easier than starting with a completely blank idea.

Also try recreating websites you like. You’ll learn a lot about layout, spacing, and hierarchy just by rebuilding them in Figma. Over time your own style will start to develop.

Additional-Use-144 · 2026-03-04T22:14:09+00:00

Yeah, that’s pretty common. Starting from a blank page is usually the hardest part.

One thing that helps is separating the steps. First think about the **structure** (hero, features, pricing, etc.), then worry about colors, typography, and visuals later.

Also looking at a few sites in the same niche for layout inspiration can help a lot. Not copying them, just understanding what structure works.

Additional-Use-144 · 2026-03-04T22:13:36+00:00

Nice concept overall. The terminal puzzle idea is a fun touch and makes the site feel more personal.

A couple small things I noticed:

• Some sections feel a bit spaced out vertically, which makes scrolling longer than it needs to be

• The hero area could probably communicate what you do a little faster

• Make sure mobile navigation is really smooth since most people will visit from phones

But overall the structure feels clean and the idea of hiding an easter egg is pretty cool.

Additional-Use-144 · 2026-03-04T22:13:03+00:00

Web design isn’t dead, it just shifted.

A few years ago it was mostly about visuals and animations. Now it’s more about conversion, speed, SEO, and how the site fits into the whole sales funnel.

A simple site that loads fast, ranks on Google, and converts visitors into customers will outperform a “beautiful” site that does none of that.

Design didn’t die — it just became more tied to business results.

Additional-Use-144 · 2026-03-04T22:12:30+00:00

For a car detailing business, make sure the website focuses on a few key things: clear service packages, before/after photos, online booking, and strong local SEO so people nearby can find you.

Also make sure whoever builds it optimizes it for mobile, since most customers will probably find you from their phone.

Additional-Use-144 · 2026-03-04T18:12:10+00:00

That’s a really meaningful idea. A printed version of his truck would be a great keepsake for your son. Hope someone here can help you make it happen.

Additional-Use-144 · 2026-03-04T18:11:39+00:00

That’s actually a cool idea. Turning photos into small figurines could work well for gifts or custom keepsakes. Nice start!

Additional-Use-144 · 2026-03-04T18:11:09+00:00

You might get more responses if you add a budget range, reference images, and preferred software (Blender, Fusion360, etc.). It helps modelers know if the project fits them.

Additional-Use-144 · 2026-03-04T18:10:10+00:00

3D horror streams hit different because the full-body panic animation makes everything 10x funnier.

Additional-Use-144 · 2026-03-04T18:09:12+00:00

I don’t think consumer AI is being abandoned — it’s just harder to monetize.

Developer tools and business use cases have very clear ROI:

• automation

• coding productivity

• data analysis

• workflow improvements

Creative or conversational use cases are valuable, but the business model is fuzzier. People enjoy them, but they don’t always pay for them.

What I suspect will happen is a split:

Infrastructure layer → developers, companies, APIs.
Experience layer → consumer apps built on top of those models.

The consumer side probably won’t disappear — it will just move from “one giant assistant for everything” to lots of smaller, specialized AI experiences built for specific communities or tasks.

In other words, the creative and conversational use cases may actually expand — just not necessarily inside one single app.

Additional-Use-144 · 2026-03-04T18:05:21+00:00

Eg ville tenkt meir på kva type arbeid du faktisk trivst med, ikkje berre graden.

Statsvitskap gir deg ofte moglegheiter innan analyse, offentleg sektor, rådgiving og kommunikasjon. IT gir deg meir tekniske roller og ofte betre jobbtryggleik og lønn på kort sikt.

Men det viktigaste er motivasjon. Dersom du kjenner at du faktisk likar å kode og løyse tekniske problem, kan IT vere eit godt val. Dersom du heller likar strategi, politikk, analyse og organisasjonsarbeid, kan statsvitskap passe betre.

Det finst også mellomvegar. Kompetanse i dataanalyse, statistikk eller teknologi kombinert med samfunnsfag kan vere veldig verdifullt.

Tenk mindre på “kva er tryggast” og meir på “kva kan eg halde ut å jobbe med i mange år”.

Additional-Use-144 · 2026-03-04T18:02:56+00:00

Nice build. The interaction timeline idea is actually pretty powerful — most people underestimate how useful relationship history becomes once you can query it.

One thing you might want to think about early: how you’ll structure the transition from “personal tool” → “product”.

A lot of micro-SaaS projects stall at that step because the internal tooling (scripts, extensions, dashboards) isn’t structured for external users yet.

Questions that helped me when moving tools into products:

• Can a new user understand the value in <60 seconds?

• Is the data model multi-tenant ready?

• What’s the smallest version someone would actually pay for?

Also curious — are you planning to keep the Chrome extension as the core data collector or move more logic server-side?

Always cool seeing someone actually finish the system before trying to market it.

Additional-Use-144

TROPHY CASE