Job search
UXfolio Alternatives: Keep Case-Study Guidance, Private Sharing, and Recruiter Access
Preserve your case narrative and reader access before choosing a document portfolio, a custom site, or staying with UXfolio.
Choose a UXfolio alternative by naming the capability you need to preserve: help explaining a case, password or invitation access, or freedom over its presentation. Notion is worth investigating for a document-style portfolio you can edit yourself. Framer is worth investigating for a custom site you are prepared to maintain. Keep UXfolio on the shortlist when guided case writing and individual case passwords solve the actual problem.
Before rebuilding a homepage, carry one representative case through the proposed workflow. Check whether its reasoning remains clear and whether the intended reader can reach it. LandOffer publishes this comparison; its recent job listings can supply a target role for deciding which case belongs first. This is a public-documentation review checked October 22, 2026, not a paid-editor trial, access-security test or recruiter study.

Establish the UXfolio capabilities you are replacing
UXfolio’s July 2026 feature guide describes section-specific questions, structured draft assistance and Figma prototype embedding. Those are useful distinctions for someone whose project notes have not become a readable argument. A general-purpose page builder gives you somewhere to arrange the argument; it does not establish why your chosen design followed from the evidence.
Its current pricing page offers a seven-day trial with unlimited draft portfolios and case studies. The trial includes four AI actions, divided between two case-study attempts and two Job Fit Checker attempts. Publishing and password protection belong to paid access. The annual offer displayed US$108 billed yearly, expressed as US$9 per month. That monthly equivalent is not a monthly payment schedule.
Treat drafting and sharing as separate requirements. A saved trial case is useful for evaluating the writing workflow, but it is not an application-ready live link. Equally, unlimited public cases do not mean that every piece of work is yours to disclose. Get permission for the content before choosing the access mechanism.
Compare the replacement task, not a universal winner
This shortlist deliberately compares two different substitutes. It is not a ranking of every portfolio builder or a claim that either reproduces UXfolio’s editor.
| Requirement | UXfolio baseline | Notion route | Framer route |
|---|---|---|---|
| Case-writing guidance | UX-specific section questions and structured assistance | Carry your own case outline into pages | Build your own content template and editorial rules |
| Public reading | Paid publishing | Published Notion Site | Free Framer domain or paid custom-domain route |
| Restricted reading | Portfolio or individual-case password documented | Private guest invitation requires a Notion account; no native page password documented | One shared site password documented; do not assume individual-case controls |
| Prototype presentation | Native Figma prototype embedding described | Embed blocks with source-dependent behavior | Embed component; source may block framing |
| Continuing work | Case content and presentation within a dedicated tool | Page structure, permissions and linked material | Layout, content model, responsive behavior and linked material |
The last row is editorial judgment about the work to budget, rather than a measured time comparison. A builder may fit your skills well enough that this work is welcome. It still needs an owner when you later replace a screenshot, shorten a narrative or retire a project.
Notion: accept the document workflow and its access trade-off
Notion’s Sites guide documents web publication, automatic content updates and an unlimited number of published pages. Additional customization and a custom-domain add-on involve paid options. That provides a plausible route for an approved public case whose structure is already settled.
The same guide’s password FAQ says page password protection is currently unavailable. Its permissions documentation says an invited guest needs a Notion account. A public link and a named private invitation therefore offer different reading experiences. Decide whether a reviewer can reasonably use the invitation route before choosing it for an application.
The Sites guide also warns about default subpage publication and contributor information in webpage metadata. Review the surrounding page tree, not just the visible opening paragraph. Turning off search indexing does not create a private room. For a case that must remain restricted, a public Notion page is not a substitute for UXfolio’s individual-case password.
The attraction here is a familiar document workflow. You can keep a clear sequence of headings and captions without designing a new visual identity. The work you take over is specific: place evidence beside the decision it supports, remove process stages you did not perform, and make the opening explain your role and scope. A polished template cannot make those decisions for you.
Framer: buy presentation freedom with a maintenance plan
Framer’s pricing page displayed Basic at $10 per month with yearly billing selected, with 30 site pages, two CMS collections and 1,000 CMS items. The comparison table visibly included site password protection under Basic. A custom domain requires a paid plan. These are public plan observations, not a checkout total; the page says applicable sales tax is added at checkout.
A few case studies do not automatically require a higher tier. Count ordinary pages, collections and items separately, then look at the exact feature that changes the purchase. The number of case studies alone does not establish bandwidth needs or prove that an embedded prototype works.
Framer’s password lesson describes one shared password in front of the site, rather than individual user accounts. The lesson is dated September 2023 and now flags interface changes after June 2026. Use it for the documented access concept, not as proof of today’s exact button sequence or per-case restrictions.
This route makes sense when your narrative is strong and a specific layout requirement remains: perhaps you need a clearer relationship between a dense service map and its explanation. Budget for narrow-screen reading and later revisions. If the entire site is gated, even the introduction can require a password; that is a different application journey from a public homepage with one protected case.
Worked migration: preserve Mira’s reasoning before the layout
Mira is a fictional designer moving a personal, non-client library reservation exercise. The example contains no employer material, actual research results or live portfolio. Her goal is to preserve one design decision while investigating Notion, not to reproduce every UXfolio decoration.
Her original notes say: “Reservation flow, list and calendar options, pickup deadline, confirmation.” That inventory names screens but does not explain the decision. She completes this content map before choosing blocks:
| Case section | Completed material to retain | Reader question it answers |
|---|---|---|
| Scope and ownership | Personal design exercise; Mira created the flow and screens; no implementation | What did she actually do? |
| Constraint | A reservation must show both pickup location and the final collection date | What makes the decision difficult? |
| Alternatives | Calendar-first exploration versus list-first exploration | What credible options were considered? |
| Decision | List first, with collection date beside each reserved item | Why this arrangement? |
| Supporting artifact | Two simplified sketches and an annotated comparison of information placement | Where can I inspect the reasoning? |
| Remaining uncertainty | No usability evaluation or live circulation-system integration | What has not been demonstrated? |
The calendar-first alternative remains in the case as a rejected exploration: it foregrounds dates, while her stated design aim is to keep item-specific collection information together. This is her design rationale, not a usability finding.
Her finished opening is:
I designed a personal library reservation concept focused on collection deadlines. I compared a calendar-first route with a list-first route and chose the list because it keeps the item, pickup location and final collection date together. The sketches below explain that information-placement decision. This exercise was not implemented or evaluated with library users.
Her migration brief is equally specific: “One page, six headings, the opening above, two sketches beside the alternatives, and an uncertainty note beside the final screen. Remove the generic discovery timeline because there was no discovery study. Keep the original text and images separately from the page builder.”
Mira chooses Notion as the next route to investigate because this case can be public and her outline is complete. She does not choose it as a password replacement. Her completed result is a portable content specification, not an imported page or proof that any template improves hiring outcomes. If she later needs guidance for a less developed case, staying with UXfolio remains reasonable.

