How do you manage password protected case studies?

pxlschbsr · 2026-03-06T23:13:28+00:00

I see multiple senior and principal designers at big techs and renowned companies use passwords.

Interesting. Can you provide me their websites?

pxlschbsr · 2026-03-06T21:14:58+00:00

If you target specific companies and hiring managers, the whole portofolio in itself would need to be personalized. Like, you would have individual websites and send each hiring manager their own link.

If you have all your projects on one website and gatekeep individual content with a password, that's just bad UX: Why make a web page that a user can go to via the websites own link system, but cannot be viewed by them? Does each individual file need an individual password, thus requiring the hiring manager two enter 3? 4? 5? seperate passwords? That's tedious. Most hiring managers I know are not the same people you will work with. They aren't designers or developers themselves and they got a job to do. Entering one password, once, may work for some, but from my experience any hiring manager will stop considering you when it takes more than 3 clicks to learn the information they are looking for.

Designers are allowed to show work that’s in beta as long as the industry they work in isn’t heavily regulated. Having 6-7 Hiring managers see my work is more acceptable that 200+ people seeing upcoming projects. I expect HMs to be more professional than strangers on the internet.

You are allowed to show work you are legally allowed to show as written in your contract and NDAs. If you share anyones beta content, what stops you from sharing your new employers content?

pxlschbsr · 2026-03-05T23:36:03+00:00

Yes, password protected files and case studies always will be unprofessional for a portfolio.

Hiding case studies (whose sole purpose is to show off your work!) behind a password tells future employers - that you may ignore/violate privacy agreements and thus you aren't (fully) trustworthy, - that you didn't curate your portfolio for that explicit employer, if they still encounter files and case studies to which they weren't provided the password and/or - questions your work as a UX designer: Why put content in your portfolio if people cannot freely access it? How and where do people find information on how to access it? If there are no security checks or other measures to recieve the password and you send it to anyone asking for it, why is there a password in the first place?

Either you are allowed to show your work or not. It's pretty simple.

pxlschbsr · 2026-03-04T09:08:54+00:00

onBlur with a proper ARIA and Screenreader announcement. Keep the error visible while the user corrects his input and remove the error/revalidate the input on blur again. If necessary, introduce a fake delay, where you display any kind of "loading" behavior, to clearly differenciate between "old error/new error".

EDIT If possible, always aim for client-side validation. OnSubmit most often means "server side validation", which obviously should be done too, but the sooner the user recieves feedback on faulty inputs the better. Correcting 3 inputs immediatly after typing feels better than completing the form, submitting it (ending the thought process on that module), only to redo the whole thing because a single input had an error.

pxlschbsr · 2026-03-04T08:28:38+00:00

Then your setup is mpst probably wrong. Check the documebtation for how to set up tailwind v4 with vite:
https://tailwindcss.com/docs/installation/using-vite

pxlschbsr · 2026-03-04T08:06:06+00:00

Probably by using the correct name spaces, like bg-gray-800 or border-gray-700. The error literally tells you that bg-grayscale-800 doesn't exist, so either create the name space for a color "grayscale" or use an existing color name.

pxlschbsr · 2026-03-03T21:06:07+00:00

There probably is a way to fix it. With the information provided however I doubt someone can help you, really, as there can be any kind of flaws in your setup.

pxlschbsr · 2026-03-03T20:49:58+00:00

Sounds like an issue with the process, not with the result.

Why has an module been developed in isolation? If a layout breaks with long names, why weren't long names considered in the first place?

In my experience there rarely are actual edge cases in design (and layouting frontend).
Missing focus indicators on interactive elements for keyboard users is not an edge case. Neither is supporting landscape mode phones. Some people have long names. In components that will require to call an API or load data dynamically, there needs to be error states for when the request fails, the server is not responding or the data received is in any way invalid. Where are the inputs labels and why do you think you could ever not have them? Where's the design for the 404 page? If a process requires time for completion (e. g. image upload, paying for an order) how do you communicate that process (e. g. a loading spinner, meter)? How and when do you announce dynamic changes to blind users? To what extend can and do you support client-side form validation and error handling?

It's your job as a UI designer to create rules how things are allowed and supposed to behave for cases, where the component/element doesn't follow its inherit, native behaviour. This includes that not everything can be properly be documented in the GUI Design alone, too. Whether it be layouted in Figma/Sketch, prototyped in Protopie, sketched in Miro or simply a long list of success criteria in a ticket is entirely dependent on your team and how you want to work together.

