Back
React on Salesforce: I Turned My CV into an Experience Cloud Portfolio and you can too!
Salesforce Multi-Framework is now GA, so I rebuilt my consultant CV as a React app running on Experience Cloud. This is a practical portfolio pattern for Salesforce professionals who want their CV to prove platform craft, not just list it.
React on Salesforce: the portfolio idea
Most Salesforce CVs are static documents. They list projects, certifications, tools, and job titles, but they rarely prove much beyond the words on the page. For consultants, architects, admins, and developers, that feels like a missed opportunity.
So I rebuilt my React CV as a Salesforce-hosted Experience Cloud portfolio. The goal was simple: create a public, forkable portfolio pattern that shows Salesforce knowledge, modern frontend delivery, and enough implementation discipline to be useful beyond a demo.
What this project is
This is a React on Salesforce portfolio built with Salesforce Multi-Framework, Vite, Tailwind, Salesforce DX, and Experience Cloud. It turns a consultant CV into a live web experience with a profile hero, certification proof, skills, project history, industry experience, and PDF export.
The content is deliberately easy to change. The sample CV data lives in one TypeScript file, so another Salesforce professional can fork the repo, update the profile, deploy it to a sandbox or Experience Cloud site, and share a working portfolio rather than another flat PDF.
Why Salesforce Multi-Framework matters
Salesforce Multi-Framework changes the conversation because React can now run natively on Salesforce in supported production orgs. Salesforce describes the GA release as a way to build React apps on the platform while still using Salesforce security, governance, GraphQL, Apex, and UI APIs without bolting on separate authentication plumbing.
For consultants, that matters. It means the answer to “can this live on Salesforce?” does not have to start with a defensive explanation about LWC rewrites, separate hosting, or awkward identity handoffs. For the right use case, you can keep a modern React workflow and still deliver inside the Salesforce platform.
SalesforceBolt made the same point in its earlier React on Salesforce explainer. It is useful background reading alongside the official Salesforce GA announcement because it frames the real-world appeal: teams can bring hooks, component libraries, and familiar frontend tooling into Salesforce without giving up platform governance.
What the build includes
The Experience Cloud portfolio includes a branded ConsultantCloud-style landing page, profile summary, certification count, Salesforce skills, work history, industry experience, external links, and browser-based PDF export. It is built as a Salesforce DX project so the source, metadata, and deployment notes sit together.
The React source lives under the WebApplication folder. The build process compiles it into a GA UIBundle, which is what Salesforce deploys. That distinction matters: the WebApplication source is where you work, but the UIBundle is what the Salesforce platform recognises in the current GA path.
The security lesson
A public Salesforce CV should be read-only. This project keeps optional auth Apex out of the default deploy path, disables self-registration, and treats the guest surface as something to minimise rather than decorate.
That is not the glamorous part of the project, but it is the part that makes the sample safer to copy. Multi-Framework opens the door to richer front ends on Salesforce, but the old platform instincts still matter: know your guest user, deploy only what you need, and do not turn a simple public page into an accidental application.
What I learned building it
First, deploy the UIBundle, not the experimental WebApplication source folder. The source is where the React app is built, but the deployed Salesforce asset is the UIBundle.
Second, PDF export needs care. Tailwind v4 can output modern colour formats that browser capture tools do not always like, so the print layout is isolated before capture and uses safer colours for the generated PDF.
Third, a portfolio project is more convincing when it has edges. A polished page is nice. A repo with deployment notes, security guidance, Experience Cloud metadata, and a repeatable build script is better. It shows that you can ship the thing, not just style the thing.
Want the LinkedIn Banner?
The certification banner is the bit I expect people to want first: Trailblazer, 7 Salesforce Certifications, and a public Trailblazer profile turned into something you can actually share.
If you want a LinkedIn banner like this, sign up to ConsultantCloud and add your public Trailblazer URL. The idea is that ConsultantCloud can generate a clean Salesforce credibility banner for your own profile, using your Trailblazer profile and certification count as the source.
Sign up here: https://www.consultantcloud.io/sign-up
Who should fork it
Fork this if you are a Salesforce admin learning React, a consultant trying to show platform range, or a developer who wants a more interesting Salesforce portfolio than another generic static site.
It is not meant to replace your LinkedIn profile or your PDF CV. It is meant to sit beside them as proof. A small public artifact that says: I understand Salesforce, I understand modern frontend tooling, and I can join the dots between the two.
Quick answers
Can React run on Salesforce? Yes. Salesforce Multi-Framework is GA and supports React apps running natively on Salesforce through the platform deployment model.
Is this useful for Salesforce consultants? Yes. A Salesforce-hosted React CV can demonstrate platform knowledge, frontend capability, deployment discipline, and security awareness in one shareable portfolio.
Does this replace Lightning Web Components? No. LWC is still the right answer for many Salesforce-native use cases. React on Salesforce is another option when a modern React app is the better fit.
Try it
Demo: https://d0y000002jj75uae-dev-ed.my.site.com/hostedcvsalesforce/
SalesforceBolt React explainer: https://www.salesforcebolt.com/2026/06/react-runs-on-salesforce-multi-framework.html
Official Salesforce GA post: https://developer.salesforce.com/blogs/2026/07/build-with-react-on-salesforce-multi-framework-is-now-ga
Repo: https://github.com/fizzy2562/hosted-cv-salesforce
Sign up here