Worked access decision: Jules separates the introduction from the case
Jules is another fictional author. His proposed portfolio contains a public introduction and a reconstructed personal scheduling exercise intended for a small review group. He wants the introduction to remain open, the exercise to circulate only with a review password, and no reviewer to need a new workspace account. No real invitation, password, publication or application occurs in this example.
He completes the following access record rather than selecting the builder with the longest feature list:
| Item | Intended reader path | Documented fit | Decision |
|---|---|---|---|
| Introduction | Open without credentials | Public page route available across the shortlist | Keep this route simple |
| Case narrative | Shared password, without a new reviewer account | UXfolio documents individual-case passwords | Retain UXfolio for this requirement |
| Same narrative in Notion | Named private invitation | Guest must have a Notion account | Does not meet his preferred route |
| Same narrative in Framer | Whole-site shared password | Site password documented | Would also gate the introduction if both occupy that protected site |
| Prototype | Readable separately from case access | Builder embedding is not proof of source access | Keep the explanation complete without relying on interaction |
His completed choice is to keep UXfolio, because replacing it would introduce an access trade-off he does not want. This is a legitimate alternatives decision: discovering that a capability matters can justify retaining the starting tool.
He drafts this unsent introduction for a permitted review channel:
My portfolio introduction summarizes the kind of design work I’m presenting. The scheduling case is a personal exercise with a separate case password, which I can provide through your preferred channel. Its annotated screens explain the key decision without requiring the interactive prototype. Please let me know if your review process requires a different format.
That note describes a proposed route, not successful delivery or recruiter access. His acceptance task remains to inspect the published case as an intended visitor. UXfolio’s case-password instructions warn that a signed-in owner will not see the password prompt and recommend an incognito check. His own editor session would therefore be insufficient evidence.
Keep the prototype’s permissions separate
An embedded prototype introduces another dependency after the reader reaches the case. Notion’s embed guide notes that external-login embeds do not work in its desktop or mobile apps, and that source changes appear in the embed. Framer’s embed documentation warns that source websites can block framing through HTTP headers. Neither statement verifies your particular prototype.
Keep a concise explanation and permitted static fallback in the case itself. Describe what interaction the reader would inspect and what the screens omit. Then, before using a real application link, check both the portfolio route and the prototype route from an appropriate visitor context. Decide whether the prototype may be shown before configuring its access. The enclosing page’s password does not change the source file’s permissions.
Choose the smallest migration that solves the problem
Keep UXfolio when its writing questions or individual-case access are the features you would otherwise rebuild. Investigate Notion when the narrative is finished, the document format fits, and either public reading or account-based guest access is acceptable. Investigate Framer when a defined presentation need justifies owning the site’s layout and maintenance.
Before paying, write down the capability that is missing today and the work you will take over. Preserve original copy, image files and a record of application links; changing hosts does not promise a one-click transfer or portable site export. Compare the next billing commitment with the actual feature needed, rather than treating all displayed monthly equivalents as monthly contracts.
Use one relevant role from LandOffer’s recent listings, choose the case that explains a related decision, and complete a content map like Mira’s. Then record the intended reader route like Jules’s, including any login or password step. Move only when the new route preserves both the case explanation and the access you need; otherwise, improve the existing case first.