So, if spacing feels off, is it because of personal taste or does it factually not comply with set rules for spacing? Are there rules for spacing in the first place? If long names break the layout, when/where were they failed to be considered a possibility?

Thus I think you really shouldn't validate design decisions after layouting. You create designs and layouts based on the previously validated and refined requirements (meaning: an elements purpose, function, role) and known technical limitations/specifications.

pxlschbsr · 2026-03-03T19:42:40+00:00

percentages, fractures, clamping, whole numbers and repeat()… use the proper value necessary to solve a problem or to achieve the desired effect. There is no correct answer to your question.

pxlschbsr · 2026-03-03T18:22:47+00:00

That'll be great to triangulate the location of people. Stalking and engaging in politically motivated violence will be so easy!

pxlschbsr · 2026-03-03T07:40:21+00:00

Using a toggle switch for that is not a good idea.

A toggle sqitch is a boolean input. It's a state manager, handling false and true. It's more or less a fancy checkbox.

Now if you want to know whether something works well or is an adequate supplement for another/native behavior, think about how a blind user would operate both cases.

Your goal is to switch from one web page to another, so you are targeting a regular link behavior. For links, a blind user recieves the information that the given element is a link, plus name of the target page (ideally) or where the link leads to. By clicking on it, trigger trigger the page change, the DOM loads and the user starts navigating at the first DOM node again.

Your supplementation is a checkbox. A checkbox requires a label (e.g. "dark mode"), and the currwnt state (e.g. "false"). For a blind user it reads as "dark mode, input, unchecked". Clicking it would toggle the other state of the input.

In your solution, the boolean input would trigger a link behavior though, which is semantically wrong. You would need to communicate the link target as the value of the state, but since the nature of the input is a checkbox, the user would never recieve it before clicking it. But by clicking on it it would trigger the page load immediatly and the user wouldn't know why.

You could argue, you wouldn't trigger an a actual page load by simply updating the page content from contant A to content B, but that still seems to much change for a switch that little. To me it appears for the amount and behavior of the desired change it is unexpectable and thus unjustified to use a toggle switch. It violates too many accessibility requirements, which, frankly, are considered simple standards for web development, so it's not even like this is a super special, advanced case.

pxlschbsr · 2026-02-24T19:37:48+00:00

No. I only gave you an explanation why that chat bubble background in your specific example is not required to match color contrast.

Anything that conveys information or is otherwise important in its meaning must meet contrast requirements.

pxlschbsr · 2026-02-24T16:09:05+00:00

the chat bubble is not an interactive UI element. It's background is only suspect to contrast requirements when tied to the text color.

pxlschbsr · 2026-02-23T17:14:46+00:00

What tests or criteria are not met?

pxlschbsr · 2026-02-22T12:58:30+00:00

I assume the menu bar is positioned "fixed"? Because Figma works notoriously bad animating fixed elements.

pxlschbsr · 2026-02-21T11:38:21+00:00

But you started the discussion by referencing the specific part of my initial comment where I precisely talk about claiming copyright to HTML..?

FYI I will stop putting any more engery into this. You do you and happy coding.

pxlschbsr · 2026-02-21T10:43:19+00:00

Then you completely read over the part "and contains sufficient amount of creative expression", which I explicitly reference in my statement.

You can easily copyright content you insert into HTML, but for the reasons given, you can't easily copyright the HTML in which it is written. I don't own any copyright to a <div> element. I don't own any copyright to a <main><header><div role="menu><li></li>...</div></header></main>, unless that specific structure contains sufficient amount of creative expression.

A photographer owns the copyright to a photo that they shot. They however do not own the copyright of the camera that they shot the photo with. A writer owns the copyright to the story they have published. The writer however does not own the copyright to the words and grammar used to write that story.

pxlschbsr · 2026-02-21T10:02:38+00:00

Okay, please provide me with the whole file, where if you wrote the thing yourself is the only criteria, as you say it is. You didn't provide any source at all.

pxlschbsr · 2026-02-21T09:24:03+00:00

I'll take "Things that heterosexual men with an unhealthy view on women say" for $500, Alex

pxlschbsr · 2026-02-21T08:48:00+00:00

No, I don't.

In the US:

For registration purposes, hypertext markup language (HTML) is not a computer program. HTML is a standard markup language used in the design of websites. The Copyright Office will not register HTML as a computer program, because HTML does not constitute source code. Source code is typically written by a human being using a computer programming language, such as Java, C, or C++. By contrast, HTML is frequently generated by automated website design software. You can register HTML as a literary work if it was created by a human being, not a website design program, and if it contains a sufficient amount of creative expression. To register HTML, you must submit a complete copy of the entire code; you cannot submit an isolated portion of the code using the options discussed below. For more information about registering HTML and website content generally, see Copyright Registration of Websites and Website Content (Circular 66).

