DevFolioX docs
DevFolioX gives you a live portfolio link without writing code, and shows you every open and where it came from. This page covers everything it can do today.
Get started
The whole flow is four steps, and only the first one takes real time.
- Fill in your details. Type them in, import a résumé, or pull projects from GitHub.
- Publish. Sign in and press Publish. Your portfolio goes live at
/<username>/<portfolio>. - Share the URL. Put it on LinkedIn, your résumé, or in job applications.
- Watch the numbers. The analytics page shows views, visitors, sources, and clicks for every published portfolio.
Fill in your details
Your profile holds your experience, projects, skills, social links, and custom sections. Start from a truly blank workspace, load the demo, or use one of the importers below.
Resume import
Upload a PDF or DOCX résumé up to 5 MB. It is parsed in memory and never stored. You review and edit the extracted profile, experience, projects, and skills before anything is applied.
GitHub import
Enter a public GitHub profile and choose repositories. Descriptions, languages and topics, repository links, and homepage links become editable projects.
Health check
Before publishing, run the health check. It flags missing identity or contact details, weak targeting, incomplete projects, link issues, résumé readiness, and layouts that need an image you have not added.
Custom sections
Add custom sections for certifications, awards, education, writing, speaking, open source, or anything else. They support eight layouts: list, cards, timeline, grid, compact, split, spotlight, and badges.
JSON editor
For bulk edits, the advanced JSON editor exposes the complete workspace: content, portfolio versions, targeting, design, branding, résumé data, and custom sections.
Publish and share
Publishing creates an immutable snapshot of your portfolio at a clean URL in the form /<username>/<portfolio>. Keep editing afterwards; visitors see the published version until you publish again, and the URL does not change.
- Publish, unpublish, duplicate, and delete each portfolio from the portfolio manager; rename it in the builder.
- Set a per-portfolio favicon, share title, share description, and share image for link previews.
- Attach a public résumé to an individual portfolio, shown in one of seven treatments: embedded, card, compact, split, spotlight, minimal, or terminal.
- Published pages include canonical and social metadata, JSON-LD profile data, sitemap discovery, skip navigation, and reduced-motion support.
Design
Every section has its own layout, chosen independently of the theme. None of it requires code.
| Themes | 10: Ink, Sand, Moss, Aurora, Cobalt, Rose, Mono, Sunset, Ice, and Noir |
|---|---|
| Core sections | 60 layouts across Hero, About, Experience, Projects, Skills, and Contact |
| Résumé | 7 layouts |
| Custom sections | 8 layouts |
- Rename, show or hide, reorder, and shuffle sections. Empty sections are hidden automatically.
- Preview desktop, tablet, and mobile while editing, with an adjustable editor and preview split.
- Upload hero and project images through signed Cloudinary uploads. Secrets stay on the server.
- Projects can have separate GitHub and live demo links. Skill-logo layouts fall back to text.
Versions per role
Create several named portfolios, for example one for backend roles and one for product engineering. Each has its own target role, its own content, its own choice and order of experience, projects, and skills, and its own URL and analytics. Editing one leaves the others untouched.
First-party analytics
Every published portfolio is counted automatically. There is nothing to install or connect.
| Reach | Views, unique visitors, engaged visitors, engagement rate |
|---|---|
| Actions | Résumé opens and clicks on contact, project, social, and custom links |
| Sources | Your tracked link’s name, or the referring site’s hostname such as github.com, plus device type |
| Time | Daily traffic over 7, 30, or 90 days |
| Comparison | All portfolios side by side |
Analytics never block the public page: if recording fails, the portfolio still loads normally. Site administrators also see aggregate product metrics such as sign-ups, publish rate, and time to first publish.
Tracked links
Browsers usually hide where a visit came from when the link is opened from an email app, a PDF résumé, or a chat app, so those visits would otherwise count as Direct. Tracked links fix that: each one adds ?via=<name> to your URL, and visits through it are labelled with that name in analytics.
- Copy them from the portfolio manager or right after you publish: LinkedIn, Résumé, Email, GitHub, X, or any name you type, such as a company you are applying to.
- The tag is removed from the address bar once the page loads, so a visitor who re-shares the page does not pass your tag along.
- A tag is only the name you chose. It says nothing about the visitor.
Analytics privacy
Analytics count visits. They are not built to identify the people behind them.
What is stored
Random visitor and session IDs, the event type, a fixed action target, referrer host, device type, portfolio ID, and time. A view is counted once per portfolio per session.
What is not stored
IP addresses, names, email addresses, résumé or profile text, project descriptions, custom-section names, or full referrer URLs. Browser Do Not Track is honoured. Signed-in creator events contain only a user ID, event type, optional portfolio key, and time.
Your data
Portfolio deletion
Deleting a portfolio removes its saved and published data, its own content, attached résumé, analytics events, and any uploaded images no other portfolio uses. Deleting your last portfolio also removes the shared workspace data.
Account deletion
The danger zone in your account permanently removes every portfolio, workspace data, published pages, uploaded Cloudinary images, analytics admin membership, and the sign-in account itself.
How publishing works
Editing and publishing are separate. Drafts live in your browser and your signed-in workspace; publishing copies a snapshot to the public route.
- DraftLocal draft and signed-in Supabase workspace
- PublishCreates an immutable public snapshot
- Public URL
/<username>/<portfolio>
Draft profile, experience, project, and skill rows are readable only by their owner under Supabase Row Level Security. Workspace saves run in a single Postgres transaction, and public pages read only the published snapshot.