mirror of
https://github.com/AmruthPillai/Reactive-Resume.git
synced 2026-07-24 17:03:55 +10:00
62f8270b3e
commit b2b0470a1d9267d042ec0ac66523c6635bf5b199
Author: Amruth Pillai <im.amruth@gmail.com>
Date: Tue May 19 13:13:38 2026 +0200
chore: update .gitignore to include .vite-hooks and modify pnpm-lock.yaml for dependencies
commit d28fadb5cd8706c874e616102878b4a394ec84c1
Author: Amruth Pillai <im.amruth@gmail.com>
Date: Tue May 19 13:08:04 2026 +0200
fix: remove timestamp conflict guard
commit c6998d9dbab19d09d3c8054feef1d2e4117555eb
Author: Amruth Pillai <im.amruth@gmail.com>
Date: Tue May 19 12:11:51 2026 +0200
chore(release): v5.1.5
commit f33d168711804880e1f12e88d24290aae16cc258
Author: Amruth Pillai <im.amruth@gmail.com>
Date: Tue May 19 11:58:35 2026 +0200
revert: compose.yml
commit d961e6535811a10c335525fb33a08d03e737278d
Author: Amruth Pillai <im.amruth@gmail.com>
Date: Tue May 19 11:58:08 2026 +0200
refactor(agent): replace 'revert' terminology with 'restore' for clarity, resolves #3086
commit 17f351171be218e33f01c469d95e4164d4c8dc57
Author: Amruth Pillai <im.amruth@gmail.com>
Date: Tue May 19 11:10:41 2026 +0200
refactor(pdf): simplify sidebar section filtering and update summary feature logic
commit d55179b9d76879e3204de185e8b53fadd0a107ed
Author: Amruth Pillai <im.amruth@gmail.com>
Date: Tue May 19 09:53:37 2026 +0200
chore: update pnpm-lock.yaml and turbo.json
commit 7cade6980e1a04352536bd44ef773f338c4ef599
Author: Amruth Pillai <im.amruth@gmail.com>
Date: Tue May 19 09:38:30 2026 +0200
fix(polyfill): add tested polyfill for Map Upsert methods
commit 26d175bb9c53d93225d1e907678445252c13d660
Merge: 1cf33dc6c 5b1297fa2
Author: Amruth Pillai <im.amruth@gmail.com>
Date: Tue May 19 09:23:29 2026 +0200
Merge remote-tracking branch 'origin/main' into feat/explore-hono-orpc-migration
# Conflicts:
# packages/api/src/services/agent-url.ts
# packages/runtime-externals/package.json
commit 1cf33dc6c9d81735730ad656e16dab6501c6d6a1
Author: Amruth Pillai <im.amruth@gmail.com>
Date: Tue May 19 09:22:12 2026 +0200
chore: preserve branch changes before main sync
commit b380a4b00fdbcdd81ff4f8ef72b330fd027ccda5
Author: Amruth Pillai <im.amruth@gmail.com>
Date: Mon May 18 07:50:28 2026 +0200
chore: lot of fixes for monorepo migration
commit 8fcf0ec64e1c29572ebaff494338368bfcf75760
Author: Amruth Pillai <im.amruth@gmail.com>
Date: Fri May 15 13:57:17 2026 +0200
chore: update knip version and refine web app routing with new SEO endpoints
commit 234e68086ff15610a93877354c98e2c020364533
Author: Amruth Pillai <im.amruth@gmail.com>
Date: Fri May 15 12:10:06 2026 +0200
refactor(auth): update OAuth routes to include API prefix and remove unused schema endpoint
commit 91c84b9a8496b0ce21d71cae9f8b2a027638c9ac
Author: Amruth Pillai <im.amruth@gmail.com>
Date: Fri May 15 11:54:29 2026 +0200
chore: update dependencies and enhance PWA metadata in web app
commit 150117d4a5a9dd6cd92c64891aad8cae90f6a7af
Author: Amruth Pillai <im.amruth@gmail.com>
Date: Fri May 15 11:12:35 2026 +0200
docs: revise manifest-only pwa testing scope
commit 6b939a55661aec9dd8122b184e4b60a5c7325fb5
Author: Amruth Pillai <im.amruth@gmail.com>
Date: Fri May 15 11:11:33 2026 +0200
docs: add manifest-only pwa design
commit 1422e1fc96c400948b273210a1067251087d15d4
Author: Amruth Pillai <im.amruth@gmail.com>
Date: Fri May 15 11:05:04 2026 +0200
chore(dev): simplify server proxy config
commit bc2ff5a9f6fda41e6c40333c8f163aa23a6c5e48
Author: Amruth Pillai <im.amruth@gmail.com>
Date: Fri May 15 11:04:50 2026 +0200
docs: add unsafe oauth redirect plan
commit 445359ebe9b96c1515bf1c4c3f73ba8a8448ec12
Author: Amruth Pillai <im.amruth@gmail.com>
Date: Fri May 15 11:04:34 2026 +0200
feat(auth): add unsafe oauth redirect flag
commit 73fffdd24598e56b2793f7657919bc794835892e
Author: Amruth Pillai <im.amruth@gmail.com>
Date: Fri May 15 10:55:02 2026 +0200
docs: design unsafe oauth redirect flag
commit c0066aa19c15fc8a4c8e5179ed49889c117519f4
Author: Amruth Pillai <im.amruth@gmail.com>
Date: Fri May 15 10:22:04 2026 +0200
chore: update translation source paths
commit 9033da082418d252aafd6c2eed72f71f014be3d9
Author: Amruth Pillai <im.amruth@gmail.com>
Date: Fri May 15 10:09:25 2026 +0200
refactor(arch): react spa + hono migration
commit 6f27936c11bda895977dc63ee550c3346d4ce24b
Author: Amruth Pillai <im.amruth@gmail.com>
Date: Fri May 15 01:10:47 2026 +0200
docs: add docker nightly tagging design
commit ecc1fd9a88a0ee1dca2f1977dfc17f74527fe1da
Author: Amruth Pillai <im.amruth@gmail.com>
Date: Thu May 14 20:05:44 2026 +0200
feat: migrate to hono spa server
233 lines
8.9 KiB
Plaintext
233 lines
8.9 KiB
Plaintext
---
|
|
title: "Sharing your resume publicly"
|
|
description: "Learn how to share your resume via a public URL, track public engagement, and optionally protect your resume with a password."
|
|
---
|
|
|
|
Reactive Resume lets you share your resume via a **public URL** that anyone can access. When you make your resume public, it becomes available at a unique link that you can share with human recipients such as recruiters, collaborators, or portfolio visitors. Public resume URLs are not search-indexed by default.
|
|
|
|
## Key benefits of public sharing
|
|
|
|
<CardGroup cols={2}>
|
|
<Card title="Always up-to-date" icon="arrows-rotate">
|
|
Viewers always see the latest version of your resume. No need to send new files when you make updates.
|
|
</Card>
|
|
<Card title="Track engagement" icon="chart-line">
|
|
See public view counters in the builder.
|
|
</Card>
|
|
<Card title="Password protection" icon="lock">
|
|
Optionally require a password so only people you trust can access your resume.
|
|
</Card>
|
|
<Card title="Easy to share" icon="share">
|
|
A simple URL that works anywhere—email signatures, LinkedIn, portfolios, job applications.
|
|
</Card>
|
|
</CardGroup>
|
|
|
|
## How to enable public sharing
|
|
|
|
<Steps>
|
|
<Step title="Open your resume in the builder">
|
|
Navigate to your resume in the resume builder.
|
|
</Step>
|
|
|
|
<Step title="Go to the Sharing section">In the **right sidebar**, select **Sharing**.</Step>
|
|
|
|
<Step title="Toggle 'Allow Public Access'">
|
|
Turn on the **Allow Public Access** switch. Once enabled, your resume will be accessible via its public URL.
|
|
|
|
<Frame caption="Sharing section in the resume builder">
|
|
<img
|
|
src="/images/guides/sharing-your-resume-publicly/screenshot-1.webp"
|
|
alt="Sharing section showing the public access control"
|
|
/>
|
|
</Frame>
|
|
</Step>
|
|
|
|
<Step title="Copy your public URL">
|
|
Your public URL is displayed below the toggle. It follows this format:
|
|
|
|
```
|
|
https://rxresu.me/{username}/{slug}
|
|
```
|
|
|
|
Click the **copy** button to copy the URL to your clipboard.
|
|
|
|
</Step>
|
|
</Steps>
|
|
|
|
<Tip>
|
|
The `{slug}` is the unique, URL-safe name you assign to your resume when you create it. If you want to change your
|
|
slug, go to the dashboard, right-click your resume card, and choose "Update" to edit its details.
|
|
</Tip>
|
|
|
|
## How the public URL works
|
|
|
|
When someone visits your public resume URL:
|
|
|
|
1. **They see the live version** - The page renders your current resume data with all your latest changes
|
|
2. **No account required** - Visitors don't need a Reactive Resume account to view or download your resume
|
|
3. **They can download a PDF** - Visitors can use the download button on the public page
|
|
4. **Views are tracked** - Visits are counted in your resume statistics (see below)
|
|
|
|
<Info>
|
|
Changes you make in the builder are reflected immediately on the public URL. There's no separate "publish" step—your
|
|
public resume is always in sync. Treat the link as something you send to people directly, not as a search profile page.
|
|
</Info>
|
|
|
|
## Tracking public engagement
|
|
|
|
When your resume is public, Reactive Resume tracks public views. This helps you understand whether people are opening the link you shared.
|
|
|
|
### Where to find statistics
|
|
|
|
In the resume builder, open the **right sidebar** and select **Statistics**.
|
|
|
|
You'll see public view information such as:
|
|
|
|
| Metric | Description |
|
|
| ------------------- | ---------------------------------------------------------------- |
|
|
| **Views** | Number of times your public resume page was visited |
|
|
| **Last viewed** | The date when your resume was last viewed |
|
|
|
|
<Info>
|
|
Statistics are only shown after public sharing is enabled. If you turn off public access, existing stats are
|
|
preserved.
|
|
</Info>
|
|
|
|
### What counts as a view?
|
|
|
|
A view is counted each time someone loads your public resume page. This includes:
|
|
|
|
- Direct visits to your public URL
|
|
- Clicks from links you've shared
|
|
|
|
Owner self-visits while you are signed in to your account are not included in the view statistics.
|
|
|
|
<Note>
|
|
Only **you** can see your resume's view statistics. Visitors to your public URL cannot see how many views your resume
|
|
has.
|
|
</Note>
|
|
|
|
## Password protecting your resume
|
|
|
|
If you want to share your resume with specific people but keep it private from the general public, you can add password protection.
|
|
|
|
When password protection is enabled:
|
|
|
|
- Visitors must enter the correct password to view your resume
|
|
- The password prompt appears before any resume content is shown
|
|
- You can share the password separately with trusted individuals
|
|
|
|
### How to set a password
|
|
|
|
<Steps>
|
|
<Step title="Enable public access">
|
|
First, make sure **Allow Public Access** is turned on in the **Sharing** section.
|
|
</Step>
|
|
|
|
<Step title="Click Set Password">Below the public URL, click **Set Password**.</Step>
|
|
|
|
<Step title="Enter your password">
|
|
Type a password (6-64 characters) and confirm. This password will be required to view your resume.
|
|
</Step>
|
|
|
|
<Step title="Share the password separately">
|
|
Share the password with your intended audience through a secure channel (e.g., direct message, email).
|
|
</Step>
|
|
</Steps>
|
|
|
|
<Warning>
|
|
Choose a password you're comfortable sharing. Anyone with the password can view and download your resume.
|
|
</Warning>
|
|
|
|
### How to remove password protection
|
|
|
|
If you no longer need password protection:
|
|
|
|
1. Go to the **Sharing** section in the right sidebar
|
|
2. Click **Remove Password**
|
|
3. Confirm the action
|
|
|
|
Your resume will become accessible to anyone with the public URL.
|
|
|
|
## Use cases for public sharing
|
|
|
|
<AccordionGroup>
|
|
<Accordion title="LinkedIn profile" icon="linkedin">
|
|
Add your public resume URL to your LinkedIn profile's **Featured** section or **Contact Info**. Recruiters can view your detailed resume directly.
|
|
</Accordion>
|
|
|
|
<Accordion title="Email signature" icon="envelope">
|
|
Include your resume link in your email signature. Anyone you correspond with can quickly access your resume.
|
|
</Accordion>
|
|
|
|
<Accordion title="Portfolio website" icon="globe">
|
|
Embed or link to your resume from your personal website. The link always shows your latest resume.
|
|
</Accordion>
|
|
|
|
<Accordion title="Job applications" icon="briefcase">
|
|
Some applications accept a link to your resume, while others require a file upload. Use the public URL when a link is
|
|
accepted, and export a PDF when an upload is required.
|
|
</Accordion>
|
|
|
|
<Accordion title="Networking events" icon="users">
|
|
Share your resume URL via QR code or NFC. Update your resume before the event and everyone gets the latest version.
|
|
</Accordion>
|
|
|
|
<Accordion title="Confidential job search" icon="lock">
|
|
Use password protection to share your resume only with specific recruiters while keeping it hidden from your current employer.
|
|
</Accordion>
|
|
</AccordionGroup>
|
|
|
|
## Turning off public access
|
|
|
|
To make your resume private again:
|
|
|
|
1. Go to the **Sharing** section in the right sidebar
|
|
2. Turn off the **Allow Public Access** switch
|
|
|
|
When public access is disabled:
|
|
|
|
- Your public URL returns a "not found" error
|
|
- Existing links stop working immediately
|
|
- Your statistics are preserved (they'll resume if you re-enable public access)
|
|
- Password protection settings are preserved
|
|
|
|
<Tip>
|
|
If you only want to temporarily hide your resume, consider using password protection instead of disabling public
|
|
access entirely. This way, your URL remains active for people who have the password.
|
|
</Tip>
|
|
|
|
## Copying the URL from the builder dock
|
|
|
|
The builder dock includes a **Copy URL** shortcut. It copies the same public URL shown in the **Sharing** section.
|
|
|
|
<Warning>
|
|
Copying the URL does not enable public access. Turn on **Allow Public Access** in the **Sharing** section before sending
|
|
the link to someone else.
|
|
</Warning>
|
|
|
|
## Frequently asked questions
|
|
|
|
<AccordionGroup>
|
|
<Accordion title="Can I customize my public URL?">
|
|
Yes! The URL is based on your **username** and the resume's **slug**. You can change the slug in the **Update Resume** dialog. To open it, right-click on your resume card in the dashboard and select "Update". The username is set in your account settings.
|
|
</Accordion>
|
|
|
|
<Accordion title="Are public resumes meant to be search-indexed pages?">
|
|
No. By default, public resume URLs are meant for human recipients who receive the link from you, not as search profile
|
|
pages. If you want tighter access control, use password protection or keep your resume private.
|
|
</Accordion>
|
|
|
|
<Accordion title="Do views from my own visits count?">
|
|
No. If you are signed in as the owner, your own visits are excluded from the view statistics.
|
|
</Accordion>
|
|
|
|
<Accordion title="Can I see who viewed my resume?">
|
|
No, Reactive Resume tracks public view counts, not the identity of visitors. This protects visitor privacy.
|
|
</Accordion>
|
|
|
|
<Accordion title="What happens if I change my username?">
|
|
Your public URL will change to reflect the new username. Old URLs will stop working immediately. You might need to update any links you've shared.
|
|
</Accordion>
|
|
</AccordionGroup>
|