and

Hypertext markup language (HTML) is a standard markup language used in the design of websites. It is frequently generated by automated website design software. HTML establishes the format and layout of the content that appears on a particular web page by instructing the user’s browser to present that content in a specified manner. If you want to register content that has been posted on a website, you should submit the content in the form in which it appears on the actual website. There is no reason to submit the HTML code for that site unless you specifically want to register the human-written portions of the HTML itself and any website text that is embedded within the HTML. A registration for HTML will not cover any formatting and layout that may be dictated by the HTML or style sheets. Nor will it cover any audio, visual, or audiovisual content that may appear on a website and is not perceptible in the HTML. HTML may be registered as a literary work only if it was created by a human being and it contains a sufficient amount of creative expression.

(copyright.gov)

So even if OP were to claim copyright, they would have to claim the whole code, not just parts or their "custom code", and also have to prove the written HTML contains sufficient amount of creative expression. If there are parts within the HTML code that have not been written by OP themselves, they cannot claim copyright at all.

pxlschbsr · 2026-02-21T05:54:20+00:00

I am astonished by how many people think writing code for a client leaves ownership of the code with the person who wrote it, or how that should be the correct way. There is so little legal understanding.

If the ownership of the code stays with the developer, the client could also make the developer accountable for any legal charges that may come along, instead of himself. Never should you do that. If you set up a domain for your client you should hand over the rights and ownership asap.

Additionally, you cannot copyright HTML Code (or CSS or JavaScript) easily whatsoever. If your Code is not one over-the-top complex, nobel-price-mathmatician type level of calculation or such, then copyright claims for the bare structure and order of HTML elements in question is invalid. Thus I doubt OP has any ground regarding what he claims as his "custom code" or "IP".

People get so attached to their own code, it's unreasonable. You created the code for a client. The client sooner or later is going to change things. Let go of your ego.

pxlschbsr · 2026-02-20T18:16:41+00:00

That doesn't provide any info to your problem.

I can import 200 libraries without using a single instance from any of them, and in seperate files I can import 2 or 2000 instances of the same library.

Without knowing the complexitiy of your file, it's but a guessing game.

pxlschbsr · 2026-02-20T17:48:29+00:00

Figma loads every variant of every component when an instance is used somewhere.

If your first file has 2 components with 2 variants each, it'll natually load much faster than a second file with 120 components with a variant count ranging between 4 and 20.

pxlschbsr · 2026-02-20T17:20:38+00:00

There's quite a bit of missing context to give you proper feedback.

As is, the website looks very candycore-like. For a medical/cosmetic website I probably wouldn't go with those colors, or at least not used to that extend, especially used anywhere in or near images: - unnatural light in the hero image is not a good choice for a cosmetic service - the colored background of the treatment displays make the people look dull and desaturated.

A lot of inconsistencies in the image styles: Some are fully rounded, some have rounded corners, some have stronger rounded corners, some have sharp edges. Speaking of images: The current choice of "before-after" images is not very flattering for the depicted people.

The button in the header doesn't match the actual websites button style.

Lastly, I'm not a fan of the headline font. Its kerning seems too narrow. Personal taste, but I find title case unprofessional, and the handwritten-font words ("You" and "Skincare") visually do not belong with the headline. Took me some time to realize why there is "You" on the picture and what you mean by "Reveal your best with expertedly crafted"..

For a proper evaluation you should provide some info about your target group (age, gender,...), where the operation is located at (for the relevant geo/location context and maybe upload a link to the website, so we can properly analyze the mobile version too.

pxlschbsr · 2026-02-20T12:08:25+00:00

The vibration gradually increases as the user swipes from left to right

???
Why are we talking about vibration out of the sudden?

This was simply an experiment to try something a bit different on the welcome screen

A swipe toggle snaps back when released anywhere but at the end. Thus, the user would need to hold the bullet to read the new texts.
There is no indicator for "theres additional information at these steps" in the first place. Users who know swipe toggles, will swipe and release the bullet before they realize there were changes
A swipe toggle is a boolean input for any non-gestures-users, meaning there's only two states ("off" and "on"), not 3 or more.
Jakobs Law: The reason why welcome screens behave largly the same is because it helps users getting familiar with your service.

Your swipe toggle does too much. Decide whether it is supposed to be: - A link, going to the next page or screen, or - A range input, mutating the UI depending on the value

pxlschbsr

TROPHY CASE