mirror of
https://github.com/AmruthPillai/Reactive-Resume.git
synced 2026-10-03 10:13:47 +10:00
chore(copy): rewrite marketing, app, and docs copy to read less AI-generated
Rewrites the landing page, in-app microcopy, and public docs, then fixes what the rewrite exposed: stale template counts, a broken quickstart anchor, out-of-sync FAQ structured data, dead error-hint branches in the MCP tools, and wrong-sense translations across all 53 locales. Adds GLOSSARY.md so translators get the right sense of the ambiguous UI terms.
This commit is contained in:
Amruth Pillai
@@ -328,7 +328,7 @@ When you copy a stylesheet to another resume, semantic section types, placements
|
||||
starting point. Exact IDs and template parts are intentionally specific to a resume or template.
|
||||
|
||||
1. Select **Copy stylesheet** in the source resume.
|
||||
2. Open **Design -> Custom Styles** in the destination resume.
|
||||
2. Open **Design → Custom Styles** in the destination resume.
|
||||
3. Paste the stylesheet and review any warnings.
|
||||
4. Replace or remove exact IDs and template-part rules that do not apply.
|
||||
5. Wait for **Valid**, then compare the preview and exported PDF.
|
||||
|
||||
@@ -807,7 +807,7 @@ rss: true
|
||||
- Added the new **Meowth** resume template (compact ATS-friendly layout with an inline three-column entry header), thanks to [@JamesGoslings](https://github.com/JamesGoslings). [#2923](https://github.com/amruthpillai/reactive-resume/pull/2923)
|
||||
- Added support for custom icon colors on section items, thanks to [@Ruzenie](https://github.com/Ruzenie). [#2928](https://github.com/amruthpillai/reactive-resume/pull/2928)
|
||||
- Improved account-related email UX with better templates for password reset and email verification. [b87f2007](https://github.com/amruthpillai/reactive-resume/commit/b87f2007)
|
||||
- Consolidated separate settings pages into a single **Integrations** page for a more streamlined configuration flow. [5d8126d4](https://github.com/amruthpillai/reactive-resume/commit/5d8126d4)
|
||||
- Consolidated separate settings pages into a single **Integrations** page. [5d8126d4](https://github.com/amruthpillai/reactive-resume/commit/5d8126d4)
|
||||
|
||||
## Fixes
|
||||
- Added a targeted Chinese localization fix for the `Skills` section title (`zh-CN`). [#2931](https://github.com/amruthpillai/reactive-resume/pull/2931)
|
||||
@@ -913,7 +913,7 @@ rss: true
|
||||
- Fixed the "Tailor Resume" button being incorrectly disabled when AI is not configured — the dialog already supports plain resume duplication as a fallback.
|
||||
- Fixed the tailor resume flow to open the resume builder in a new tab while keeping the job listing open for reference, instead of navigating away and auto-opening the application page.
|
||||
- Apply option links in the job detail sheet are now validated before rendering, preventing malformed or potentially unsafe URLs.
|
||||
- Improved job card loading skeletons to match the actual card layout (logo, title, badges) for a smoother loading experience.
|
||||
- Improved job card loading skeletons to match the actual card layout (logo, title, badges).
|
||||
- Centered the "Configure Job Search" empty state on the page.
|
||||
- Extracted the `JobCard` component into its own file for better code organization.
|
||||
|
||||
@@ -974,7 +974,7 @@ rss: true
|
||||
## Fixes
|
||||
- Printer endpoint now resolves to IP when using chromedp, improving compatibility with proxied deployments.
|
||||
- Switched OpenAI integration to `chat/completions` for resume import and AI features.
|
||||
- AI PDF/DOCX resume parsing is now more robust via direct file send (multimodal input).
|
||||
- AI PDF/DOCX resume parsing is now more reliable via direct file send (multimodal input).
|
||||
- Resume import normalization hardened: section defaults merged, required fields enforced, missing IDs/flags autogenerated.
|
||||
- Fixed UI migration regressions (accordion behavior, button interaction, right sidebar scrollbar).
|
||||
- Fixed multi-page PDF crashes and Gemini API ingestion errors.
|
||||
@@ -1010,7 +1010,7 @@ rss: true
|
||||
## Features & Improvements
|
||||
- Added feature flag: `FLAG_DISABLE_IMAGE_PROCESSING` (allows disabling image processing site-wide).
|
||||
- Updated Discord invite link in the app and documentation.
|
||||
- Added comprehensive codebase and architecture documentation in `CLAUDE.md`.
|
||||
- Added codebase and architecture documentation in `CLAUDE.md`.
|
||||
- Synced latest translations from Crowdin (multiple language updates and additions).
|
||||
|
||||
## Maintenance & Other
|
||||
@@ -1136,7 +1136,7 @@ rss: true
|
||||
</Update>
|
||||
|
||||
<Update label="v5.0.0" description="22th January 2026">
|
||||
This release is a major overhaul of Reactive Resume. The app has been completely redesigned and rebuilt from scratch for a more intuitive, user-friendly experience.
|
||||
This release is a major overhaul of Reactive Resume. The app was redesigned and rebuilt from scratch.
|
||||
|
||||
**Highlights:**
|
||||
- 2 new resume templates: _Ditgar_ and _Lapras_
|
||||
@@ -1150,10 +1150,10 @@ This release is a major overhaul of Reactive Resume. The app has been completely
|
||||
- Resume import from PDF/DOCX (requires AI Integration)
|
||||
- Stronger infrastructure for better reliability and scalability
|
||||
- Drag-and-drop for moving items between sections and pages
|
||||
- Powerful new CSS Editor with autocompletion and highlighting
|
||||
- New CSS Editor with autocompletion and highlighting
|
||||
- Custom sections now support typed extension for finer control
|
||||
- Icon style selector for indicators (stars, circles, custom, etc.)
|
||||
- Sidebar width adjustment and full-width page support
|
||||
|
||||
And much more! Explore the new version and share your feedback via [contact](https://amruthpillai.com/#contact) or [GitHub issues](https://github.com/amruthpillai/reactive-resume/issues).
|
||||
That list is not exhaustive. Send feedback via [contact](https://amruthpillai.com/#contact) or [GitHub issues](https://github.com/amruthpillai/reactive-resume/issues).
|
||||
</Update>
|
||||
|
||||
@@ -1,9 +1,9 @@
|
||||
---
|
||||
title: Sponsors
|
||||
description: "Meet the individuals, companies, and open-source backers whose GitHub sponsorships fund ongoing development and hosting of Reactive Resume."
|
||||
description: "The sponsors whose support funds ongoing development and hosting of Reactive Resume."
|
||||
---
|
||||
|
||||
Reactive Resume stays free, open-source, and independent because companies choose to support the work behind it. Thank you to every sponsor who helps fund hosting, maintenance, and continued development for the community.
|
||||
Sponsors pay for hosting, maintenance, and ongoing development, which is what keeps Reactive Resume free and independent. Thank you to everyone who chips in.
|
||||
|
||||
## Atlas Cloud
|
||||
|
||||
@@ -11,7 +11,7 @@ Reactive Resume stays free, open-source, and independent because companies choos
|
||||
|
||||
[Atlas Cloud](https://www.atlascloud.ai/?utm_source=github&utm_medium=link&utm_campaign=reactive-resume) supports Reactive Resume as a project sponsor. Atlas Cloud provides a unified AI platform for developers, with access to hundreds of models for chat, image generation, video generation, media processing, and GPU cloud workloads through one API key, one endpoint, and one billing account.
|
||||
|
||||
Explore Atlas Cloud at [atlascloud.ai](https://www.atlascloud.ai/?utm_source=github&utm_medium=link&utm_campaign=reactive-resume).
|
||||
Learn more at [atlascloud.ai](https://www.atlascloud.ai/?utm_source=github&utm_medium=link&utm_campaign=reactive-resume).
|
||||
|
||||
## Sponsor Reactive Resume
|
||||
|
||||
|
||||
@@ -1,12 +1,11 @@
|
||||
---
|
||||
title: "Spotlight"
|
||||
description: "Discover articles, YouTube videos, tutorials, and social media posts about Reactive Resume shared by users, reviewers, and community members."
|
||||
description: "Articles, videos, tutorials, and social media posts about Reactive Resume, shared by the community."
|
||||
---
|
||||
|
||||
<Note>
|
||||
Have you created something that makes use of Reactive Resume, or spread the word about it in your own way? I'd love to
|
||||
feature it here! Send me an email at [hello@amruthpillai.com](mailto:hello@amruthpillai.com) and I'll make sure to add
|
||||
it to this page.
|
||||
Have you built something with Reactive Resume, or spread the word about it in your own way? I'd love to feature it
|
||||
here. Email me at [hello@amruthpillai.com](mailto:hello@amruthpillai.com) and I'll add it to this page.
|
||||
</Note>
|
||||
|
||||
---
|
||||
@@ -26,7 +25,7 @@ A collection of blog posts and articles written by the community about Reactive
|
||||
*/}
|
||||
</CardGroup>
|
||||
|
||||
<Info>No articles have been featured yet. Be the first to contribute!</Info>
|
||||
<Info>No articles have been featured yet.</Info>
|
||||
|
||||
---
|
||||
|
||||
@@ -45,11 +44,11 @@ Video tutorials, reviews, and walkthroughs created by the community.
|
||||
*/}
|
||||
</CardGroup>
|
||||
|
||||
<Info>No videos have been featured yet. Be the first to contribute!</Info>
|
||||
<Info>No videos have been featured yet.</Info>
|
||||
|
||||
---
|
||||
|
||||
## Social Media
|
||||
## Social media
|
||||
|
||||
Posts and threads from social media platforms sharing experiences with Reactive Resume.
|
||||
|
||||
@@ -64,4 +63,4 @@ Posts and threads from social media platforms sharing experiences with Reactive
|
||||
*/}
|
||||
</CardGroup>
|
||||
|
||||
<Info>No social media posts have been featured yet. Be the first to contribute!</Info>
|
||||
<Info>No social media posts have been featured yet.</Info>
|
||||
|
||||
@@ -3,9 +3,9 @@ title: "Reactive Resume vs Adobe Express"
|
||||
description: "Compare Reactive Resume and Adobe Express for resume templates, PDF export, visual editing, structured data, and self-hosting."
|
||||
---
|
||||
|
||||
Adobe Express is a better fit when you need broader document, image, and layout editing around a resume. Reactive Resume is a better fit when you want content held in resume-specific fields, with resume-focused exports and deployment choices.
|
||||
Adobe Express suits you when the resume sits inside broader document, image, and layout work. Reactive Resume keeps the content in resume-specific fields, with resume-focused exports and a choice of where the app runs.
|
||||
|
||||
Adobe Express offers a resume maker within a general creative editor. Reactive Resume is limited to the resume workflow: it organizes sections such as experience and education, renders them in a template, and keeps the same resume data available when you change layouts or create versions.
|
||||
Adobe Express has a resume maker inside a general creative editor. Reactive Resume only does resumes: it organizes sections such as experience and education, renders them in a template, and keeps the same data when you change layouts or create new versions.
|
||||
|
||||
## Quick comparison
|
||||
|
||||
@@ -18,29 +18,29 @@ Adobe Express offers a resume maker within a general creative editor. Reactive R
|
||||
| Deployment | Hosted use or self-hosting under an MIT license | Adobe-hosted service |
|
||||
| Free plan | Core hosted resume workflow has no premium tier | Free-plan features and asset access have defined limits |
|
||||
|
||||
Adobe Express says its resume maker includes customizable resume templates. Its broader editor can suit people who need to combine a resume with edited images or custom page layouts. Its [Free plan documentation](https://helpx.adobe.com/express/web/adobe-express-subscription/free.html) is the right place to check current feature and asset boundaries before relying on a particular tool.
|
||||
Adobe Express says its resume maker includes customizable resume templates. Its wider editor suits people who need to combine a resume with edited images or custom page layouts. Check its [Free plan documentation](https://helpx.adobe.com/express/web/adobe-express-subscription/free.html) for current feature and asset boundaries before you rely on a particular tool.
|
||||
|
||||
## Where Adobe Express is a better fit
|
||||
|
||||
Use Adobe Express when the resume is one part of a wider visual document workflow. Its editing tools can be useful for placing images, adjusting graphics, or making layouts that do not fit a dedicated resume template. It may also be a practical choice when you already use Adobe Express for related documents or visual content.
|
||||
Use Adobe Express when the resume is one part of a wider visual document. Its editing tools help with placing images, adjusting graphics, or building layouts that no resume template covers. It is also a practical choice when you already use Adobe Express for related documents or visual content.
|
||||
|
||||
The broader editor is the meaningful advantage here: it can handle work that is outside a resume builder's normal controls. Confirm the plan and content availability for the assets or features you need rather than assuming they are all included with a free account.
|
||||
The wider editor is the real advantage. It handles work that falls outside a resume builder's controls. Confirm plan and content availability for the assets or features you need instead of assuming a free account includes them all.
|
||||
|
||||
## Where Reactive Resume is a better fit
|
||||
|
||||
Use Reactive Resume when you want the work history and other resume sections to remain structured rather than arranged only as page elements. This can make it simpler to prepare targeted resume versions, switch templates, or keep a data backup alongside document exports. The [exporting guide](/guides/exporting-your-resume) covers PDF, DOCX, Markdown, and JSON exports.
|
||||
Use Reactive Resume when work history and other sections should stay structured rather than sit on the page as arranged elements. That makes it easier to prepare targeted versions, switch templates, or keep a data backup next to your document exports. The [exporting guide](/guides/exporting-your-resume) covers PDF, DOCX, Markdown, and JSON.
|
||||
|
||||
Reactive Resume also offers choices beyond the hosted app. The project is [open source](/use-cases/open-source-resume-builder), licensed under MIT, and supports [self-hosting](/use-cases/self-hosted-resume-builder). Those options matter only if you need them; for a single visual document, Adobe Express may be the more direct editor.
|
||||
There are also options beyond the hosted app. The project is [open source](/use-cases/open-source-resume-builder) under MIT and supports [self-hosting](/use-cases/self-hosted-resume-builder). Those only matter if you need them; for a single visual document, Adobe Express is the more direct editor.
|
||||
|
||||
## Which should you choose?
|
||||
|
||||
Choose Adobe Express when broad creative editing, visual assets, or a general document canvas are central to the task. Choose Reactive Resume when the resume itself is central and you prefer reusable structured fields, resume-specific controls, and multiple export formats.
|
||||
Choose Adobe Express when broad creative editing, visual assets, or a general document canvas are central to the task. Choose Reactive Resume when the resume itself is the task and you want reusable structured fields, resume-specific controls, and several export formats.
|
||||
|
||||
Both services can produce a PDF for sharing. The decision is largely about the editing model and whether you need a general creative workspace or a focused resume editor.
|
||||
Both services produce a PDF for sharing. The decision comes down to the editing model: a general creative workspace or a focused resume editor.
|
||||
|
||||
## Reactive Resume limitations in this comparison
|
||||
|
||||
Reactive Resume has a smaller visual asset library and does not provide a general-purpose design canvas. It is not the natural tool for extensive image work, graphic composition, or creating many non-resume document types. Adobe Express is better aligned with those needs.
|
||||
Reactive Resume has a smaller visual asset library and no general-purpose design canvas. It is the wrong tool for heavy image work, graphic composition, or producing many non-resume document types. Adobe Express fits those needs better.
|
||||
|
||||
## Sources
|
||||
|
||||
|
||||
@@ -3,9 +3,9 @@ title: "Reactive Resume vs Canva"
|
||||
description: "Compare Reactive Resume and Canva for free resume creation, visual control, exports, data portability, and self-hosting."
|
||||
---
|
||||
|
||||
Canva is a better fit for freeform visual composition and a broad design library. Reactive Resume is purpose-built around structured resume fields, reusable resume data, and the option to self-host.
|
||||
Canva suits freeform visual composition and gives you a broad design library. Reactive Resume is built around structured resume fields, reusable resume data, and the option to self-host.
|
||||
|
||||
Both tools can help you make a resume, but they begin from different models. Canva is a general visual-design product with resume templates among its design types. Reactive Resume is a resume editor: work history, education, skills, and other sections are stored as resume data, then rendered through a selected template.
|
||||
Both tools make resumes, but they start from different models. Canva is a general design product with resume templates among its design types. Reactive Resume is a resume editor: work history, education, skills, and other sections are stored as data, then rendered through the template you pick.
|
||||
|
||||
## Quick comparison
|
||||
|
||||
@@ -18,29 +18,29 @@ Both tools can help you make a resume, but they begin from different models. Can
|
||||
| Deployment | Hosted use or self-hosting under the MIT license | Canva-hosted service |
|
||||
| Plan boundary | The hosted core resume workflow has no premium tier | Some Canva content and features have plan-specific availability |
|
||||
|
||||
Reactive Resume supports [PDF, DOCX, Markdown, and JSON exports](/guides/exporting-your-resume). Its JSON format is useful when you want to retain the content and settings for another Reactive Resume resume. Canva's resume builder is part of a wider design environment, which can be more appropriate when the resume needs custom graphics, brand elements, or a layout that goes beyond resume-specific controls.
|
||||
Reactive Resume supports [PDF, DOCX, Markdown, and JSON exports](/guides/exporting-your-resume). Its JSON format holds the content and settings so you can reuse them in another Reactive Resume resume. Canva's resume builder is part of a wider design environment, which fits better when the resume needs custom graphics, brand elements, or a layout beyond resume-specific controls.
|
||||
|
||||
## Where Canva is a better fit
|
||||
|
||||
Choose Canva when visual composition is the main task. Its resume page points to a large collection of customizable templates, and its wider product includes tools for arranging text, images, and graphic elements. That is useful for a resume that needs to align with an existing portfolio, brand kit, or presentation style.
|
||||
Choose Canva when visual composition is the main task. Its resume page points to a large collection of customizable templates, and the wider product arranges text, images, and graphic elements. That helps when a resume has to match an existing portfolio, brand kit, or presentation style.
|
||||
|
||||
Canva can also be the more convenient choice when the same person is preparing related design materials, such as a portfolio cover, social graphic, or presentation. Check the availability and licensing details for the individual templates, elements, and features you select; the availability of a free Canva account does not mean every asset is included.
|
||||
Canva is also the convenient option when you are preparing related design material at the same time, such as a portfolio cover, a social graphic, or a presentation. Check availability and licensing for the individual templates, elements, and features you pick. A free Canva account does not mean every asset is included.
|
||||
|
||||
## Where Reactive Resume is a better fit
|
||||
|
||||
Choose Reactive Resume when the content should stay in recognizable resume fields and you expect to reuse it across versions. You can change a template without re-entering the underlying sections, adjust resume-specific layout settings, and keep exports in several document and data formats.
|
||||
Choose Reactive Resume when the content should stay in recognizable resume fields and you expect to reuse it across versions. You can change a template without re-entering the underlying sections, adjust resume layout settings, and export in several document and data formats.
|
||||
|
||||
It is also appropriate when infrastructure control matters. Reactive Resume is [MIT-licensed](/legal/license), its source is public, and it can be deployed on your own infrastructure. The [self-hosting guide](/self-hosting/docker) explains the Docker-based path; hosted use remains available when you do not want to run the service.
|
||||
It also fits when you care about infrastructure. Reactive Resume is [MIT-licensed](/legal/license), its source is public, and you can deploy it yourself. The [self-hosting guide](/self-hosting/docker) covers the Docker path, and hosted use stays available if you would rather not run the service.
|
||||
|
||||
## Which should you choose?
|
||||
|
||||
Use Canva if the resume is primarily a visual design project and you want a general canvas with a broad library of design assets. Use Reactive Resume if you want a dedicated resume workflow, portable resume data, and the option to run the software yourself.
|
||||
Use Canva if the resume is mainly a visual design project and you want a general canvas with a broad asset library. Use Reactive Resume if you want a dedicated resume workflow, portable resume data, and the option to run the software yourself.
|
||||
|
||||
For a typical application submission, either workflow can end with a PDF. The difference is whether you prefer to compose each page as a design or manage resume sections and template settings separately.
|
||||
For a typical application, either workflow ends in a PDF. The difference is whether you compose each page as a design or manage resume sections and template settings separately.
|
||||
|
||||
## Reactive Resume limitations in this comparison
|
||||
|
||||
Reactive Resume has a narrower design canvas. It does not aim to provide Canva's general-purpose composition tools or its broader asset library. If your resume depends on custom illustrations, extensive image editing, or unusual page composition, Canva may give you more direct control.
|
||||
Reactive Resume has a narrower design canvas. It does not try to match Canva's general composition tools or its asset library. If your resume depends on custom illustrations, heavy image editing, or unusual page composition, Canva gives you more direct control.
|
||||
|
||||
## Sources
|
||||
|
||||
|
||||
@@ -3,7 +3,7 @@ title: "Reactive Resume vs CareerCircle"
|
||||
description: "Compare Reactive Resume and CareerCircle by free PDF and Word exports, career resources, accounts, open source, and self-hosting."
|
||||
---
|
||||
|
||||
CareerCircle is a better fit when you want resume drafting alongside job listings, courses, and professional-development resources. Reactive Resume is a better fit when resume ownership, export formats, and self-hosting are the main concerns.
|
||||
CareerCircle puts resume drafting next to job listings, courses, and professional-development resources. Reactive Resume is a standalone resume tool built around resume ownership, export formats, and self-hosting.
|
||||
|
||||
## Quick comparison
|
||||
|
||||
@@ -15,17 +15,17 @@ CareerCircle is a better fit when you want resume drafting alongside job listing
|
||||
| Career services | Resume and application tools | Jobs, courses, and professional-development resources |
|
||||
| Account | An account stores resume versions | Sign-up is required to use the service |
|
||||
|
||||
CareerCircle documents PDF and Microsoft Word downloads from its resume builder. It also places staffing-expert guidance, job search, courses, and professional-development resources in the same service.
|
||||
CareerCircle documents PDF and Microsoft Word downloads from its resume builder. It puts staffing-expert guidance, job search, courses, and professional-development resources in the same service.
|
||||
|
||||
Reactive Resume supports [PDF, DOCX, Markdown, and JSON exports](/guides/exporting-your-resume), and its [dashboard](/guides/managing-resumes-from-the-dashboard) supports separate resume versions. Its source is public under the [MIT license](/legal/license), with a Docker self-hosting path.
|
||||
Reactive Resume supports [PDF, DOCX, Markdown, and JSON exports](/guides/exporting-your-resume), and its [dashboard](/guides/managing-resumes-from-the-dashboard) keeps separate resume versions. Its source is public under the [MIT license](/legal/license), with a Docker self-hosting path.
|
||||
|
||||
## Where CareerCircle is a better fit
|
||||
|
||||
Choose CareerCircle when you want the resume builder connected to job search, courses, and professional-development resources. Its staffing-expert guidance is also useful when you prefer help within that career-services workflow.
|
||||
Choose CareerCircle when you want the resume builder connected to job search, courses, and professional-development resources. Its staffing-expert guidance also helps if you prefer to get that advice inside the same career service.
|
||||
|
||||
## Where Reactive Resume is a better fit
|
||||
|
||||
Choose Reactive Resume when you want to keep multiple resume versions and export them in document or data formats. It is also an option when you want to run the software yourself; see the [self-hosting guide](/self-hosting/docker).
|
||||
Pick Reactive Resume to keep several resume versions and export them in document or data formats. You can also run the software yourself; see the [self-hosting guide](/self-hosting/docker).
|
||||
|
||||
## Which should you choose?
|
||||
|
||||
@@ -33,7 +33,7 @@ Choose CareerCircle for a sign-up-based career service with its resume builder,
|
||||
|
||||
## Reactive Resume limitations in this comparison
|
||||
|
||||
Reactive Resume does not provide CareerCircle's broader course, job, and community services. If those resources should live alongside the resume workflow, CareerCircle is the closer fit.
|
||||
Reactive Resume has none of CareerCircle's course, job, and community services. If those resources should sit alongside the resume workflow, CareerCircle is the closer fit.
|
||||
|
||||
## Sources
|
||||
|
||||
|
||||
@@ -3,7 +3,7 @@ title: "Reactive Resume vs Freesumes"
|
||||
description: "Compare Reactive Resume and Freesumes by no-account use, PDF export, templates, saved resume management, privacy, and self-hosting."
|
||||
---
|
||||
|
||||
Freesumes is a better fit when you want to make one resume in a browser session without an account or card. Reactive Resume is a better fit when you want saved resume management, multiple export formats, sharing, or automation.
|
||||
Freesumes is built for making one resume in a browser session, without an account or a card. Reactive Resume saves your resumes instead, and adds several export formats, sharing, and automation.
|
||||
|
||||
## Quick comparison
|
||||
|
||||
@@ -15,25 +15,25 @@ Freesumes is a better fit when you want to make one resume in a browser session
|
||||
| Other template formats | DOCX, Markdown, and JSON exports | Separate Word and Google Docs templates |
|
||||
| Data handling | Resumes persist in the account and server storage | Builder data is wiped when the tab is refreshed or closed |
|
||||
|
||||
Freesumes documents a no-account, no-card builder with six templates and PDF output. It separately provides Word and Google Docs templates. Its builder says it does not collect or store entered information, and that data is wiped when the browser tab is refreshed or closed.
|
||||
Freesumes documents a no-account, no-card builder with six templates and PDF output. It offers Word and Google Docs templates separately. Its builder says it does not collect or store what you enter, and that the data is wiped when you refresh or close the browser tab.
|
||||
|
||||
Reactive Resume stores and manages resume versions in its [dashboard](/guides/managing-resumes-from-the-dashboard), with [PDF, DOCX, Markdown, and JSON exports](/guides/exporting-your-resume). It can also support [sharing resumes](/use-cases/export-and-share-resumes) and API or MCP automation.
|
||||
Reactive Resume keeps resume versions in its [dashboard](/guides/managing-resumes-from-the-dashboard), with [PDF, DOCX, Markdown, and JSON exports](/guides/exporting-your-resume). It can also [share resumes](/use-cases/export-and-share-resumes) and run API or MCP automation.
|
||||
|
||||
## Where Freesumes is a better fit
|
||||
|
||||
Choose Freesumes when you want a one-off browser session without an account or card and accept that the builder data disappears on refresh or close. Its separate Word and Google Docs templates also fit an editor-first workflow.
|
||||
Choose Freesumes for a one-off browser session without an account or card, if you accept that the builder data disappears on refresh or close. Its separate Word and Google Docs templates also suit an editor-first workflow.
|
||||
|
||||
## Where Reactive Resume is a better fit
|
||||
|
||||
Choose Reactive Resume when you want to keep resume versions, share them, or export them in several formats. It also provides self-hosting; see the [Docker guide](/self-hosting/docker).
|
||||
Reactive Resume holds on to your resume versions so you can share them or export them in several formats. It can also be self-hosted; see the [Docker guide](/self-hosting/docker).
|
||||
|
||||
## Which should you choose?
|
||||
|
||||
Choose Freesumes for a no-account, browser-session PDF workflow or its separate Word and Google Docs templates. Choose Reactive Resume when you want saved resume management, sharing, multiple export formats, or automation.
|
||||
Choose Freesumes for a no-account, browser-session PDF workflow or its separate Word and Google Docs templates. Choose Reactive Resume when you want saved resume management, sharing, several export formats, or automation.
|
||||
|
||||
## Reactive Resume limitations in this comparison
|
||||
|
||||
Reactive Resume requires an account and uses server-backed persistence. That is a limitation for someone who wants a one-off local browser session where entered builder data is removed on refresh or close.
|
||||
Reactive Resume needs an account and stores resumes on the server. That is a drawback if you want a one-off local browser session where the builder data disappears on refresh or close.
|
||||
|
||||
## Sources
|
||||
|
||||
|
||||
@@ -3,7 +3,7 @@ title: "Reactive Resume vs Jobscan"
|
||||
description: "Compare Reactive Resume and Jobscan by free PDF creation, ATS parse checking, job matching, exports, open source, and automation."
|
||||
---
|
||||
|
||||
Jobscan is a better fit when your workflow centers on its hosted resume scanner and its match-rate score against a job description. Reactive Resume is a better fit when you want structured resume data, multiple export formats, open-source deployment, and API or MCP automation — with a free ATS checker that measures how well your file parses rather than predicting an outcome.
|
||||
Jobscan makes sense when your workflow revolves around its hosted resume scanner and the match rate it reports against a job description. Reactive Resume gives you structured resume data, several export formats, open-source deployment, and API or MCP automation, plus a free ATS checker that measures how well your file parses rather than predicting an outcome.
|
||||
|
||||
## Quick comparison
|
||||
|
||||
@@ -14,25 +14,25 @@ Jobscan is a better fit when your workflow centers on its hosted resume scanner
|
||||
| Analysis | Built-in ATS checker, free: a parse-quality score, a pass/warn/fail checklist, and optional job-description keyword coverage, all computed in your browser | Separate resume scanner producing a match rate against a job description |
|
||||
| Automation | Authenticated API and MCP workflows | Separate scanner workflow |
|
||||
|
||||
Jobscan's builder documents a free PDF-creation workflow, LinkedIn import, and nine ATS-friendly templates. Its separate scanner describes resume scoring, formatting checks, and job-listing analysis as product features. Those features are vendor positioning and do not guarantee ATS handling or hiring outcomes.
|
||||
Jobscan's builder documents a free PDF-creation workflow, LinkedIn import, and nine ATS-friendly templates. Its separate scanner lists resume scoring, formatting checks, and job-listing analysis as product features. Those are vendor claims about the product, not guarantees about ATS handling or hiring outcomes.
|
||||
|
||||
Reactive Resume exports PDF, DOCX, Markdown, and JSON and supports authenticated automation through its API and MCP server. Its [ATS checker](/guides/using-the-ats-checker) scores how faithfully software can extract your PDF and lists which of a posting's terms already appear in it. It deliberately does not report a match rate or predict a rejection, because neither is knowable from the file.
|
||||
Reactive Resume exports PDF, DOCX, Markdown, and JSON, and it supports authenticated automation through its API and MCP server. Its [ATS checker](/guides/using-the-ats-checker) scores how faithfully software can extract your PDF and lists which of a posting's terms already appear in it. It reports no match rate and predicts no rejection, because neither is knowable from the file.
|
||||
|
||||
## Where Jobscan is a better fit
|
||||
|
||||
Choose Jobscan when you want a match-rate score against a specific posting, and its associated recommendations, as the center of your review process. Its scanner is a paid, hosted product built around that number.
|
||||
Choose Jobscan when a match rate against a specific posting, and the recommendations that come with it, drive your review process. Its scanner is a paid, hosted product built around that number.
|
||||
|
||||
## Where Reactive Resume is a better fit
|
||||
|
||||
Choose Reactive Resume when you want to own structured resume data, choose a template, export in several formats, or automate authenticated resume workflows. Its API and MCP server can support scripts, integrations, and compatible AI clients.
|
||||
Reactive Resume is the better choice when you want to own structured resume data, pick a template, export in several formats, or automate authenticated resume workflows. Its API and MCP server support scripts, integrations, and compatible AI clients.
|
||||
|
||||
## Which should you choose?
|
||||
|
||||
Choose Jobscan when a match-rate score against each posting is your primary need. Choose Reactive Resume when the builder, data portability, self-hosting, and automation are primary, and a parse-quality check that runs free and locally covers the rest.
|
||||
Choose Jobscan when a match rate against each posting is your primary need. Choose Reactive Resume when the builder, data portability, self-hosting, and automation come first, and a free local parse-quality check covers the rest.
|
||||
|
||||
## Reactive Resume limitations in this comparison
|
||||
|
||||
Reactive Resume's ATS checker measures file properties: whether the text extracts, in what order, and whether your facts survive. It does not produce a match rate against a posting, and it does not claim to predict a rejection. If a documented match-rate score is what you want, Jobscan is the more direct fit.
|
||||
Reactive Resume's ATS checker measures file properties: whether the text extracts, in what order, and whether your facts survive. It produces no match rate against a posting and makes no claim about predicting a rejection. If you want a documented match-rate score, Jobscan is the more direct fit.
|
||||
|
||||
## Sources
|
||||
|
||||
|
||||
@@ -3,7 +3,7 @@ title: "Reactive Resume vs Kickresume"
|
||||
description: "Compare Reactive Resume and Kickresume by free downloads, AI writing, content examples, templates, provider choice, and self-hosting."
|
||||
---
|
||||
|
||||
Kickresume is a better fit when you want AI writing, imports, examples, and related career documents in one guided product. Reactive Resume is a better fit when you want an open-source resume editor with a core hosted workflow that has no premium tier, optional provider-configured AI, and self-hosting.
|
||||
Kickresume bundles AI writing, imports, examples, and related career documents into one guided product. Reactive Resume is an open-source editor whose core hosted workflow has no premium tier, with optional provider-configured AI and self-hosting.
|
||||
|
||||
## Quick comparison
|
||||
|
||||
@@ -15,17 +15,17 @@ Kickresume is a better fit when you want AI writing, imports, examples, and rela
|
||||
| Documents | Resume-focused exports and versions | Resumes, cover letters, websites, and related tools |
|
||||
| Free plan | Core hosted workflow has no premium tier | Unlimited documents and downloads when using free customization options |
|
||||
|
||||
Kickresume's help center documents AI writing, LinkedIn import, PDF import, examples, guides, and cover-letter and website workflows. Its free-plan FAQ says documents and downloads are unlimited when you use free customization options; premium-marked options are outside that boundary.
|
||||
Kickresume's help center documents AI writing, LinkedIn import, PDF import, examples, guides, and cover-letter and website workflows. Its free-plan FAQ says documents and downloads are unlimited when you use free customization options; premium-marked options fall outside that.
|
||||
|
||||
Reactive Resume can export PDF, DOCX, Markdown, and JSON. Its AI features remain optional: you connect a provider, model, endpoint when needed, and API key. Provider use may incur separate provider costs.
|
||||
Reactive Resume exports PDF, DOCX, Markdown, and JSON. Its AI stays optional: you connect a provider, a model, an endpoint when one is needed, and an API key. The provider may charge you separately.
|
||||
|
||||
## Where Kickresume is a better fit
|
||||
|
||||
Choose Kickresume when you want prewritten examples, guided prompts, integrated AI writing, or related career documents in one interface. Its import options can also be helpful when starting from a LinkedIn profile or an existing PDF or DOCX resume.
|
||||
Choose Kickresume when you want prewritten examples, guided prompts, built-in AI writing, or related career documents in one interface. Its import options also help when you are starting from a LinkedIn profile or an existing PDF or DOCX resume.
|
||||
|
||||
## Where Reactive Resume is a better fit
|
||||
|
||||
Choose Reactive Resume when you want to keep AI optional and select the provider that handles your resume content. It is open source, can be self-hosted, and offers API and MCP workflows for authenticated automation.
|
||||
Reactive Resume is the better choice when you want AI to stay optional and want to pick the provider that handles your resume content. It is open source, can be self-hosted, and has API and MCP workflows for authenticated automation.
|
||||
|
||||
## Which should you choose?
|
||||
|
||||
@@ -33,7 +33,7 @@ Choose Kickresume for a bundled writing, examples, and career-document workflow.
|
||||
|
||||
## Reactive Resume limitations in this comparison
|
||||
|
||||
Reactive Resume has a smaller built-in content-example library and requires provider setup before AI features can be used. It does not bundle Kickresume's wider guided career-document workflow.
|
||||
Reactive Resume has a smaller built-in library of content examples and needs provider setup before its AI features work. It does not bundle Kickresume's wider guided career-document workflow.
|
||||
|
||||
## Sources
|
||||
|
||||
|
||||
@@ -3,7 +3,7 @@ title: "Reactive Resume vs LiveCareer"
|
||||
description: "Compare Reactive Resume and LiveCareer by free downloads, guided content, resume checks, templates, open source, and self-hosting."
|
||||
---
|
||||
|
||||
LiveCareer is a better fit when you want ready-made content, spell-checking, writing tips, and ResumeCheck in the drafting workflow. Reactive Resume is a better fit when PDF or DOCX export and source access matter more than a built-in checker.
|
||||
LiveCareer gives you ready-made content, spell-checking, writing tips, and ResumeCheck while you draft. Reactive Resume has no built-in checker; it gives you PDF or DOCX export and access to the source.
|
||||
|
||||
## Quick comparison
|
||||
|
||||
@@ -14,25 +14,25 @@ LiveCareer is a better fit when you want ready-made content, spell-checking, wri
|
||||
| Drafting support | Direct editing and optional AI | Ready-made content, spell-checking, and writing tips |
|
||||
| Resume review | No native checker product | ResumeCheck identifies common issues |
|
||||
|
||||
LiveCareer documents TXT as the free-builder download format. Its premium access documents unlimited PDF and Word downloads. The product also documents ready-made content, spell-checking, writing tips, and ResumeCheck.
|
||||
LiveCareer documents TXT as the free builder's download format, and unlimited PDF and Word downloads under premium access. The product also documents ready-made content, spell-checking, writing tips, and ResumeCheck.
|
||||
|
||||
Reactive Resume supports [PDF, DOCX, Markdown, and JSON exports](/guides/exporting-your-resume). Its [AI workflow](/guides/using-ai) is optional and provider-configured, while its source is public under the [MIT license](/legal/license).
|
||||
Reactive Resume supports [PDF, DOCX, Markdown, and JSON exports](/guides/exporting-your-resume). Its [AI workflow](/guides/using-ai) is optional and provider-configured, and its source is public under the [MIT license](/legal/license).
|
||||
|
||||
## Where LiveCareer is a better fit
|
||||
|
||||
Choose LiveCareer when ready-made content, spelling checks, writing tips, and a resume checker are important during drafting. Those tools are useful when you want review features in the same product as the builder.
|
||||
Choose LiveCareer when ready-made content, spelling checks, writing tips, and a resume checker matter while you draft. Those tools help if you want the review features in the same product as the builder.
|
||||
|
||||
## Where Reactive Resume is a better fit
|
||||
|
||||
Choose Reactive Resume when PDF or DOCX output, reusable resume data, or source access are the priority. It can also be self-hosted; the [Docker guide](/self-hosting/docker) covers that deployment path.
|
||||
Use Reactive Resume when PDF or DOCX output, reusable resume data, or source access come first. You can also self-host it; the [Docker guide](/self-hosting/docker) covers that path.
|
||||
|
||||
## Which should you choose?
|
||||
|
||||
Choose LiveCareer when its guided content and checker features fit your drafting process and TXT output is sufficient without premium access. Choose Reactive Resume when you want PDF or DOCX output and a self-hosting option.
|
||||
Choose LiveCareer when its guided content and checker suit how you draft and TXT output is enough without premium access. Choose Reactive Resume when you want PDF or DOCX output and a self-hosting option.
|
||||
|
||||
## Reactive Resume limitations in this comparison
|
||||
|
||||
Reactive Resume has a smaller guided-content and checker surface. It does not include LiveCareer's ready-made content, spell-checking, writing tips, or native ResumeCheck product.
|
||||
Reactive Resume has a smaller guided-content and checker surface. It has no equivalent to LiveCareer's ready-made content, spell-checking, writing tips, or its ResumeCheck product.
|
||||
|
||||
## Sources
|
||||
|
||||
|
||||
@@ -3,7 +3,7 @@ title: "Reactive Resume vs MyPerfectResume"
|
||||
description: "Compare Reactive Resume and MyPerfectResume by free downloads, writing guidance, templates, AI, open source, and self-hosting."
|
||||
---
|
||||
|
||||
MyPerfectResume is geared toward guided writing: it offers step-by-step prompts, expert-written content suggestions, and a resume checker. Reactive Resume is an open-source resume editor whose core hosted workflow has no premium tier and includes PDF, DOCX, Markdown, and JSON exports, but it does not provide an equivalent built-in content library or specialized checker.
|
||||
MyPerfectResume is built around guided writing: step-by-step prompts, expert-written content suggestions, and a resume checker. Reactive Resume is an open-source editor whose core hosted workflow has no premium tier and includes PDF, DOCX, Markdown, and JSON exports, but it has no equivalent content library or specialized checker.
|
||||
|
||||
## Quick comparison
|
||||
|
||||
@@ -15,31 +15,31 @@ MyPerfectResume is geared toward guided writing: it offers step-by-step prompts,
|
||||
| Checking tools | No equivalent specialized checker | ResumeCheck feedback is listed with premium access |
|
||||
| Deployment | Hosted use or self-hosting | Hosted service |
|
||||
|
||||
MyPerfectResume's free-builder guide says free accounts can access tailored content suggestions, expert tips, and unlimited plain-text downloads. The same guide says PDF or Word template downloads require a premium plan. Its pricing page separately lists TXT downloads with basic access and places PDF, Word, and ResumeCheck behind premium access.
|
||||
MyPerfectResume's free-builder guide says free accounts get tailored content suggestions, expert tips, and unlimited plain-text downloads, and that PDF or Word template downloads need a premium plan. Its pricing page lists TXT downloads with basic access and puts PDF, Word, and ResumeCheck behind premium access.
|
||||
|
||||
Reactive Resume takes a different path: it gives you a rendered [PDF, DOCX, Markdown, or JSON export](/guides/exporting-your-resume) without a premium tier. This is most useful when you already know what to write and want to keep both a presentation-ready document and reusable resume data.
|
||||
Reactive Resume takes a different path: you get a rendered [PDF, DOCX, Markdown, or JSON export](/guides/exporting-your-resume) with no premium tier. That helps most when you already know what to write and want both a presentation-ready document and reusable resume data.
|
||||
|
||||
## Where MyPerfectResume is a better fit
|
||||
|
||||
MyPerfectResume fits when getting started with the wording is the main obstacle. Its guide describes prompts for building or importing a resume, job-specific bullet-point suggestions, summary suggestions, writing tips, and AI-powered suggestions for skills. The product also offers a resume checker, so it can suit someone looking for a guided sequence and feedback surface in the same hosted product.
|
||||
MyPerfectResume fits when the wording is the hard part. Its guide describes prompts for building or importing a resume, job-specific bullet-point suggestions, summary suggestions, writing tips, and AI-powered suggestions for skills. It also has a resume checker, so the guided sequence and the feedback live in the same hosted product.
|
||||
|
||||
Its cover-letter workflow is another reason to choose it when you want guided related documents. The free guide describes creating a matching cover letter with prompts and content suggestions, although its designed cover-letter downloads also have a premium boundary.
|
||||
Its cover-letter workflow is another reason to pick it if you want guided related documents. The free guide describes writing a matching cover letter with prompts and content suggestions, though the designed cover-letter downloads sit behind the same premium boundary.
|
||||
|
||||
## Where Reactive Resume is a better fit
|
||||
|
||||
Reactive Resume fits when you have the content and want a designed export without selecting a premium plan. You can make template and layout choices in the editor, then export a PDF or DOCX for document use, Markdown for text workflows, or JSON for a backup that retains the structured resume data. See the [template selection guide](/guides/choosing-a-template) for the available template workflow.
|
||||
Reactive Resume fits when you have the content and want a designed export without picking a premium plan. Make your template and layout choices in the editor, then export a PDF or DOCX for document use, Markdown for text workflows, or JSON for a backup that keeps the structured resume data. The [template selection guide](/guides/choosing-a-template) covers the template workflow.
|
||||
|
||||
It also fits when control over the application matters. Reactive Resume is [MIT-licensed](/legal/license), its source is public, and it can be self-hosted. The hosted service remains an option for people who do not want to operate the stack.
|
||||
You also get control over the application itself. Reactive Resume is [MIT-licensed](/legal/license), its source is public, and you can self-host it. The hosted service stays available if you would rather not run the stack.
|
||||
|
||||
## Which should you choose?
|
||||
|
||||
Choose MyPerfectResume if you want prompts, prewritten suggestions, and a dedicated resume-checking tool while you draft. Choose Reactive Resume if you already have content and want designed exports, portable JSON, or the option to run the software yourself.
|
||||
Choose MyPerfectResume if you want prompts, prewritten suggestions, and a dedicated resume-checking tool while you draft. Choose Reactive Resume if you already have the content and want designed exports, portable JSON, or the option to run the software yourself.
|
||||
|
||||
The choice is not about a promised application outcome. It is about whether guided content and checking tools are worth using a paid workflow for formatted downloads.
|
||||
Neither choice promises an application outcome. The question is whether guided content and checking tools are worth a paid workflow for formatted downloads.
|
||||
|
||||
## Reactive Resume limitations in this comparison
|
||||
|
||||
Reactive Resume does not include an equivalent library of role-specific prewritten bullets, the same step-by-step writing prompts, or a specialized resume checker. Its optional AI integration requires you to configure a provider and review any suggested text. If you want a hosted product that supplies the drafting prompts and feedback in one place, MyPerfectResume has a broader built-in writing surface.
|
||||
Reactive Resume has no equivalent library of role-specific prewritten bullets, no step-by-step writing prompts, and no specialized resume checker. Its optional AI integration asks you to configure a provider and review whatever it suggests. If you want a hosted product that supplies the drafting prompts and the feedback in one place, MyPerfectResume has the broader built-in writing surface.
|
||||
|
||||
## Sources
|
||||
|
||||
|
||||
@@ -3,7 +3,7 @@ title: "Reactive Resume vs Novorésumé"
|
||||
description: "Compare Reactive Resume and Novorésumé by free document limits, templates, guided writing, AI, exports, and self-hosting."
|
||||
---
|
||||
|
||||
Novorésumé is a better fit when guided design, writing advice, a content library, and its integrated assistant are central to drafting. Reactive Resume is a better fit when you need several saved resume versions without its Basic document and page limits.
|
||||
Novorésumé is the stronger choice when guided design, writing advice, a content library, and its built-in assistant carry most of the drafting. Reactive Resume lets you keep several saved resume versions, without the Basic plan's document and page limits.
|
||||
|
||||
## Quick comparison
|
||||
|
||||
@@ -14,25 +14,25 @@ Novorésumé is a better fit when guided design, writing advice, a content libra
|
||||
| Drafting support | Direct editing and optional AI | Guided design, writing advice, content library, and integrated assistant |
|
||||
| Exports | PDF, DOCX, Markdown, and JSON | See Novorésumé plan and export options |
|
||||
|
||||
Novorésumé's current Basic plan permits exactly one document and a maximum one-page document length. Its Premium plan lists 72 documents and documents up to 10 pages. The product also documents templates, a content library, real-time advice, and an integrated assistant.
|
||||
Novorésumé's current Basic plan permits exactly one document, capped at one page. Its Premium plan lists 72 documents and documents up to 10 pages. The product also documents templates, a content library, real-time advice, and an integrated assistant.
|
||||
|
||||
Reactive Resume keeps resume versions in the [dashboard](/guides/managing-resumes-from-the-dashboard) and supports [PDF, DOCX, Markdown, and JSON exports](/guides/exporting-your-resume). Its source is public under the [MIT license](/legal/license), and it can be run with Docker.
|
||||
Reactive Resume keeps resume versions in the [dashboard](/guides/managing-resumes-from-the-dashboard) and supports [PDF, DOCX, Markdown, and JSON exports](/guides/exporting-your-resume). Its source is public under the [MIT license](/legal/license), and it runs with Docker.
|
||||
|
||||
## Where Novorésumé is a better fit
|
||||
|
||||
Choose Novorésumé when its guided design, writing advice, content library, and integrated assistant are more useful than managing several versions in the same system. Premium also fits when its larger document count and longer documents match your needs.
|
||||
Choose Novorésumé when its guided design, writing advice, content library, and integrated assistant are worth more to you than managing several versions in one system. Premium also fits when its larger document count and longer documents match what you need.
|
||||
|
||||
## Where Reactive Resume is a better fit
|
||||
|
||||
Choose Reactive Resume when you want to manage multiple saved resumes and export them in PDF, DOCX, Markdown, or JSON. It also provides a self-hosting option; see the [Docker guide](/self-hosting/docker).
|
||||
Pick Reactive Resume to manage several saved resumes and export them as PDF, DOCX, Markdown, or JSON. You can also self-host it; see the [Docker guide](/self-hosting/docker).
|
||||
|
||||
## Which should you choose?
|
||||
|
||||
Choose Novorésumé when its guided drafting tools are the priority and its Basic or Premium document limits fit your workflow. Choose Reactive Resume when you want multiple resume versions and designed exports without moving to a premium plan.
|
||||
Choose Novorésumé when its guided drafting tools come first and its Basic or Premium document limits fit your workflow. Choose Reactive Resume when you want several resume versions and designed exports without moving to a premium plan.
|
||||
|
||||
## Reactive Resume limitations in this comparison
|
||||
|
||||
Reactive Resume has a smaller guidance and content surface. It does not provide Novorésumé's integrated content library and assistant in the same guided drafting workflow.
|
||||
Reactive Resume has a smaller guidance and content surface. It has no equivalent to Novorésumé's content library and assistant inside a guided drafting workflow.
|
||||
|
||||
## Sources
|
||||
|
||||
|
||||
@@ -3,9 +3,9 @@ title: "Reactive Resume vs Overleaf"
|
||||
description: "Compare Reactive Resume's visual resume builder with Overleaf's LaTeX templates, source editing, collaboration, and PDF workflow."
|
||||
---
|
||||
|
||||
Overleaf is a better fit for direct LaTeX source control, a large community template gallery, and document collaboration. Reactive Resume is a better fit for people who want to edit structured resume sections visually without writing or debugging LaTeX.
|
||||
Overleaf suits people who want to work in LaTeX source, use a large community template gallery, and collaborate on documents. Reactive Resume is for people who want to edit structured resume sections visually, without writing or debugging LaTeX.
|
||||
|
||||
These products use different authoring models. Overleaf is an online LaTeX editor that compiles source into documents, including CV and resume templates. Reactive Resume stores resume content as structured data and renders it through its built-in templates and visual controls.
|
||||
The two products use different authoring models. Overleaf is an online LaTeX editor that compiles source into documents, including CV and resume templates. Reactive Resume stores resume content as structured data and renders it through its own templates and visual controls.
|
||||
|
||||
## Quick comparison
|
||||
|
||||
@@ -18,29 +18,29 @@ These products use different authoring models. Overleaf is an online LaTeX edito
|
||||
| Output | PDF, DOCX, Markdown, and Reactive Resume JSON | Compiled document PDFs and project source |
|
||||
| Free plan | Core hosted resume workflow has no premium tier | Free plan has documented collaboration and compile limits |
|
||||
|
||||
Overleaf's [CV and résumé gallery](https://www.overleaf.com/latex/templates/tagged/cv) includes community templates, while its [plans documentation](https://docs.overleaf.com/getting-started/free-and-premium-plans) explains the differences between free and paid accounts. Reactive Resume keeps the task narrower: enter resume content, select a template, tune its settings, and export the result.
|
||||
Overleaf's [CV and résumé gallery](https://www.overleaf.com/latex/templates/tagged/cv) collects community templates, and its [plans documentation](https://docs.overleaf.com/getting-started/free-and-premium-plans) explains the differences between free and paid accounts. Reactive Resume keeps the task narrower: enter resume content, pick a template, tune its settings, and export the result.
|
||||
|
||||
## Where Overleaf is a better fit
|
||||
|
||||
Use Overleaf if you want to work directly in LaTeX. It gives you control over the source document and access to a broad community template gallery. That can be useful when you already maintain academic or technical documents in LaTeX, want to make source-level typesetting changes, or need a resume that follows a particular LaTeX template.
|
||||
Use Overleaf if you want to work directly in LaTeX. It gives you control over the source document and access to a broad community template gallery. That helps when you already keep academic or technical documents in LaTeX, want to change the typesetting at the source level, or need a resume that follows a particular LaTeX template.
|
||||
|
||||
Overleaf also has a document-collaboration workflow. Its plan pages describe collaborator and compile-time allowances, so review those limits for the plan you use. This can be more suitable than a resume-focused tool when several people need to work on a LaTeX project or when the resume is part of a larger academic document set.
|
||||
Overleaf also has a document-collaboration workflow. Its plan pages describe collaborator and compile-time allowances, so check the limits for the plan you use. That can beat a resume-focused tool when several people work on the same LaTeX project, or when the resume belongs to a larger set of academic documents.
|
||||
|
||||
## Where Reactive Resume is a better fit
|
||||
|
||||
Use Reactive Resume if you prefer a visual editor and do not want to maintain LaTeX source. It keeps common resume content in fields for profile details, experience, education, skills, projects, and other sections, then shows the result in a live preview. You can switch templates and adjust resume-specific layout settings without editing a document class or compilation configuration.
|
||||
Use Reactive Resume if you prefer a visual editor and do not want to maintain LaTeX source. It keeps common resume content in fields for profile details, experience, education, skills, projects, and other sections, then shows the result in a live preview. You can switch templates and adjust resume layout settings without touching a document class or a compilation config.
|
||||
|
||||
Reactive Resume also provides [PDF, DOCX, Markdown, and JSON exports](/guides/exporting-your-resume). Its JSON export preserves resume content and settings for later restoration or another version. If you need to operate the software on your own infrastructure, the project is [MIT-licensed](/legal/license) and [self-hostable](/self-hosting/docker).
|
||||
Reactive Resume also has [PDF, DOCX, Markdown, and JSON exports](/guides/exporting-your-resume). The JSON export preserves resume content and settings so you can restore it later or branch another version. If you need to run the software on your own infrastructure, the project is [MIT-licensed](/legal/license) and [self-hostable](/self-hosting/docker).
|
||||
|
||||
## Which should you choose?
|
||||
|
||||
Choose Overleaf if LaTeX source, community templates, or collaborative academic-document workflows are central to how you work. Choose Reactive Resume if you want a focused visual resume builder and structured fields without a LaTeX editing workflow.
|
||||
Choose Overleaf if LaTeX source, community templates, or collaborative academic documents are central to how you work. Choose Reactive Resume if you want a focused visual resume builder and structured fields without a LaTeX editing workflow.
|
||||
|
||||
Both tools can produce a PDF, but the ongoing maintenance differs. With Overleaf, you maintain a source document. With Reactive Resume, you update resume data and template settings.
|
||||
Both tools produce a PDF, but the upkeep differs. With Overleaf you maintain a source document. With Reactive Resume you update resume data and template settings.
|
||||
|
||||
## Reactive Resume limitations in this comparison
|
||||
|
||||
Reactive Resume does not offer LaTeX source editing or Overleaf-style collaboration for academic document projects. It also does not expose the same source-level typesetting control as a LaTeX template. Overleaf is the more relevant option when those capabilities are required.
|
||||
Reactive Resume has no LaTeX source editing and no Overleaf-style collaboration on academic document projects. It also does not expose the source-level typesetting control of a LaTeX template. Overleaf is the more relevant option when you need those.
|
||||
|
||||
## Sources
|
||||
|
||||
|
||||
@@ -3,7 +3,7 @@ title: "Reactive Resume vs Resume.com"
|
||||
description: "Compare two free resume builders by PDF export, accounts, templates, open-source access, portability, and self-hosting."
|
||||
---
|
||||
|
||||
Reactive Resume and Resume.com both let you create and download a PDF resume without a paid membership. Resume.com is a straightforward hosted builder; Reactive Resume stores resume details in structured sections and also offers source access, self-hosting, and additional export formats.
|
||||
Reactive Resume and Resume.com both let you create and download a PDF resume without a paid membership. Resume.com is a straightforward hosted builder. Reactive Resume stores resume details in structured sections and adds source access, self-hosting, and more export formats.
|
||||
|
||||
## Quick comparison
|
||||
|
||||
@@ -13,31 +13,31 @@ Reactive Resume and Resume.com both let you create and download a PDF resume wit
|
||||
| Accounts | Account required for the hosted builder and saved resume management | An email is requested to save work in the dashboard |
|
||||
| Workflow | Structured sections, template settings, and live preview | Hosted builder with templates and saved resumes |
|
||||
|
||||
The important common ground is the download boundary: Resume.com says its builder has no paid membership tier and that PDF and plain-text downloads are free. Reactive Resume is not a lower-cost substitute for a paid Resume.com PDF; both can produce one without a premium upgrade.
|
||||
The common ground here is the download boundary. Resume.com says its builder has no paid membership tier and that PDF and plain-text downloads are free. Reactive Resume is not a cheaper way to get a Resume.com PDF: both produce one without a premium upgrade.
|
||||
|
||||
Reactive Resume adds [DOCX, Markdown, and JSON exports](/guides/exporting-your-resume). JSON preserves Reactive Resume data for backup or reuse, while Markdown can be useful when a plain-text document needs formatting. Its [public MIT license](/legal/license) and [Docker self-hosting guide](/self-hosting/docker) also make the application runnable outside the hosted service.
|
||||
Reactive Resume adds [DOCX, Markdown, and JSON exports](/guides/exporting-your-resume). JSON preserves the data for backup or reuse, and Markdown helps when a plain-text document still needs some formatting. Its [public MIT license](/legal/license) and [Docker self-hosting guide](/self-hosting/docker) also let you run the application outside the hosted service.
|
||||
|
||||
## Where Resume.com is a better fit
|
||||
|
||||
Resume.com fits when you want a hosted builder with a simple account-and-dashboard workflow. Its account guide says you can start creating a resume and then enter an email address to save it. Its free-plan help page also describes multiple professional and creative templates, editing, and access to saved work online.
|
||||
Resume.com fits when you want a hosted builder with a simple account-and-dashboard workflow. Its account guide says you can start a resume and then enter an email address to save it. Its free-plan help page describes professional and creative templates, editing, and online access to saved work.
|
||||
|
||||
That can be the less technical choice for someone who only needs a browser-based editor and a free PDF or text download. There is no need to set up a server, choose an AI provider, or consider data exports beyond the finished document.
|
||||
That is the less technical choice if you only need a browser-based editor and a free PDF or text download. There is no server to set up, no AI provider to pick, and no data export to think about beyond the finished document.
|
||||
|
||||
## Where Reactive Resume is a better fit
|
||||
|
||||
Reactive Resume fits when the resume should remain portable as data as well as a document. The editor keeps sections separate from templates, so a change of template does not require re-entering work history or education.
|
||||
Reactive Resume fits when the resume should stay portable as data as well as a document. The editor keeps sections separate from templates, so changing a template does not mean re-entering your work history or education.
|
||||
|
||||
It is also a fit for people who need deployment control. You can use the hosted product, inspect the source, or run it on your own infrastructure. For workflows that need programmatic access, Reactive Resume also exposes [MCP tools](/guides/using-the-mcp-server) and API-oriented capabilities. AI assistance is optional and uses a provider you configure, rather than being required for ordinary editing.
|
||||
Deployment is your call too. Use the hosted product, read the source, or run it on your own infrastructure. For programmatic access, Reactive Resume exposes [MCP tools](/guides/using-the-mcp-server) and API capabilities. AI assistance is optional and uses a provider you configure; ordinary editing does not need it.
|
||||
|
||||
## Which should you choose?
|
||||
|
||||
Choose Resume.com when you want a hosted, no-paid-membership builder whose documented free downloads cover PDF and plain text. Choose Reactive Resume when you want the same free-PDF outcome plus structured data exports, optional self-hosting, or automation interfaces.
|
||||
Choose Resume.com when you want a hosted builder with no paid membership, whose documented free downloads cover PDF and plain text. Choose Reactive Resume when you want the same free PDF plus structured data exports, optional self-hosting, or automation interfaces.
|
||||
|
||||
Neither choice removes the need to review the final document for accuracy and formatting. The practical decision is whether a focused hosted workflow is enough or whether control over the application and resume data matters too.
|
||||
Either way, you still have to check the final document for accuracy and formatting. The decision is whether a focused hosted workflow is enough, or whether you also want control over the application and your resume data.
|
||||
|
||||
## Reactive Resume limitations in this comparison
|
||||
|
||||
Reactive Resume has more setup decisions when you use its technical options. Self-hosting requires operating infrastructure, and provider-configured AI requires your own provider setup and may involve provider charges. Its additional exports and automation tools are unnecessary if you only want to enter content in a hosted builder and download a PDF.
|
||||
Reactive Resume asks more of you once you use its technical options. Self-hosting means running infrastructure, and provider-configured AI means your own provider setup and possible provider charges. Its extra exports and automation tools are unnecessary if you only want to type content into a hosted builder and download a PDF.
|
||||
|
||||
## Sources
|
||||
|
||||
|
||||
@@ -3,7 +3,7 @@ title: "Reactive Resume vs Resume.io"
|
||||
description: "Compare Reactive Resume and Resume.io by free PDF access, templates, writing tools, exports, open source, and self-hosting."
|
||||
---
|
||||
|
||||
Resume.io offers a commercial, guided builder with sample content and a template-focused workflow. Its documented free PDF allowance is narrower, covering its Vancouver template alongside TXT export. Reactive Resume includes its templates and PDF, DOCX, Markdown, and JSON exports without a premium resume tier.
|
||||
Resume.io is a commercial, guided builder with sample content and a template-focused workflow. Its documented free PDF allowance is narrower: the Vancouver template, alongside TXT export. Reactive Resume includes its templates and its PDF, DOCX, Markdown, and JSON exports with no premium resume tier.
|
||||
|
||||
## Quick comparison
|
||||
|
||||
@@ -15,31 +15,31 @@ Resume.io offers a commercial, guided builder with sample content and a template
|
||||
| Deployment | Hosted use or self-hosting | Hosted service |
|
||||
| Pricing availability | No premium resume tier | Plans can vary by location |
|
||||
|
||||
Resume.io's free-plan help article says a free account can build a resume, download a PDF with its Vancouver template, or download a TXT file. It says a premium trial is needed to download in its other designed templates and access premium features. This is a template-specific free-PDF allowance, not a claim that all Resume.io PDF downloads are paid.
|
||||
Resume.io's free-plan help article says a free account can build a resume and download either a PDF with the Vancouver template or a TXT file. The same article says downloading in its other designed templates, and using premium features, needs a premium trial. So the free PDF allowance is template-specific, not a claim that every Resume.io PDF download is paid.
|
||||
|
||||
The same help page says Resume.io's plan availability can vary by location or from previous plans. Rather than relying on a quoted price, check its current account flow if plan availability is material to your decision.
|
||||
The help page also says plan availability can vary by location or differ from previous plans. Rather than trusting a quoted price, check the current account flow if plan availability matters to your decision.
|
||||
|
||||
## Where Resume.io is a better fit
|
||||
|
||||
Resume.io fits when you want a commercial template experience with content help included in the service. Its help article points to sample resumes and describes cover-letter tools with pre-generated sentences and tips. A free account can also share an online resume link and return later to edit the document.
|
||||
Resume.io fits when you want a commercial template experience with content help included. Its help article points to sample resumes and describes cover-letter tools with pre-generated sentences and tips. A free account can also share an online resume link and come back later to edit the document.
|
||||
|
||||
The Vancouver template makes it a viable option for someone who likes that design and only needs a single free PDF path. Its premium workflow may suit users who want access to its wider template selection and related features through the hosted product.
|
||||
The Vancouver template makes it workable for someone who likes that design and needs only one free PDF path. Its premium workflow suits people who want the wider template selection and related features through the hosted product.
|
||||
|
||||
## Where Reactive Resume is a better fit
|
||||
|
||||
Reactive Resume fits when you want to choose from included templates and export a designed document without a template-tier limit. Its [export guide](/guides/exporting-your-resume) covers PDF, DOCX, Markdown, and JSON. The data export is useful for retaining structured content and settings in addition to a document download.
|
||||
Reactive Resume fits when you want to pick from the included templates and export a designed document without a template tier in the way. Its [export guide](/guides/exporting-your-resume) covers PDF, DOCX, Markdown, and JSON. The data export keeps your structured content and settings alongside the document download.
|
||||
|
||||
It also fits when source access or self-hosting matter. Reactive Resume is [MIT-licensed](/legal/license), and its [Docker guide](/self-hosting/docker) documents the self-hosted route. The product's optional AI integration lets you configure a provider if you want assistance, while ordinary resume editing does not depend on it.
|
||||
You also get source access and self-hosting. Reactive Resume is [MIT-licensed](/legal/license), and its [Docker guide](/self-hosting/docker) documents the self-hosted route. Its optional AI integration lets you configure a provider if you want help, while ordinary editing does not depend on it.
|
||||
|
||||
## Which should you choose?
|
||||
|
||||
Choose Resume.io if its guided content, sample resumes, hosted workflow, and Vancouver free-PDF option fit how you want to write. Choose Reactive Resume if you want its included templates, multiple export formats, and no premium tier for the core resume workflow.
|
||||
Choose Resume.io if its guided content, sample resumes, hosted workflow, and Vancouver free-PDF option match how you want to write. Choose Reactive Resume if you want its included templates, several export formats, and no premium tier on the core resume workflow.
|
||||
|
||||
The most important detail is not whether either service can create a resume for free. It is whether the free download you need is available in the template and file format you plan to use.
|
||||
Both services can make a resume for free. What matters is whether the free download you need comes in the template and file format you plan to use.
|
||||
|
||||
## Reactive Resume limitations in this comparison
|
||||
|
||||
Reactive Resume has a smaller built-in guided-content library. It does not offer Resume.io's collection of sample resumes, pre-generated cover-letter sentences, and tips as an equivalent integrated experience. Its optional AI features also require a provider choice and configuration, which may be less convenient for someone who wants a commercial writing workflow already assembled.
|
||||
Reactive Resume has a smaller built-in guided-content library. It has no equivalent to Resume.io's collection of sample resumes, pre-generated cover-letter sentences, and tips. Its optional AI features also require you to choose and configure a provider, which is less convenient if you want a commercial writing workflow already assembled.
|
||||
|
||||
## Sources
|
||||
|
||||
|
||||
@@ -3,7 +3,7 @@ title: "Reactive Resume vs Resume-Now"
|
||||
description: "Compare Reactive Resume and Resume-Now by free export formats, guided writing, AI tools, templates, and self-hosting."
|
||||
---
|
||||
|
||||
Resume-Now centers on guided drafting, with content suggestions, AI writing tools, and resume-analysis tools. Reactive Resume centers on direct editing of structured resume data and includes designed PDF and DOCX exports, while its built-in writing-guidance surface is smaller.
|
||||
Resume-Now is built around guided drafting, with content suggestions, AI writing tools, and resume analysis. Reactive Resume is built around direct editing of structured resume data and includes designed PDF and DOCX exports, with a much smaller writing-guidance surface.
|
||||
|
||||
## Quick comparison
|
||||
|
||||
@@ -15,31 +15,31 @@ Resume-Now centers on guided drafting, with content suggestions, AI writing tool
|
||||
| Analysis tools | No equivalent specialized checker | Resume checker, summary generator, skills generator, and AI review |
|
||||
| Deployment | Hosted use or self-hosting | Hosted service |
|
||||
|
||||
Resume-Now's free-builder guide says that the no-cost download is a TXT file. It states that a download using a premium template requires paid access, and its FAQ says premium file formats require an upgrade. That makes free creation different from getting a designed PDF or Word document.
|
||||
Resume-Now's free-builder guide says the no-cost download is a TXT file, and that downloading with a premium template requires paid access. Its FAQ says premium file formats require an upgrade. So free creation is not the same as a designed PDF or Word document.
|
||||
|
||||
Reactive Resume includes [PDF, DOCX, Markdown, and JSON exports](/guides/exporting-your-resume) in the core workflow. JSON is a structured backup format rather than a final application document; PDF and DOCX are the designed document options in this comparison.
|
||||
Reactive Resume includes [PDF, DOCX, Markdown, and JSON exports](/guides/exporting-your-resume) in the core workflow. JSON is a structured backup format rather than a document you send; PDF and DOCX are the designed outputs here.
|
||||
|
||||
## Where Resume-Now is a better fit
|
||||
|
||||
Resume-Now fits when you want guidance while producing the content. Its free-builder guide walks through choosing a template, importing an existing resume, answering career questions, selecting personalized content suggestions, and using an AI enhancement action. It also describes spell-check, formatting controls, and optional sections during review.
|
||||
Resume-Now fits when you want help producing the content. Its free-builder guide walks through picking a template, importing an existing resume, answering career questions, choosing personalized content suggestions, and running an AI enhancement action. It also describes spell-check, formatting controls, and optional sections during review.
|
||||
|
||||
The product has a larger set of related writing and analysis tools. Its public pages list an AI summary generator, skills generator, resume checker, and AI review. This can be useful when you want suggestions and feedback before deciding what to include, rather than starting from your own completed draft.
|
||||
The product has a larger set of related writing and analysis tools. Its public pages list an AI summary generator, a skills generator, a resume checker, and an AI review. Those help when you want suggestions and feedback before deciding what to include, rather than starting from a draft you already wrote.
|
||||
|
||||
## Where Reactive Resume is a better fit
|
||||
|
||||
Reactive Resume fits when direct editing and access to a designed export matter more than a guided-content library. The editor separates resume sections from the visual template, so you can change a template without replacing the underlying experience, education, or skills. The [template guide](/guides/choosing-a-template) covers that selection process.
|
||||
Reactive Resume fits when direct editing and a designed export matter more than a guided-content library. The editor keeps resume sections separate from the visual template, so you can change templates without replacing your experience, education, or skills. The [template guide](/guides/choosing-a-template) covers that selection process.
|
||||
|
||||
It is also suitable when portability or deployment control matters. Reactive Resume is [open source under the MIT license](/legal/license) and can be run using the [self-hosting documentation](/self-hosting/docker). Its optional AI functionality is provider-configured, so it remains optional rather than a required part of the editing workflow.
|
||||
Portability and deployment control come with it. Reactive Resume is [open source under the MIT license](/legal/license) and can be run by following the [self-hosting documentation](/self-hosting/docker). Its AI is provider-configured, so it stays optional rather than a required part of the editing workflow.
|
||||
|
||||
## Which should you choose?
|
||||
|
||||
Choose Resume-Now if you want questions, suggestions, and a collection of hosted analysis tools while drafting, and you accept the TXT-only free download boundary. Choose Reactive Resume if you prefer direct control over your content and want a designed PDF or DOCX export without moving to a premium tier.
|
||||
Choose Resume-Now if you want questions, suggestions, and a set of hosted analysis tools while drafting, and you accept the TXT-only free download. Choose Reactive Resume if you want direct control over your content and a designed PDF or DOCX export without moving to a premium tier.
|
||||
|
||||
Both workflows still require you to verify that every statement is accurate and that the final document is appropriate for the role.
|
||||
Both workflows still leave you to verify that every statement is accurate and that the final document suits the role.
|
||||
|
||||
## Reactive Resume limitations in this comparison
|
||||
|
||||
Reactive Resume has a smaller built-in writing-guidance surface. It does not provide Resume-Now's collection of prewritten suggestions, dedicated resume checker, summary generator, skills generator, or AI review as integrated tools. Its optional AI path also asks you to choose and configure a provider, which is more setup than using a hosted suggestion workflow.
|
||||
Reactive Resume has a smaller built-in writing-guidance surface. It has no equivalent to Resume-Now's prewritten suggestions, resume checker, summary generator, skills generator, or AI review. Its optional AI path also asks you to choose and configure a provider, which is more setup than a hosted suggestion workflow.
|
||||
|
||||
## Sources
|
||||
|
||||
|
||||
@@ -3,7 +3,7 @@ title: "Reactive Resume vs ResumeGemini"
|
||||
description: "Compare Reactive Resume and ResumeGemini by free PDF export, AI optimization, content examples, open source, and self-hosting."
|
||||
---
|
||||
|
||||
ResumeGemini is a better fit when you want prewritten examples and integrated job-targeted AI suggestions while drafting. Reactive Resume is a better fit when open-source deployment control and an optional provider model matter more than a bundled optimization product.
|
||||
ResumeGemini offers prewritten examples and job-targeted AI suggestions while you draft. Reactive Resume gives you deployment control and your own choice of AI provider instead of a bundled optimization product.
|
||||
|
||||
## Quick comparison
|
||||
|
||||
@@ -13,25 +13,25 @@ ResumeGemini is a better fit when you want prewritten examples and integrated jo
|
||||
| Job targeting | Manual edits or optional AI assistance | AI optimization, keyword alignment, and content tips for a target job |
|
||||
| PDF | PDF export | Site documents free-plan PDF download and free/premium templates |
|
||||
|
||||
ResumeGemini describes prewritten, job-specific examples and AI recommendations, keyword alignment, and content tips based on a target job. Its product page documents free and premium templates, plus free-plan resume download. This supports at least one free-template/free-PDF path; it does not establish that every template is free.
|
||||
ResumeGemini describes prewritten, job-specific examples, AI recommendations, keyword alignment, and content tips for a target job. Its product page documents free and premium templates plus a free-plan resume download. That covers at least one free template and free PDF path; it does not mean every template is free.
|
||||
|
||||
Reactive Resume supports PDF, DOCX, Markdown, and JSON exports. AI is optional and requires a tested, enabled provider that you configure; the provider account can have separate costs.
|
||||
Reactive Resume supports PDF, DOCX, Markdown, and JSON exports. AI is optional and needs a provider you configure, test, and enable, and that provider account can cost extra.
|
||||
|
||||
## Where ResumeGemini is a better fit
|
||||
|
||||
Choose ResumeGemini when you want a content library and job-targeted AI optimization in the same drafting workflow. Its examples and suggestions can be useful when the first version of the wording is the main problem.
|
||||
Choose ResumeGemini when you want a content library and job-targeted AI optimization in one drafting workflow. Its examples and suggestions help most when the first draft of the wording is the problem.
|
||||
|
||||
## Where Reactive Resume is a better fit
|
||||
|
||||
Choose Reactive Resume when you want to inspect or deploy the software yourself, keep resumes as structured data, or select an AI provider independently. It also exposes authenticated API and MCP workflows for automation.
|
||||
Use Reactive Resume to inspect or deploy the software yourself, keep resumes as structured data, or pick your own AI provider. It also exposes authenticated API and MCP workflows for automation.
|
||||
|
||||
## Which should you choose?
|
||||
|
||||
Choose ResumeGemini for integrated examples and keyword-oriented suggestions. Choose Reactive Resume for open-source access, self-hosting, and control over the AI provider and automation workflow.
|
||||
Choose ResumeGemini for built-in examples and keyword-oriented suggestions. Choose Reactive Resume for open-source access, self-hosting, and control over the AI provider and automation workflow.
|
||||
|
||||
## Reactive Resume limitations in this comparison
|
||||
|
||||
Reactive Resume does not include a built-in content-example library or a native keyword-optimization product. Its AI workflow also requires you to configure provider credentials before using it.
|
||||
Reactive Resume has no built-in library of content examples and no native keyword-optimization product. Its AI workflow also needs provider credentials before you can use it.
|
||||
|
||||
## Sources
|
||||
|
||||
|
||||
@@ -3,7 +3,7 @@ title: "Reactive Resume vs Resumod"
|
||||
description: "Compare Reactive Resume and Resumod by AI writing, role-specific samples, named tool surfaces, exports, open source, and self-hosting."
|
||||
---
|
||||
|
||||
Resumod is a better fit when you want role-specific sample categories alongside its named ATS Resume Checker and AI Resume Builder tools. Reactive Resume is a better fit when you want open-source deployment, optional bring-your-own AI, and structured resume exports.
|
||||
Resumod suits you when you want role-specific sample categories alongside its ATS Resume Checker and AI Resume Builder. Reactive Resume gives you open-source deployment, optional bring-your-own AI, and structured resume exports.
|
||||
|
||||
## Quick comparison
|
||||
|
||||
@@ -12,25 +12,25 @@ Resumod is a better fit when you want role-specific sample categories alongside
|
||||
| Content help | Direct editing; optional provider-configured AI | Role-specific sample categories and a named AI Resume Builder |
|
||||
| Checking tools | No equivalent built-in tool | Named ATS Resume Checker |
|
||||
|
||||
Resumod's [product page](https://resumod.co/) lists role-specific sample categories and links to an [ATS Resume Checker](https://resumod.co/ats-resume-checker) and [AI Resume Builder](https://resumod.co/ai-resume-builder). The cited pages do not document the detailed mechanics, outputs, or complete plan limits for those tools.
|
||||
Resumod's [product page](https://resumod.co/) lists role-specific sample categories and links to an [ATS Resume Checker](https://resumod.co/ats-resume-checker) and an [AI Resume Builder](https://resumod.co/ai-resume-builder). Those pages do not document how the tools work, what they output, or their full plan limits.
|
||||
|
||||
Reactive Resume offers PDF, DOCX, Markdown, and JSON exports. Its AI features are optional: you connect and enable a provider using your own credentials, and that provider can have separate costs.
|
||||
Reactive Resume exports PDF, DOCX, Markdown, and JSON. Its AI is optional: you connect and enable a provider with your own credentials, and that provider can cost extra.
|
||||
|
||||
## Where Resumod is a better fit
|
||||
|
||||
Choose Resumod when role-specific examples and its named ATS-checker and AI-builder tools are more useful than provider choice.
|
||||
Choose Resumod when role-specific examples and its named ATS-checker and AI-builder tools are worth more to you than picking your own provider.
|
||||
|
||||
## Where Reactive Resume is a better fit
|
||||
|
||||
Choose Reactive Resume when source access, self-hosting, and separate provider choice are important. It keeps resumes as structured data and exposes authenticated API and MCP workflows for automation.
|
||||
Use Reactive Resume when source access, self-hosting, and a separate provider choice matter. It keeps resumes as structured data and exposes authenticated API and MCP workflows for automation.
|
||||
|
||||
## Which should you choose?
|
||||
|
||||
Choose Resumod for its bundled sample and tool surfaces. Choose Reactive Resume for configurable AI, deployment control, several export formats, and data-oriented automation.
|
||||
Choose Resumod for its bundled samples and named tools. Choose Reactive Resume for configurable AI, deployment control, several export formats, and data-oriented automation.
|
||||
|
||||
## Reactive Resume limitations in this comparison
|
||||
|
||||
Reactive Resume does not include a built-in role-specific content library or a named ATS-checker tool. Its AI features also need provider setup before they are available.
|
||||
Reactive Resume has no built-in role-specific content library and no named ATS-checker tool. Its AI features also need provider setup before they work.
|
||||
|
||||
## Sources
|
||||
|
||||
|
||||
@@ -3,7 +3,7 @@ title: "Reactive Resume vs Rezi"
|
||||
description: "Compare Reactive Resume and Rezi by free limits, ATS scoring, keyword targeting, AI writing, provider choice, and self-hosting."
|
||||
---
|
||||
|
||||
Rezi is a better fit when you want its integrated score, keyword-targeting, AI writing, interview tool, and expert-review option. Reactive Resume is a better fit when you want optional provider-configured AI, open-source self-hosting, and API or MCP automation.
|
||||
Rezi suits you when you want its score, keyword targeting, AI writing, interview tool, and expert-review option. Reactive Resume keeps AI optional and provider-configured, and adds open-source self-hosting plus API or MCP automation.
|
||||
|
||||
## Quick comparison
|
||||
|
||||
@@ -16,25 +16,25 @@ Rezi is a better fit when you want its integrated score, keyword-targeting, AI w
|
||||
| Free limits | Core hosted workflow has no premium tier | One resume and three PDF downloads |
|
||||
| Deployment | Hosted use or self-hosting | Hosted service |
|
||||
|
||||
Rezi's pricing page documents the free plan's one-resume and three-PDF-download limits, plus integrated AI writing and editing. It also lists Rezi Score, keyword targeting, AI Interview, and an expert resume-review option. These are documented product features and positioning, not a promise of ATS passage, interviews, or hiring results.
|
||||
Rezi's pricing page documents the free plan's one-resume and three-PDF-download limits, plus integrated AI writing and editing. It also lists Rezi Score, keyword targeting, AI Interview, and an expert resume-review option. Those are documented product features, not a promise of ATS passage, interviews, or hiring results.
|
||||
|
||||
Reactive Resume's AI is optional and bring-your-own-provider: you configure provider credentials, and provider use can incur separate costs. It does not have Rezi's specialist scoring, keyword-targeting, interview, or human-review tools.
|
||||
Reactive Resume's AI is optional and bring-your-own-provider: you configure the credentials, and provider use can cost extra. It has no equivalent to Rezi Score, keyword targeting, AI Interview, or expert review.
|
||||
|
||||
## Where Rezi is a better fit
|
||||
|
||||
Choose Rezi when you want its score, keyword-targeting, AI writing, interview practice, or expert-review option in one product. The documented free limits are also useful to consider if you only need one resume and up to three PDF downloads.
|
||||
Choose Rezi when you want its score, keyword targeting, AI writing, interview practice, or expert review in one product. Its documented free limits are also worth weighing if you only need one resume and up to three PDF downloads.
|
||||
|
||||
## Where Reactive Resume is a better fit
|
||||
|
||||
Choose Reactive Resume when provider choice, open-source access, and self-hosting are more important than an integrated score. It also provides authenticated API and MCP workflows for resume and application automation.
|
||||
Reactive Resume is the better choice when provider choice, open-source access, and self-hosting matter more than a built-in score. It also has authenticated API and MCP workflows for resume and application automation.
|
||||
|
||||
## Which should you choose?
|
||||
|
||||
Choose Rezi for an integrated scoring and review-oriented workflow. Choose Reactive Resume for deployment control, configurable AI, structured exports, and API or MCP automation.
|
||||
Choose Rezi for a scoring and review-oriented workflow. Choose Reactive Resume for deployment control, configurable AI, structured exports, and API or MCP automation.
|
||||
|
||||
## Reactive Resume limitations in this comparison
|
||||
|
||||
Reactive Resume does not offer Rezi's specialist score, keyword-targeting, interview tool, or human-review option. Its AI features require provider setup and may involve separate provider costs.
|
||||
Reactive Resume has no equivalent to Rezi's score, keyword targeting, interview tool, or human review. Its AI features need provider setup and may cost extra through the provider.
|
||||
|
||||
## Sources
|
||||
|
||||
|
||||
@@ -3,7 +3,7 @@ title: "Reactive Resume vs Zety"
|
||||
description: "Compare Reactive Resume and Zety by free downloads, guided writing, resume checks, templates, open source, and self-hosting."
|
||||
---
|
||||
|
||||
Zety combines a guided resume builder with writing assistance, a cover-letter workflow, a resume check, and job-matching tools. Reactive Resume is an open-source editor that includes designed PDF and DOCX exports, but it does not provide equivalent prewritten guidance or job matching.
|
||||
Zety is a guided resume builder with writing assistance, a cover-letter workflow, a resume check, and job-matching tools. Reactive Resume is an open-source editor with designed PDF and DOCX exports, and it has no equivalent prewritten guidance or job matching.
|
||||
|
||||
## Quick comparison
|
||||
|
||||
@@ -15,31 +15,31 @@ Zety combines a guided resume builder with writing assistance, a cover-letter wo
|
||||
| Related job tools | No equivalent job matching | Resume Check and Instant Job Matches listed in the free package |
|
||||
| Deployment | Hosted use or self-hosting | Hosted service |
|
||||
|
||||
Zety's pricing page lists TXT download in its free package. In the plan comparison, it identifies PDF, Word, and TXT as multiple formats and shows TXT only for the free package. This means the free package can create and export text, but a designed PDF or Word download is in the paid workflow.
|
||||
Zety's pricing page lists a TXT download in its free package. Its plan comparison names PDF, Word, and TXT among its download formats and shows TXT only for the free package. So the free package can write and export text, while a designed PDF or Word download sits in the paid workflow.
|
||||
|
||||
Reactive Resume includes [PDF, DOCX, Markdown, and JSON exports](/guides/exporting-your-resume) in its core resume workflow. The difference is a document-format boundary, not a guarantee about how either resume will be received by an employer or an applicant-tracking system.
|
||||
Reactive Resume includes [PDF, DOCX, Markdown, and JSON exports](/guides/exporting-your-resume) in its core resume workflow. That difference is about document formats. Neither product can tell you how an employer or an applicant-tracking system will handle the result.
|
||||
|
||||
## Where Zety is a better fit
|
||||
|
||||
Zety fits when you want guidance and related job-search tools in one hosted product. Its pricing page lists a resume builder, templates, cover-letter builder, cover-letter templates, a resume check, and instant job matches. The wider Zety site also presents resume help and examples alongside the builder.
|
||||
Zety fits when you want guidance and related job-search tools in one hosted product. Its pricing page lists a resume builder, templates, a cover-letter builder, cover-letter templates, a resume check, and instant job matches. The wider Zety site puts resume help and examples alongside the builder.
|
||||
|
||||
That can be a practical fit when you want assistance choosing words, want to prepare a matching cover letter, or want a separate checking tool before exporting. The free package's TXT download can also be sufficient when you are submitting content into a text-based form rather than attaching a formatted document.
|
||||
That suits you if you want help choosing words, a matching cover letter, or a separate check before you export. The free package's TXT download is also enough when you paste content into a text form instead of attaching a formatted document.
|
||||
|
||||
## Where Reactive Resume is a better fit
|
||||
|
||||
Reactive Resume fits when you want to download a designed PDF or DOCX without upgrading. Its templates render structured resume sections, and the [template guide](/guides/choosing-a-template) explains the template-selection workflow. JSON export retains Reactive Resume's structured data for backup or reuse, which is separate from the final PDF or DOCX.
|
||||
Reactive Resume fits when you want to download a designed PDF or DOCX without upgrading. Its templates render structured resume sections, and the [template guide](/guides/choosing-a-template) covers how to pick one. JSON export keeps your structured data for backup or reuse, separately from the final PDF or DOCX.
|
||||
|
||||
It also offers deployment control: the source is public under the [MIT license](/legal/license), and the project can be deployed through the [Docker self-hosting guide](/self-hosting/docker). Optional AI support can be configured with your own provider if you want assistance while editing.
|
||||
You also control where it runs. The source is public under the [MIT license](/legal/license), and the [Docker self-hosting guide](/self-hosting/docker) covers running your own instance. AI help is optional and uses a provider you configure.
|
||||
|
||||
## Which should you choose?
|
||||
|
||||
Choose Zety if you want a hosted builder with guided writing, a resume check, cover-letter tools, and job-matching features, and TXT is enough for the free export. Choose Reactive Resume if a free designed PDF or DOCX, structured exports, and the option to self-host are more important than those built-in guidance tools.
|
||||
Choose Zety if you want a hosted builder with guided writing, a resume check, cover-letter tools, and job matching, and TXT is enough for the free export. Choose Reactive Resume if a free designed PDF or DOCX, structured exports, and the option to self-host matter more than those guidance tools.
|
||||
|
||||
Review the final wording and document layout in either product. The available toolset can support preparation, but it does not determine a hiring result.
|
||||
Either way, check the final wording and layout yourself. The tools help you prepare a resume; they do not decide the hiring result.
|
||||
|
||||
## Reactive Resume limitations in this comparison
|
||||
|
||||
Reactive Resume does not have an equivalent integrated library of prewritten writing guidance, a dedicated resume-check product, or job matching. Its optional AI route needs provider setup, and self-hosting has operational work. Zety may be more convenient if you want those hosted services available alongside the builder and do not need a free PDF or Word export.
|
||||
Reactive Resume has no built-in library of prewritten writing guidance, no dedicated resume-check product, and no job matching. Its optional AI route needs provider setup, and self-hosting means running a server. Zety is more convenient if you want those hosted services next to the builder and do not need a free PDF or Word export.
|
||||
|
||||
## Sources
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: "Project Architecture"
|
||||
description: "Explore the Reactive Resume monorepo layout, runtime boundaries between the web and server apps, and the package ownership model."
|
||||
title: "Project architecture"
|
||||
description: "How the Reactive Resume monorepo is laid out, the runtime boundaries between the web and server apps, and the package ownership model."
|
||||
---
|
||||
|
||||
Reactive Resume is a pnpm/Turborepo monorepo. The product runs as one deployed Node.js process, while the source is split into a full-stack web app, a server adapter, and focused internal packages.
|
||||
@@ -9,7 +9,7 @@ Internal packages are source-consumed through their `package.json` export maps.
|
||||
|
||||
---
|
||||
|
||||
## Runtime Shape
|
||||
## Runtime shape
|
||||
|
||||
```mermaid
|
||||
flowchart TD
|
||||
@@ -39,7 +39,7 @@ flowchart TD
|
||||
|
||||
---
|
||||
|
||||
## Workspace Map
|
||||
## Workspace map
|
||||
|
||||
| Workspace | Ownership |
|
||||
| --- | --- |
|
||||
@@ -65,7 +65,7 @@ flowchart TD
|
||||
|
||||
---
|
||||
|
||||
## Boundary Rules
|
||||
## Boundary rules
|
||||
|
||||
- Use `@reactive-resume/*` package exports for cross-workspace imports.
|
||||
- Do not import another workspace through `apps/**`, `packages/**`, `@reactive-resume/*/src/**`, or a TypeScript path alias to another workspace's `src`.
|
||||
@@ -83,7 +83,7 @@ pnpm exec biome check biome.json turbo.json tooling/grit/no-cross-workspace-src-
|
||||
|
||||
---
|
||||
|
||||
## Feature Placement
|
||||
## Feature placement
|
||||
|
||||
When adding code, choose the owner by behavior:
|
||||
|
||||
@@ -102,7 +102,7 @@ When adding code, choose the owner by behavior:
|
||||
|
||||
---
|
||||
|
||||
## Web Layout
|
||||
## Web layout
|
||||
|
||||
`apps/web/src/routes` stays route-owned. Route files handle URL shape, loaders, redirects, metadata, and SSR flags.
|
||||
|
||||
@@ -114,7 +114,7 @@ Dialog runtime state is centralized in `apps/web/src/dialogs/store.ts`, while di
|
||||
|
||||
---
|
||||
|
||||
## API Layout
|
||||
## API layout
|
||||
|
||||
`packages/api/src/routers/index.ts` exports the top-level oRPC contract. Feature modules under `packages/api/src/features/*` own their procedure modules, services, helpers, tests, and public package exports.
|
||||
|
||||
@@ -122,7 +122,7 @@ Avoid reintroducing technical-layer folders such as `services/` or `helpers/` at
|
||||
|
||||
---
|
||||
|
||||
## PDF And Export Boundaries
|
||||
## PDF and export boundaries
|
||||
|
||||
`packages/pdf` owns React PDF generation:
|
||||
|
||||
@@ -136,7 +136,7 @@ DOCX export generation lives in `packages/docx`.
|
||||
|
||||
---
|
||||
|
||||
## MCP Boundary
|
||||
## MCP boundary
|
||||
|
||||
MCP implementation lives in `packages/mcp`. It exposes canonical unprefixed tool names such as `list_resumes`, `read_resume`, and `apply_resume_patch`.
|
||||
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
title: "Development Setup"
|
||||
title: "Development setup"
|
||||
description: "Set up a local development environment for Reactive Resume with pnpm, Docker services, environment variables, and the web and server apps."
|
||||
---
|
||||
|
||||
@@ -8,11 +8,11 @@ description: "Set up a local development environment for Reactive Resume with pn
|
||||
[Docker](https://docs.docker.com/get-docker/) and Docker Compose - [Git](https://git-scm.com/)
|
||||
</Info>
|
||||
|
||||
This guide walks you through setting up Reactive Resume for local development. Whether you're contributing to the project or customizing it for your needs, these steps will get you up and running.
|
||||
These steps set up Reactive Resume for local development, whether you're contributing to the project or customizing it for yourself.
|
||||
|
||||
---
|
||||
|
||||
## Setting Up Your Development Environment
|
||||
## Setting up your development environment
|
||||
|
||||
<Steps>
|
||||
<Step title="Clone the Repository">
|
||||
@@ -63,7 +63,7 @@ This guide walks you through setting up Reactive Resume for local development. W
|
||||
cp .env.example .env.local
|
||||
```
|
||||
|
||||
Then edit `.env.local` as needed — for local development on the host, set at minimum:
|
||||
Then edit `.env.local` as needed. For local development on the host, set at minimum:
|
||||
|
||||
```bash
|
||||
# Application
|
||||
@@ -95,7 +95,7 @@ This guide walks you through setting up Reactive Resume for local development. W
|
||||
```
|
||||
|
||||
<Tip>
|
||||
**Email Testing**: The development stack includes [Mailpit](https://mailpit.axllent.org/), an email testing tool. All emails sent by the application will be captured and viewable at [http://localhost:8025](http://localhost:8025). No emails will actually be sent to real addresses during development.
|
||||
**Email testing**: The development stack includes [Mailpit](https://mailpit.axllent.org/). Emails the app sends are captured there and viewable at [http://localhost:8025](http://localhost:8025), so nothing reaches a real address during development.
|
||||
</Tip>
|
||||
|
||||
</Step>
|
||||
@@ -120,9 +120,9 @@ This guide walks you through setting up Reactive Resume for local development. W
|
||||
|
||||
---
|
||||
|
||||
## Available Scripts
|
||||
## Available scripts
|
||||
|
||||
Here are the most commonly used scripts during development:
|
||||
The scripts you will use most during development:
|
||||
|
||||
### Development
|
||||
|
||||
@@ -151,9 +151,7 @@ Here are the most commonly used scripts during development:
|
||||
| ------------------------- | -------------------------------------- |
|
||||
| `pnpm run lingui:extract` | Extract translatable strings from code |
|
||||
|
||||
## Understanding the Project Structure
|
||||
|
||||
Understanding the project structure will help you navigate the codebase:
|
||||
## Understanding the project structure
|
||||
|
||||
```
|
||||
reactive-resume/
|
||||
@@ -179,9 +177,9 @@ reactive-resume/
|
||||
|
||||
---
|
||||
|
||||
## Working with the Database
|
||||
## Working with the database
|
||||
|
||||
### Viewing the Database
|
||||
### Viewing the database
|
||||
|
||||
Use Drizzle Studio to explore and manage your database:
|
||||
|
||||
@@ -191,7 +189,7 @@ dotenvx run -f .env.local -- pnpm run db:studio
|
||||
|
||||
This opens a web-based GUI at [https://local.drizzle.studio](https://local.drizzle.studio).
|
||||
|
||||
### Making Schema Changes
|
||||
### Making schema changes
|
||||
|
||||
1. Edit the schema in `packages/db/src/schema/*`
|
||||
2. Generate a migration:
|
||||
@@ -207,11 +205,11 @@ This opens a web-based GUI at [https://local.drizzle.studio](https://local.drizz
|
||||
|
||||
---
|
||||
|
||||
## Working with Translations
|
||||
## Working with translations
|
||||
|
||||
Reactive Resume uses [Lingui](https://lingui.dev/) for internationalization.
|
||||
|
||||
### Adding Translatable Text
|
||||
### Adding translatable text
|
||||
|
||||
Use the `t` macro for strings or `<Trans>` component for JSX:
|
||||
|
||||
@@ -226,7 +224,7 @@ const message = t`Hello, World!`;
|
||||
<Trans>Welcome to Reactive Resume</Trans>;
|
||||
```
|
||||
|
||||
### Extracting Translations
|
||||
### Extracting translations
|
||||
|
||||
After adding new translatable text, extract them to the locale files:
|
||||
|
||||
@@ -234,13 +232,13 @@ After adding new translatable text, extract them to the locale files:
|
||||
pnpm run lingui:extract
|
||||
```
|
||||
|
||||
Translation files are located in `apps/web/locales` in `.po` format.
|
||||
Translation files live in `apps/web/locales`, in `.po` format.
|
||||
|
||||
---
|
||||
|
||||
## Code Quality
|
||||
## Code quality
|
||||
|
||||
### Linting & Formatting
|
||||
### Linting & formatting
|
||||
|
||||
Uses [Biome](https://biomejs.dev/) for linting, formatting, import organization, and Tailwind class sorting:
|
||||
|
||||
@@ -252,7 +250,7 @@ pnpm exec biome check .
|
||||
pnpm check
|
||||
```
|
||||
|
||||
### Type Checking
|
||||
### Type checking
|
||||
|
||||
Run TypeScript type checking:
|
||||
|
||||
@@ -314,11 +312,11 @@ pnpm run typecheck
|
||||
|
||||
---
|
||||
|
||||
## Next Steps
|
||||
## Next steps
|
||||
|
||||
<CardGroup cols={2}>
|
||||
<Card title="Project Architecture" icon="folder-open" href="/contributing/architecture">
|
||||
Deep dive into the project architecture and codebase structure.
|
||||
How the project and codebase are structured.
|
||||
</Card>
|
||||
<Card title="GitHub Repository" icon="github" href="https://github.com/amruthpillai/reactive-resume">
|
||||
View the source code and contribute to the project.
|
||||
|
||||
@@ -1,15 +1,15 @@
|
||||
---
|
||||
title: "Contributing Translations"
|
||||
title: "Contributing translations"
|
||||
description: "Contribute translations for Reactive Resume through Crowdin by joining the project, proposing strings, requesting new languages, and syncing updates."
|
||||
---
|
||||
|
||||
Reactive Resume is used by people all around the world, and translations help make the app accessible to everyone. If you speak a language other than English, you can help by contributing translations.
|
||||
Reactive Resume is used all over the world. If you speak a language other than English, you can help by contributing translations.
|
||||
|
||||
---
|
||||
|
||||
## How Translations Work
|
||||
## How translations work
|
||||
|
||||
Reactive Resume uses [Crowdin](https://crowdin.com/) as its localization management platform. Crowdin provides a user-friendly interface where translators can contribute translations without needing to write code or work with files directly.
|
||||
Reactive Resume uses [Crowdin](https://crowdin.com/) as its localization management platform. Crowdin gives translators an interface for contributing translations without writing code or editing files directly.
|
||||
|
||||
<Info>
|
||||
The Reactive Resume Crowdin project is available at
|
||||
@@ -20,7 +20,7 @@ Once translations are submitted and approved on Crowdin, they are automatically
|
||||
|
||||
---
|
||||
|
||||
## Getting Started
|
||||
## Getting started
|
||||
|
||||
<Steps>
|
||||
<Step title="Create a Crowdin Account">
|
||||
@@ -57,11 +57,11 @@ Once translations are submitted and approved on Crowdin, they are automatically
|
||||
|
||||
---
|
||||
|
||||
## Translation Guidelines
|
||||
## Translation guidelines
|
||||
|
||||
To maintain consistency across all translations, please follow these guidelines:
|
||||
|
||||
### Preserve Placeholders
|
||||
### Preserve placeholders
|
||||
|
||||
Some strings contain placeholders like `{name}` or `{count}`. These must remain unchanged in your translation:
|
||||
|
||||
@@ -70,7 +70,7 @@ English: "Hello, {name}!"
|
||||
Spanish: "¡Hola, {name}!"
|
||||
```
|
||||
|
||||
### Keep Formatting
|
||||
### Keep formatting
|
||||
|
||||
Preserve any HTML tags or markdown formatting in the source text:
|
||||
|
||||
@@ -79,17 +79,17 @@ English: "Click <1>here</1> to continue"
|
||||
German: "Klicken Sie <1>hier</1>, um fortzufahren"
|
||||
```
|
||||
|
||||
### Use Formal or Informal Tone Consistently
|
||||
### Use formal or informal tone consistently
|
||||
|
||||
Choose either formal or informal language based on what's standard for software in your language, and stick with it throughout.
|
||||
|
||||
### Technical Terms
|
||||
### Technical terms
|
||||
|
||||
Some technical terms (like "PDF", "URL", "JSON") are often kept in English across languages. Use your judgment based on what's common in your language's software community.
|
||||
|
||||
---
|
||||
|
||||
## Requesting a New Language
|
||||
## Requesting a new language
|
||||
|
||||
If your language is not listed in the Crowdin project, you can request it to be added.
|
||||
|
||||
@@ -110,7 +110,7 @@ Once approved, the language will be added to Crowdin and you can begin translati
|
||||
|
||||
---
|
||||
|
||||
## When Will My Translations Appear?
|
||||
## When will my translations appear?
|
||||
|
||||
Translations submitted on Crowdin are synced to the codebase periodically. Once merged, they will be included in the next release of Reactive Resume.
|
||||
|
||||
@@ -121,7 +121,7 @@ Translations submitted on Crowdin are synced to the codebase periodically. Once
|
||||
|
||||
---
|
||||
|
||||
## Tips for Effective Translation
|
||||
## Tips for effective translation
|
||||
|
||||
<CardGroup cols={2}>
|
||||
<Card title="Use Context" icon="eye">
|
||||
@@ -140,7 +140,7 @@ Translations submitted on Crowdin are synced to the codebase periodically. Once
|
||||
|
||||
---
|
||||
|
||||
## Need Help?
|
||||
## Need help?
|
||||
|
||||
<CardGroup cols={2}>
|
||||
<Card icon="book-open" title="Crowdin Translator Docs" href="https://support.crowdin.com/for-translators/">
|
||||
@@ -153,4 +153,4 @@ Translations submitted on Crowdin are synced to the codebase periodically. Once
|
||||
|
||||
---
|
||||
|
||||
Thank you for helping make Reactive Resume accessible to users worldwide!
|
||||
Thank you for helping translate Reactive Resume.
|
||||
|
||||
+16
-20
@@ -9,14 +9,14 @@ description: "Reactive Resume is a free, open-source resume builder that lets yo
|
||||
|
||||
## What is Reactive Resume?
|
||||
|
||||
**Reactive Resume** is a free and open-source resume builder designed to simplify the process of creating, updating, and sharing your professional resume. Built with privacy as a core principle, it gives you complete control over your data while providing a powerful, modern experience.
|
||||
Reactive Resume is a free and open-source resume builder that makes it easy to create, update, and share your resume. Built with privacy as a core principle, it gives you complete control over your data.
|
||||
|
||||
<CardGroup cols={2}>
|
||||
<Card title="Privacy First" icon="shield-check">
|
||||
Your data stays yours. No tracking, no ads, and complete transparency with our open-source codebase.
|
||||
Your data stays yours. No tracking, no ads, and an open-source codebase you can read.
|
||||
</Card>
|
||||
<Card title="Beautiful Templates" icon="palette">
|
||||
Choose from professionally designed templates that make your resume stand out from the crowd.
|
||||
Choose from a set of professionally designed templates.
|
||||
</Card>
|
||||
<Card title="Real-time Preview" icon="eye">
|
||||
See changes instantly as you type. What you see is exactly what you'll get when you export.
|
||||
@@ -26,7 +26,7 @@ description: "Reactive Resume is a free, open-source resume builder that lets yo
|
||||
</Card>
|
||||
</CardGroup>
|
||||
|
||||
## Key Features
|
||||
## Key features
|
||||
|
||||
<Frame>
|
||||
<img src="/images/getting-started/infographic.webp" alt="An infographic of the major features of Reactive Resume" />
|
||||
@@ -40,21 +40,19 @@ description: "Reactive Resume is a free, open-source resume builder that lets yo
|
||||
|
||||
<Accordion title="Multiple Templates" icon="grid-2">
|
||||
Choose from a variety of professionally designed templates including Azurill, Bronzor, Chikorita, Ditgar, Ditto,
|
||||
Gengar, Glalie, Kakuna, Lapras, Leafish, Meowth, Onyx, Pikachu, Rhyhorn, and Scizor - each with unique layouts and styles.
|
||||
Gengar, Glalie, Kakuna, Lapras, Leafish, Meowth, Onyx, Pikachu, Rhyhorn, and Scizor, each with its own layout and style.
|
||||
</Accordion>
|
||||
|
||||
<Accordion title="Rich Text Editor" icon="text">
|
||||
Format your content with bold, italic, links, lists, and more using our intuitive rich text editor powered by
|
||||
Tiptap.
|
||||
Format your content with bold, italic, links, lists, and more using the rich text editor, powered by Tiptap.
|
||||
</Accordion>
|
||||
|
||||
<Accordion title="Multi-language Support" icon="globe">
|
||||
Reactive Resume supports multiple languages, making it accessible to users worldwide. Contribute translations to
|
||||
help us reach more people.
|
||||
Reactive Resume is available in multiple languages. Contribute translations to help us reach more people.
|
||||
</Accordion>
|
||||
|
||||
<Accordion title="Dark Mode" icon="moon">
|
||||
Work comfortably in any lighting condition with built-in dark mode support that's easy on your eyes.
|
||||
Built-in dark mode support, so you can work comfortably in any lighting condition.
|
||||
</Accordion>
|
||||
|
||||
<Accordion title="Self-hosting Ready" icon="server">
|
||||
@@ -63,22 +61,20 @@ description: "Reactive Resume is a free, open-source resume builder that lets yo
|
||||
|
||||
</AccordionGroup>
|
||||
|
||||
## Getting Started
|
||||
## Getting started
|
||||
|
||||
Whether you want to use our hosted version or run your own instance, Reactive Resume has got you covered.
|
||||
Use the hosted version, or run your own instance.
|
||||
|
||||
<CardGroup cols={2}>
|
||||
<Card title="Quickstart" icon="rocket" href="/getting-started/quickstart">
|
||||
Get up and running in minutes with our hosted version or deploy your own instance.
|
||||
Start with the hosted version, or deploy your own instance.
|
||||
</Card>
|
||||
<Card title="Development Setup" icon="code" href="/contributing/development">
|
||||
Set up a local development environment to contribute or customize Reactive Resume.
|
||||
</Card>
|
||||
</CardGroup>
|
||||
|
||||
## Tech Stack
|
||||
|
||||
Reactive Resume is built with modern web technologies:
|
||||
## Tech stack
|
||||
|
||||
| Category | Technology |
|
||||
| ---------------- | ------------------------------- |
|
||||
@@ -92,7 +88,7 @@ Reactive Resume is built with modern web technologies:
|
||||
| UI Components | Base UI + shadcn-style package |
|
||||
| State Management | Zustand + TanStack Query |
|
||||
|
||||
## Community & Support
|
||||
## Community & support
|
||||
|
||||
<CardGroup cols={2}>
|
||||
<Card title="GitHub" icon="github" href="https://github.com/amruthpillai/reactive-resume">
|
||||
@@ -102,13 +98,13 @@ Reactive Resume is built with modern web technologies:
|
||||
Ask questions about setup, configuration, and using Reactive Resume.
|
||||
</Card>
|
||||
<Card title="Reddit" icon="reddit" href="https://reddit.com/r/reactiveresume">
|
||||
Join our Reddit community to get help and connect with other users.
|
||||
Get help and talk to other users on our subreddit.
|
||||
</Card>
|
||||
<Card title="Discord" icon="discord" href="https://discord.gg/aSyA5ZSxpb">
|
||||
Join our Discord server to get help and connect with other users.
|
||||
Get help and talk to other users on our Discord server.
|
||||
</Card>
|
||||
<Card title="Sponsor" icon="heart" href="https://opencollective.com/reactive-resume/donate">
|
||||
Support the development and long-term sustainability of Reactive Resume.
|
||||
Help fund the continued development of Reactive Resume.
|
||||
</Card>
|
||||
</CardGroup>
|
||||
|
||||
|
||||
@@ -1,26 +1,26 @@
|
||||
---
|
||||
title: "Quickstart"
|
||||
description: "Get started with Reactive Resume in minutes by signing in to the hosted version or deploying your own self-hosted instance with Docker Compose."
|
||||
description: "Sign in to the hosted version of Reactive Resume, or deploy your own self-hosted instance with Docker Compose."
|
||||
---
|
||||
|
||||
## Options
|
||||
|
||||
Reactive Resume offers flexibility in how you want to use it. Choose the option that best fits your needs:
|
||||
There are two ways to use Reactive Resume:
|
||||
|
||||
<CardGroup cols={2}>
|
||||
<Card title="Use the Cloud Version" icon="cloud" href="#use-the-cloud-version">
|
||||
The fastest way to get started. **Recommended for most users.**
|
||||
<Card title="Use the Cloud Version" icon="cloud" href="#using-the-cloud-version">
|
||||
The fastest way to get started, and the right choice for most people.
|
||||
</Card>
|
||||
<Card title="Self-Host with Docker" icon="docker" href="#self-host-with-docker">
|
||||
Deploy your own instance with complete control. **Requires some technical knowledge.**
|
||||
Deploy your own instance and keep full control. Requires some technical knowledge.
|
||||
</Card>
|
||||
</CardGroup>
|
||||
|
||||
---
|
||||
|
||||
## Using the Cloud Version
|
||||
## Using the cloud version
|
||||
|
||||
The easiest way to use Reactive Resume is through our cloud version at [rxresu.me](https://rxresu.me). **This service is completely free and will always remain free.**
|
||||
The easiest way to use Reactive Resume is our cloud version at [rxresu.me](https://rxresu.me). It is free, and it will stay free.
|
||||
|
||||
<Steps>
|
||||
<Step title="Create an Account">
|
||||
@@ -33,12 +33,12 @@ The easiest way to use Reactive Resume is through our cloud version at [rxresu.m
|
||||
</Step>
|
||||
|
||||
<Step title="Fill in Your Details">
|
||||
Use our intuitive builder to add your: - Personal information - Work experience - Education - Skills - Projects -
|
||||
And more...
|
||||
Use the builder to add your personal information, work experience, education, skills, projects, and
|
||||
anything else the resume needs.
|
||||
</Step>
|
||||
|
||||
<Step title="Export & Share">
|
||||
When you're ready, export your resume as a PDF or share it via a unique public link.
|
||||
When you're ready, export your resume as a PDF or share it at its public URL.
|
||||
</Step>
|
||||
|
||||
</Steps>
|
||||
@@ -47,9 +47,9 @@ The easiest way to use Reactive Resume is through our cloud version at [rxresu.m
|
||||
|
||||
---
|
||||
|
||||
## Self-Host with Docker
|
||||
## Self-host with Docker
|
||||
|
||||
For users who prefer complete control over their data, you can deploy Reactive Resume on your own infrastructure using Docker.
|
||||
You can deploy Reactive Resume on your own infrastructure using Docker.
|
||||
|
||||
<Info>
|
||||
**From v5.1.0 onwards** — PDF generation now runs entirely client-side via `@react-pdf/renderer`. Self-hosted deployments no longer require Browserless, Chromium, or any external print service as a dependency. The `PRINTER_*` and `BROWSERLESS_*` environment variables are no longer read and can be removed from your `.env`.
|
||||
@@ -64,10 +64,10 @@ Before you begin, ensure you have the following installed:
|
||||
|
||||
<Info>
|
||||
There is <strong>no difference in features</strong> between the cloud-hosted version and the self-hosted option. Both
|
||||
provide the same privacy, customization, and functionality. Choose whichever deployment type suits your needs!
|
||||
offer the same privacy and customization. Pick whichever deployment type suits you.
|
||||
</Info>
|
||||
|
||||
### Quick Deployment
|
||||
### Quick deployment
|
||||
|
||||
<Steps>
|
||||
<Step title="Clone the Repository">
|
||||
@@ -130,7 +130,7 @@ ENCRYPTION_SECRET=your-secure-encryption-secret-here
|
||||
|
||||
</Steps>
|
||||
|
||||
### Docker Compose Services
|
||||
### Docker Compose services
|
||||
|
||||
Here's what each service in the stack does:
|
||||
|
||||
@@ -147,9 +147,9 @@ Here's what each service in the stack does:
|
||||
require S3-compatible storage; local storage rejects private objects.
|
||||
</Note>
|
||||
|
||||
### Health Checks
|
||||
### Health checks
|
||||
|
||||
All services include built-in health checks. You can verify everything is running correctly:
|
||||
All services include health checks. To verify that everything is running:
|
||||
|
||||
```bash
|
||||
docker compose ps
|
||||
@@ -159,11 +159,11 @@ You should see all services with a `healthy` status.
|
||||
|
||||
---
|
||||
|
||||
## Environment Variables Reference
|
||||
## Environment variables reference
|
||||
|
||||
Here's a complete list of environment variables you can configure:
|
||||
A complete list of the environment variables you can configure:
|
||||
|
||||
### Required Variables
|
||||
### Required variables
|
||||
|
||||
| Variable | Description | Example |
|
||||
| -------------- | ------------------------------ | ------------------------------------- |
|
||||
@@ -171,7 +171,7 @@ Here's a complete list of environment variables you can configure:
|
||||
| `AUTH_SECRET` | Secret key for authentication | Generate with `openssl rand -hex 32` |
|
||||
| `APP_URL` | Public URL of your Application | `https://rxresu.me` |
|
||||
|
||||
### Optional Variables
|
||||
### Optional variables
|
||||
|
||||
| Variable | Description | Default |
|
||||
| ------------------------------------- | ----------------------------------------------------------- | ---------------------- |
|
||||
@@ -221,7 +221,7 @@ Here's a complete list of environment variables you can configure:
|
||||
|
||||
---
|
||||
|
||||
## Next Steps
|
||||
## Next steps
|
||||
|
||||
<CardGroup cols={2}>
|
||||
<Card title="Development Setup" icon="code" href="/contributing/development">
|
||||
|
||||
@@ -1,29 +1,25 @@
|
||||
---
|
||||
title: "Accessing the Previous Version"
|
||||
description: "Learn how to access the previous version (v4) of Reactive Resume if you need to retrieve old resumes or prefer the classic experience."
|
||||
title: "Accessing the previous version"
|
||||
description: "Access the previous version (v4) of Reactive Resume to retrieve old resumes, and export them for import into the latest version."
|
||||
---
|
||||
|
||||
## The previous version is still available
|
||||
|
||||
If you've been using Reactive Resume for a while, you may have resumes saved in the previous version of the application. The good news is that **version 4 (v4) is still fully accessible** and will remain online for the foreseeable future.
|
||||
If you've used Reactive Resume for a while, you may have resumes saved in the previous version. Version 4 (v4) is still fully accessible and will remain online for the foreseeable future.
|
||||
|
||||
<Info>The previous version of Reactive Resume is available at [https://v4.rxresu.me](https://v4.rxresu.me).</Info>
|
||||
|
||||
## Why keep the old version running?
|
||||
|
||||
There are several reasons why v4 remains available:
|
||||
|
||||
- **Access to existing resumes**: Users who created resumes in v4 can still access, edit, and export them
|
||||
- **Familiarity**: Some users may prefer the interface they're already comfortable with
|
||||
- **Transition time**: Moving to a new version takes time, and there's no rush
|
||||
Anyone who created resumes in v4 can still open, edit, and export them there. Some people also prefer the interface they already know, and moving to a new version takes time.
|
||||
|
||||
## How long will v4 be available?
|
||||
|
||||
The previous version will continue to run for as long as possible—until the maintainer runs out of breath or funds to keep the server active. There are no immediate plans to shut it down.
|
||||
The previous version will keep running for as long as possible, until the maintainer runs out of breath or funds to keep the server active. There are no immediate plans to shut it down.
|
||||
|
||||
<Warning>
|
||||
While v4 will remain accessible for the foreseeable future, I recommend gradually transitioning to the latest version
|
||||
to benefit from new features, improvements, and ongoing support.
|
||||
v4 will stay accessible for the foreseeable future, but I recommend moving to the latest version when you can. That
|
||||
is where new features and ongoing support land.
|
||||
</Warning>
|
||||
|
||||
## Accessing your v4 resumes
|
||||
@@ -33,17 +29,17 @@ The previous version will continue to run for as long as possible—until the ma
|
||||
Go to [https://v4.rxresu.me](https://v4.rxresu.me) in your browser.
|
||||
</Step>
|
||||
|
||||
<Step title="Log in with your existing credentials">
|
||||
<Step title="Sign in with your existing credentials">
|
||||
Use the same account credentials you used when you originally created your resumes in v4.
|
||||
|
||||
<Tip>
|
||||
If you used social login (Google, GitHub, etc.) in v4, use the same method to sign in.
|
||||
If you used social sign-in (Google, GitHub, etc.) in v4, use the same method to sign in.
|
||||
</Tip>
|
||||
|
||||
</Step>
|
||||
|
||||
<Step title="Access your resumes">
|
||||
Once logged in, you'll find all your previously created resumes in your dashboard, exactly as you left them.
|
||||
Once signed in, you'll find all your previously created resumes in your dashboard, exactly as you left them.
|
||||
</Step>
|
||||
</Steps>
|
||||
|
||||
@@ -53,7 +49,7 @@ If you'd like to move your resumes to the latest version of Reactive Resume, you
|
||||
|
||||
1. In v4, open the resume you want to migrate
|
||||
2. Export it as a JSON file
|
||||
3. In the new version at [https://rxresu.me](https://rxresu.me), create a new account or log in
|
||||
3. In the new version at [https://rxresu.me](https://rxresu.me), create a new account or sign in
|
||||
4. Use the import feature to upload your JSON file (select the "Reactive Resume v4 (JSON)" option)
|
||||
|
||||
<Info>
|
||||
@@ -63,4 +59,4 @@ If you'd like to move your resumes to the latest version of Reactive Resume, you
|
||||
|
||||
## Questions or issues?
|
||||
|
||||
If you encounter any problems accessing v4 or have questions about migrating your resumes, feel free to open an issue on [GitHub](https://github.com/amruthpillai/reactive-resume/issues).
|
||||
If you run into problems accessing v4, or have questions about migrating your resumes, open an issue on [GitHub](https://github.com/amruthpillai/reactive-resume/issues).
|
||||
|
||||
@@ -3,14 +3,14 @@ title: "Adding a cover letter"
|
||||
description: "Learn how to create a cover letter as a custom section in Reactive Resume, format it professionally, and place it on a separate page."
|
||||
---
|
||||
|
||||
A cover letter is a personalized document that accompanies your resume when applying for a job. It introduces you to the employer, highlights your relevant qualifications, and explains why you're a good fit for the position. Reactive Resume lets you create cover letters as custom sections, giving you full control over formatting and placement.
|
||||
A cover letter goes alongside your resume when you apply for a job. It introduces you to the employer, points to your relevant qualifications, and explains why you fit the position. In Reactive Resume you write one as a custom section, so you control its formatting and where it appears.
|
||||
|
||||
## Why include a cover letter?
|
||||
|
||||
- **Stand out**: A well-written cover letter demonstrates genuine interest in the position
|
||||
- **Personalize your application**: Tailor your message to each employer and role
|
||||
- **Explain gaps or transitions**: Address career changes or gaps in your resume
|
||||
- **Show communication skills**: Demonstrate your ability to write clearly and professionally
|
||||
- It shows genuine interest in the position
|
||||
- You can tailor your message to each employer and role
|
||||
- You have room to address career changes or gaps in your resume
|
||||
- It demonstrates that you write clearly and professionally
|
||||
|
||||
## Creating a cover letter section
|
||||
|
||||
@@ -77,13 +77,12 @@ The **Content** field is where you write the body of your cover letter. Include:
|
||||
- **Sign-off**: "Sincerely," followed by your name
|
||||
|
||||
<Info>
|
||||
The recipient and content are both rendered directly on your resume without a section header, giving your cover letter
|
||||
a clean, professional appearance.
|
||||
The recipient and content are both rendered directly on your resume, without a section header.
|
||||
</Info>
|
||||
|
||||
## Using fullscreen mode for writing
|
||||
|
||||
For a distraction-free writing experience, use the fullscreen mode in the rich text editor:
|
||||
The rich text editor can expand to fill the screen when you want to write without distraction:
|
||||
|
||||
<Steps>
|
||||
<Step title="Open the cover letter item">
|
||||
@@ -96,8 +95,7 @@ For a distraction-free writing experience, use the fullscreen mode in the rich t
|
||||
</Step>
|
||||
|
||||
<Step title="Write in fullscreen">
|
||||
The editor will expand to nearly fill your screen, giving you a focused writing environment with all formatting tools
|
||||
available.
|
||||
The editor expands to nearly fill your screen, with every formatting tool still available.
|
||||
</Step>
|
||||
|
||||
<Step title="Exit fullscreen">
|
||||
@@ -107,7 +105,7 @@ For a distraction-free writing experience, use the fullscreen mode in the rich t
|
||||
|
||||
## Formatting options
|
||||
|
||||
The rich text editor supports various formatting options for your cover letter:
|
||||
The rich text editor supports:
|
||||
|
||||
- **Text styling**: Bold, italic, underline, strikethrough, highlight
|
||||
- **Headings**: H1 through H6 (though typically not needed in a cover letter)
|
||||
@@ -140,7 +138,7 @@ If you also want the cover letter to appear on its own page inside the combined
|
||||
</Step>
|
||||
|
||||
<Step title="Verify the layout">
|
||||
Check the preview to ensure your cover letter appears on its own page with proper formatting.
|
||||
Check the preview to confirm your cover letter appears on its own page and is formatted the way you want.
|
||||
</Step>
|
||||
</Steps>
|
||||
|
||||
@@ -154,8 +152,8 @@ If you also want the cover letter to appear on its own page inside the combined
|
||||
</Tip>
|
||||
|
||||
<Tip>
|
||||
**Use the same styling**: Your cover letter will inherit the fonts and colors from your resume template, ensuring a
|
||||
cohesive look.
|
||||
**Use the same styling**: Your cover letter inherits the fonts and colors from your resume template, so both
|
||||
documents match.
|
||||
</Tip>
|
||||
|
||||
<Tip>
|
||||
|
||||
@@ -1,9 +1,9 @@
|
||||
---
|
||||
title: "AI Agent Tools"
|
||||
title: "AI Agent tools"
|
||||
description: "Reference for the tools the Reactive Resume AI Agent can call to read, edit, patch, and preview resume drafts inside an isolated workspace."
|
||||
---
|
||||
|
||||
The AI Agent workspace can use a curated set of tools while it chats with you. You do not call these tools directly; the agent chooses them when your request needs resume data, supported provider web context, attachments, questions, or a resume patch.
|
||||
The AI Agent workspace has a fixed set of tools it can use while it chats with you. You do not call these tools directly. The agent picks them when your request needs resume data, supported provider web context, attachments, questions, or a resume patch.
|
||||
|
||||
## Tool activity in chat
|
||||
|
||||
|
||||
@@ -1,17 +1,17 @@
|
||||
---
|
||||
title: "Checking Service Status"
|
||||
description: "Check the current uptime and incident status for Reactive Resume's hosted servers and learn what to do when the service is experiencing issues."
|
||||
title: "Checking service status"
|
||||
description: "Check the current uptime and incident status for Reactive Resume's hosted servers, and see what to do when the service is down or slow."
|
||||
---
|
||||
|
||||
## Status Page
|
||||
## Status page
|
||||
|
||||
You can monitor the health and availability of Reactive Resume's servers at any time by visiting our status page:
|
||||
You can check the health of Reactive Resume's servers at any time on the status page:
|
||||
|
||||
<Card title="Status Page" icon="signal" href="https://status.rxresu.me">
|
||||
View real-time server metrics including uptime, CPU usage, memory usage, and more.
|
||||
</Card>
|
||||
|
||||
The status page provides information such as:
|
||||
The status page shows:
|
||||
|
||||
- **Uptime**: How long the servers have been running without interruption
|
||||
- **CPU Usage**: Current processor utilization
|
||||
@@ -20,9 +20,9 @@ The status page provides information such as:
|
||||
|
||||
---
|
||||
|
||||
## What to Do If Servers Are Down
|
||||
## What to do if servers are down
|
||||
|
||||
If you notice the servers are experiencing high load or downtime, here are some recommendations:
|
||||
If the servers are under high load or unreachable:
|
||||
|
||||
<Steps>
|
||||
<Step title="Check the status page">
|
||||
@@ -30,7 +30,7 @@ If you notice the servers are experiencing high load or downtime, here are some
|
||||
</Step>
|
||||
|
||||
<Step title="Wait and try again later">
|
||||
If the servers are under heavy load, the best course of action is to wait a bit and try again later. Peak usage times can cause temporary slowdowns.
|
||||
If the servers are under heavy load, wait a while and try again. Peak usage times can cause temporary slowdowns.
|
||||
|
||||
<Info>
|
||||
Reactive Resume is a **free, open-source service** used by thousands of people worldwide. During peak times, the servers may experience higher than usual load.
|
||||
@@ -45,26 +45,22 @@ If you notice the servers are experiencing high load or downtime, here are some
|
||||
|
||||
---
|
||||
|
||||
## A Note on Server Capacity
|
||||
## A note on server capacity
|
||||
|
||||
<Warning>
|
||||
Reactive Resume is a **free service** that runs on limited server resources. As an open-source project maintained by a
|
||||
single developer, it's not feasible to invest in powerful dedicated servers without community support.
|
||||
</Warning>
|
||||
|
||||
The reality is:
|
||||
Thousands of people use the service every day. Because it is free and has no venture funding behind it, server capacity stays constrained.
|
||||
|
||||
- **High demand**: Thousands of users rely on this service daily
|
||||
- **Limited resources**: As a free service, server capacity is constrained
|
||||
- **No corporate backing**: This isn't a venture-funded startup with unlimited cloud budgets
|
||||
|
||||
If you find Reactive Resume valuable and want to help keep the servers running smoothly (and maybe even help scale them up), please consider supporting the project.
|
||||
If Reactive Resume is useful to you and you want to help keep the servers running (and maybe scale them up), consider supporting the project.
|
||||
|
||||
---
|
||||
|
||||
## Support the Project
|
||||
## Support the project
|
||||
|
||||
Your donations directly help cover server costs, improve infrastructure, and keep Reactive Resume free for everyone.
|
||||
Donations go directly toward server costs, better infrastructure, and keeping Reactive Resume free for everyone.
|
||||
|
||||
<Card title="Donate on Open Collective" icon="heart" href="https://opencollective.com/reactive-resume/donate">
|
||||
Support Reactive Resume's development and server costs through Open Collective. Every contribution helps keep the
|
||||
@@ -82,16 +78,12 @@ Your donations directly help cover server costs, improve infrastructure, and kee
|
||||
|
||||
---
|
||||
|
||||
## Self-Hosting as an Alternative
|
||||
## Self-hosting as an alternative
|
||||
|
||||
If you need guaranteed uptime or want to avoid shared server limitations, you can always self-host Reactive Resume on your own infrastructure.
|
||||
If you need guaranteed uptime, or want to avoid the limits of a shared server, you can self-host Reactive Resume on your own infrastructure.
|
||||
|
||||
<Card title="Self-Hosting Guide" icon="server" href="/self-hosting/docker">
|
||||
Learn how to deploy Reactive Resume on your own servers using Docker.
|
||||
</Card>
|
||||
|
||||
Self-hosting gives you:
|
||||
|
||||
- **Full control** over your data and infrastructure
|
||||
- **Guaranteed availability** based on your own server capacity
|
||||
- **No shared resources** with other users
|
||||
Self-hosting gives you full control over your data and infrastructure, availability that depends only on your own server capacity, and no resources shared with other users.
|
||||
|
||||
@@ -3,11 +3,11 @@ title: "Choosing a template"
|
||||
description: "Compare the built-in Reactive Resume templates, preview each layout, and switch between them from the builder to pick the best design for your resume."
|
||||
---
|
||||
|
||||
Reactive Resume offers a variety of unique templates, each with its own design aesthetic. This guide will help you understand the differences between templates and how to change your resume's template at any time.
|
||||
Reactive Resume includes many templates, each with its own design. This guide covers how they differ and how to switch between them.
|
||||
|
||||
## How to change your template
|
||||
|
||||
Changing your resume template is simple and can be done at any time without losing any of your content.
|
||||
You can change templates at any time without losing your content.
|
||||
|
||||
<Steps>
|
||||
<Step title="Open your resume in the builder">
|
||||
@@ -33,7 +33,7 @@ Changing your resume template is simple and can be done at any time without losi
|
||||
</Step>
|
||||
|
||||
<Step title="Select your new template">
|
||||
Browse through the available templates and click on the one you want to use. Your resume will instantly update to reflect the new design.
|
||||
Browse the available templates and click the one you want. Your resume updates immediately.
|
||||
|
||||
<Frame caption="Screenshot of selecting a new template from the gallery">
|
||||
<img src="/images/guides/choosing-a-template/screenshot-3.webp" alt="Screenshot of selecting a new template from the gallery" />
|
||||
@@ -66,7 +66,7 @@ Changing your resume template is simple and can be done at any time without losi
|
||||
</Accordion>
|
||||
|
||||
<Accordion title="Think about content length" icon="ruler">
|
||||
If you have a lot of experience to showcase, choose a template with efficient space usage. For shorter resumes,
|
||||
If you have a lot of experience to fit, choose a template that uses space efficiently. For shorter resumes,
|
||||
templates with more white space can make your content feel more substantial.
|
||||
</Accordion>
|
||||
|
||||
@@ -84,11 +84,10 @@ Changing your resume template is simple and can be done at any time without losi
|
||||
|
||||
## Available templates
|
||||
|
||||
Reactive Resume includes a variety of professionally designed templates. Each template can be further customized with your choice of colors, fonts, and layout options.
|
||||
Each template can be customized further with your choice of colors, fonts, and layout options.
|
||||
|
||||
<Info>
|
||||
All templates support the same features and sections. The difference is purely in how they present your information
|
||||
visually.
|
||||
All templates support the same features and sections. They differ only in how they present your information.
|
||||
</Info>
|
||||
|
||||
<div className="grid grid-cols-1 sm:grid-cols-2 gap-4">
|
||||
@@ -157,7 +156,7 @@ Reactive Resume includes a variety of professionally designed templates. Each te
|
||||
|
||||
## Customizing your template
|
||||
|
||||
After selecting a template, you can customize it further:
|
||||
After selecting a template, you can adjust:
|
||||
|
||||
| Setting | Description |
|
||||
| -------------- | ------------------------------------------------------------ |
|
||||
|
||||
@@ -26,19 +26,19 @@ description: "Sign up for a Reactive Resume account with email and password or s
|
||||
|
||||
</Step>
|
||||
|
||||
<Step title="Sign up and log in">
|
||||
After filling in all the required fields, click the **Sign Up** button. You will be immediately logged in and can start using Reactive Resume right away.
|
||||
<Step title="Sign up and sign in">
|
||||
After filling in all the required fields, click the **Sign up** button. You will be signed in immediately and can start using Reactive Resume right away.
|
||||
|
||||
<Tip>
|
||||
No email verification is required to get started. However, it is highly recommended to verify your email address for account security.
|
||||
No email verification is required to get started, but verifying your email is strongly recommended for account security.
|
||||
</Tip>
|
||||
</Step>
|
||||
|
||||
<Step title="Verify your email (recommended)">
|
||||
While email verification is optional, it is strongly recommended to verify your email address. This helps in:
|
||||
Email verification is optional, but strongly recommended. Verifying your email:
|
||||
|
||||
- **Securing your account**: Ensures you have access to the email address associated with your account
|
||||
- **Password recovery**: Allows you to reset your password, in case you forget it
|
||||
- confirms you have access to the address on the account
|
||||
- lets you reset your password if you forget it
|
||||
|
||||
<Info>
|
||||
You can verify your email at any time from your account settings. Look for the verification prompt in your dashboard or navigate to **Settings → Profile**.
|
||||
@@ -56,7 +56,7 @@ description: "Sign up for a Reactive Resume account with email and password or s
|
||||
|
||||
---
|
||||
|
||||
## Account Security Tips
|
||||
## Account security tips
|
||||
|
||||
<CardGroup cols={2}>
|
||||
<Card title="Use a strong password" icon="lock">
|
||||
@@ -72,19 +72,17 @@ description: "Sign up for a Reactive Resume account with email and password or s
|
||||
## Troubleshooting
|
||||
|
||||
<AccordionGroup>
|
||||
<Accordion title="Username Already Taken">
|
||||
If you see an error that your username is already taken, try a different variation. Usernames must be unique across
|
||||
all users.
|
||||
<Accordion title="Username already taken">
|
||||
If your username is already taken, try a different variation. Usernames must be unique across all users.
|
||||
</Accordion>
|
||||
|
||||
<Accordion title="Email Already Registered">
|
||||
<Accordion title="Email already registered">
|
||||
If your email is already registered, you can use the **Forgot Password** link on the login page to reset your
|
||||
password and regain access to your account.
|
||||
</Accordion>
|
||||
|
||||
<Accordion title="Didn't Receive Verification Email">
|
||||
Check your spam folder first. If you still don't see it, you can request a new verification email from your account
|
||||
settings.
|
||||
<Accordion title="Didn't receive the verification email">
|
||||
Check your spam folder first. If it isn't there, request a new verification email from your account settings.
|
||||
</Accordion>
|
||||
|
||||
</AccordionGroup>
|
||||
|
||||
@@ -4,17 +4,17 @@ description: "Create your first resume in Reactive Resume by naming it, choosing
|
||||
---
|
||||
|
||||
<Steps>
|
||||
<Step title="Log in to your account">
|
||||
Head over to [https://rxresu.me](https://rxresu.me) and log in with your account credentials.
|
||||
<Step title="Sign in to your account">
|
||||
Head over to [https://rxresu.me](https://rxresu.me) and sign in with your account credentials.
|
||||
|
||||
<Tip>
|
||||
If you haven't created an account yet, follow the guide on [Creating an Account](/guides/creating-an-account).
|
||||
If you haven't created an account yet, follow the guide on [Creating an account](/guides/creating-an-account).
|
||||
</Tip>
|
||||
|
||||
</Step>
|
||||
|
||||
<Step title="Open the Resumes Dashboard">
|
||||
After logging in, navigate to your Dashboard where all of your resumes live.
|
||||
After signing in, go to your Dashboard, where all of your resumes live.
|
||||
|
||||
<Info>
|
||||
This is where you can create, import, organize, and manage multiple resumes for different roles or versions.
|
||||
@@ -34,10 +34,10 @@ description: "Create your first resume in Reactive Resume by naming it, choosing
|
||||
</Step>
|
||||
|
||||
<Step title="Name your resume">
|
||||
Fill in the resume name. This can be a generic name (e.g., “General Resume”) or something tied to the position you’re applying for.
|
||||
Fill in the resume name. This can be generic (e.g., "General Resume") or tied to the position you're applying for.
|
||||
|
||||
<Tip>
|
||||
If you can’t think of a name yet, click the magic wand button to generate a random name for you.
|
||||
If you can't think of a name yet, click the magic wand button to generate one.
|
||||
</Tip>
|
||||
|
||||
</Step>
|
||||
@@ -64,7 +64,7 @@ description: "Create your first resume in Reactive Resume by naming it, choosing
|
||||
Click **Create** to start with an empty resume, or open the split-button menu and choose **Create a Sample Resume** to start with sample content.
|
||||
|
||||
<Tip>
|
||||
A sample resume is useful when you want to explore templates, layout controls, and exports before entering your own
|
||||
A sample resume is useful when you want to try templates, layout controls, and exports before entering your own
|
||||
information.
|
||||
</Tip>
|
||||
|
||||
|
||||
@@ -18,7 +18,7 @@ Before you delete your account, you can download a copy of everything Reactive R
|
||||
</Step>
|
||||
</Steps>
|
||||
|
||||
Keep this archive in a safe place — it's the easiest way to restore your resumes if you delete your account and later change your mind.
|
||||
Keep this archive somewhere safe. It's the easiest way to restore your resumes if you delete your account and later change your mind.
|
||||
|
||||
## Delete your account
|
||||
|
||||
@@ -32,8 +32,7 @@ Keep this archive in a safe place — it's the easiest way to restore your resum
|
||||
</Step>
|
||||
|
||||
<Step title="Navigate to Danger Zone">
|
||||
Once you're in the dashboard, look for the sidebar navigation on the left. Under the <Badge>Settings</Badge> section,
|
||||
click on <Badge>Danger Zone</Badge>.
|
||||
In the dashboard sidebar on the left, under <Badge>Settings</Badge>, click the <Badge>Danger Zone</Badge> link.
|
||||
</Step>
|
||||
|
||||
<Step title="Type the confirmation text">
|
||||
|
||||
@@ -45,7 +45,7 @@ If your resume includes a [cover letter section](/guides/adding-a-cover-letter),
|
||||
- The **Resume** tab exports only your resume content and excludes cover letter sections.
|
||||
- The **Cover letter** tab exports only visible cover letter sections, rendered full width on their own page.
|
||||
|
||||
You no longer need to reorder pages or hide sections manually to produce a resume-only or cover-letter-only PDF. Select the tab that matches what you want, then pick a format.
|
||||
You do not need to reorder pages or hide sections by hand to produce a resume-only or cover-letter-only PDF. Select the tab that matches what you want, then pick a format.
|
||||
|
||||
<Info>
|
||||
The **Cover letter** tab is disabled when the resume has no cover letter section, or when every cover letter section or item is hidden.
|
||||
|
||||
@@ -3,7 +3,7 @@ title: "Fitting content on a page"
|
||||
description: "Reorganize sections, tune typography, adjust margins, and trim content to fit your Reactive Resume on a single A4 or Letter page without overflow."
|
||||
---
|
||||
|
||||
When your resume content overflows the page, Reactive Resume displays a warning just below the page. This guide explains how to reorganize and adjust your content so everything fits within your chosen page format.
|
||||
When your resume content overflows the page, Reactive Resume shows a warning just below the page. This guide covers how to reorganize and trim your content so everything fits your chosen page format.
|
||||
|
||||
<Frame caption="Screenshot of the overflow warning message in the resume builder">
|
||||
<img
|
||||
@@ -20,24 +20,23 @@ When your resume content overflows the page, Reactive Resume displays a warning
|
||||
|
||||
## Quick fixes
|
||||
|
||||
Here are several ways to fit your content within a page, ordered from simplest to most involved.
|
||||
The fixes below are ordered from simplest to most involved.
|
||||
|
||||
### 1. Switch to Free-Form format
|
||||
|
||||
If you don't plan on printing your resume, the simplest solution is to switch to **Free-Form** format. Free-Form creates a single continuous page with no height limit, eliminating overflow concerns entirely.
|
||||
If you don't plan on printing your resume, switch to **Free-Form** format. Free-Form creates a single continuous page with no height limit, so nothing can overflow.
|
||||
|
||||
With Free-Form:
|
||||
|
||||
- Your entire resume renders as one seamless document
|
||||
- No awkward page breaks to manage
|
||||
- ATS parsers and AI scanners can still read your content perfectly
|
||||
- You focus on content, not arbitrary page constraints
|
||||
- Your resume renders as one continuous document
|
||||
- There are no page breaks to manage
|
||||
- ATS parsers and AI scanners can still read your content
|
||||
- You can focus on the content instead of page limits
|
||||
|
||||
To switch formats, go to the **Page** section in the right sidebar and change the **Format** to Free-Form. For more details, see [Selecting the right page format](/guides/selecting-page-format).
|
||||
|
||||
<Tip>
|
||||
Since most resumes are viewed digitally today, Free-Form is often the best choice unless you specifically need to
|
||||
print physical copies.
|
||||
Most resumes are read on a screen, so Free-Form is often the best choice unless you need printed copies.
|
||||
</Tip>
|
||||
|
||||
### 2. Shorten text blocks
|
||||
@@ -121,16 +120,16 @@ Open the right sidebar and explore these options:
|
||||
|
||||
If you're still short on space, consider hiding sections that aren't essential for your target role:
|
||||
|
||||
- **Interests** — Nice to have, but rarely a deciding factor
|
||||
- **References** — "Available upon request" is assumed; you don't need to list them
|
||||
- **Older certifications** — Keep only those relevant to the job
|
||||
- **Volunteer work** — Include only if it strengthens your application
|
||||
- **Interests**: nice to have, but rarely a deciding factor
|
||||
- **References**: "Available upon request" is assumed, so you don't need to list them
|
||||
- **Older certifications**: keep only the ones relevant to the job
|
||||
- **Volunteer work**: include only if it strengthens your application
|
||||
|
||||
To hide a section, click on the section heading in the left sidebar and toggle the **Hidden** switch.
|
||||
|
||||
## Finding the right balance
|
||||
|
||||
If you need to stick with A4 or Letter format, start with content changes (steps 2-4) before adjusting design settings (steps 5-6). The best resumes fit their content naturally rather than forcing everything into a cramped layout.
|
||||
If you need to stick with A4 or Letter format, start with content changes (steps 2-4) before adjusting design settings (steps 5-6). A resume that fits its content reads better than one crammed into the space.
|
||||
|
||||
Try this order:
|
||||
|
||||
@@ -141,7 +140,7 @@ Try this order:
|
||||
5. Fine-tune font size and spacing last
|
||||
|
||||
<Tip>
|
||||
Use the live preview to see changes as you make them. Small adjustments add up—reducing font size by 0.5pt combined
|
||||
Use the live preview to see changes as you make them. Small adjustments add up. Reducing font size by 0.5pt along
|
||||
with slightly smaller margins can recover enough space for several lines of content.
|
||||
</Tip>
|
||||
|
||||
|
||||
@@ -17,14 +17,14 @@ Reactive Resume can create a new resume from several existing file formats. Use
|
||||
|
||||
<Info>
|
||||
PDF and Word imports depend on your AI settings because those formats are not structured resume data. Configure AI in
|
||||
**Dashboard -> Settings -> Integrations** before using those import types.
|
||||
**Dashboard → Settings → Integrations** before using those import types.
|
||||
</Info>
|
||||
|
||||
## Import a resume
|
||||
|
||||
<Steps>
|
||||
<Step title="Open the Resumes dashboard">
|
||||
Sign in and go to **Dashboard -> Resumes**.
|
||||
Sign in and go to **Dashboard → Resumes**.
|
||||
</Step>
|
||||
|
||||
<Step title="Open the import dialog">
|
||||
@@ -71,7 +71,7 @@ If you only have a PDF or Word document, choose **PDF** or **Microsoft Word**. A
|
||||
|
||||
### The PDF or Word import says AI must be enabled
|
||||
|
||||
Open **Dashboard -> Settings -> Integrations**, fill in your AI provider settings, test the connection, and enable AI features.
|
||||
Open **Dashboard → Settings → Integrations**, fill in your AI provider settings, test the connection, and enable AI features.
|
||||
|
||||
### The imported resume is incomplete
|
||||
|
||||
|
||||
@@ -1,13 +1,13 @@
|
||||
---
|
||||
title: "JSON Resume Schema"
|
||||
description: "Learn about the Reactive Resume JSON Schema, available at /schema.json, and how it aims to become the gold standard for portable resume data."
|
||||
title: "JSON Resume schema"
|
||||
description: "The Reactive Resume JSON Schema, published at /schema.json: what it covers, how to validate resume data against it, and how to build on it."
|
||||
---
|
||||
|
||||
## The Vision
|
||||
## The vision
|
||||
|
||||
I envision a world where applying for a job is as simple as transferring a JSON file from one service to a job listing portal—without any parsing errors, format inconsistencies, or human bias from subjective resume formatting.
|
||||
I want applying for a job to be as simple as sending a JSON file from one service to a job listing portal, without parsing errors, format inconsistencies, or bias from how a resume happens to be laid out.
|
||||
|
||||
Reactive Resume aims to be the **gold standard in JSON Resume Schemas**. A universal, well-documented, and rigorously typed schema that any service can adopt to enable seamless resume portability across the entire job application ecosystem.
|
||||
Reactive Resume aims to be the gold standard in JSON resume schemas: one documented, strictly typed schema that any service can adopt so resumes move between tools without loss.
|
||||
|
||||
Imagine:
|
||||
|
||||
@@ -18,20 +18,20 @@ Imagine:
|
||||
|
||||
This is the future I'm hoping to build toward.
|
||||
|
||||
## The Schema Endpoint
|
||||
## The schema endpoint
|
||||
|
||||
The Reactive Resume JSON Schema is publicly available at:
|
||||
|
||||
<Info>[https://rxresu.me/schema.json](https://rxresu.me/schema.json)</Info>
|
||||
|
||||
This endpoint returns a complete JSON Schema using the draft 2020-12 dialect. It describes the structure of a Reactive Resume document and includes:
|
||||
The endpoint returns a complete JSON Schema in the draft 2020-12 dialect. It describes the structure of a Reactive Resume document and covers:
|
||||
|
||||
- **All resume sections**: basics, summary, experience, education, projects, skills, languages, interests, awards, certifications, publications, volunteer work, and references
|
||||
- **Custom sections**: user-defined sections whose `type` selects one of the documented item shapes
|
||||
- **Metadata**: template, layout, typography, colors, page settings, and custom CSS
|
||||
- **Full descriptions**: every field is documented with its purpose and expected format
|
||||
|
||||
## Schema Dialect and Document Shape
|
||||
## Schema dialect and document shape
|
||||
|
||||
The schema document declares its JSON Schema dialect in its own `$schema` field:
|
||||
|
||||
@@ -45,9 +45,9 @@ The schema document declares its JSON Schema dialect in its own `$schema` field:
|
||||
Resume documents do not include a top-level `version` property. They also do not include the schema document's
|
||||
`$schema` field. Validate the exported resume object directly against the canonical schema endpoint.
|
||||
|
||||
## Using the Schema
|
||||
## Using the schema
|
||||
|
||||
### Validating Resume Data
|
||||
### Validating resume data
|
||||
|
||||
You can use the schema to validate resume JSON files in any language that supports JSON Schema validation:
|
||||
|
||||
@@ -64,7 +64,7 @@ if (!isValid) {
|
||||
}
|
||||
```
|
||||
|
||||
### IDE Autocompletion
|
||||
### IDE autocompletion
|
||||
|
||||
Associate exported resume files with the canonical schema in VS Code's `settings.json`:
|
||||
|
||||
@@ -81,7 +81,7 @@ Associate exported resume files with the canonical schema in VS Code's `settings
|
||||
|
||||
This keeps editor configuration outside the resume data and avoids adding unsupported top-level properties.
|
||||
|
||||
### Building Integrations
|
||||
### Building integrations
|
||||
|
||||
The schema enables third-party integrations:
|
||||
|
||||
@@ -90,7 +90,7 @@ The schema enables third-party integrations:
|
||||
- **Other resume builders** can import/export using a common format
|
||||
- **AI tools** can understand resume structure for analysis or enhancement
|
||||
|
||||
## Schema Structure Overview
|
||||
## Schema structure overview
|
||||
|
||||
The resume data is organized into these top-level sections:
|
||||
|
||||
@@ -130,22 +130,22 @@ Each section within `sections` follows a consistent structure:
|
||||
}
|
||||
```
|
||||
|
||||
## For Developers & Job Portals
|
||||
## For developers and job portals
|
||||
|
||||
If you're building a job portal, HR system, or any service that handles resumes, I encourage you to adopt this schema. Benefits include:
|
||||
If you're building a job portal, HR system, or any other service that handles resumes, I'd encourage you to adopt this schema:
|
||||
|
||||
- **Zero parsing errors**: structured data means no OCR or PDF parsing mistakes
|
||||
- **Complete information**: all resume data is preserved, including links and metadata
|
||||
- **Easy integration**: JSON is universally supported across all platforms
|
||||
- **Canonical contract**: one public schema endpoint tracks the current Reactive Resume data model
|
||||
|
||||
Want to integrate? The schema is open and freely available. You can fetch it programmatically or reference it in your systems.
|
||||
The schema is open and free to use. Fetch it programmatically, or reference it by URL from your own systems.
|
||||
|
||||
## Complete JSON Schema
|
||||
|
||||
Below is the complete JSON Schema for Reactive Resume. You can also fetch the latest version directly from [https://rxresu.me/schema.json](https://rxresu.me/schema.json).
|
||||
The full JSON Schema for Reactive Resume follows. You can also fetch the latest version directly from [https://rxresu.me/schema.json](https://rxresu.me/schema.json).
|
||||
|
||||
<Tip>Copy the schema from the live endpoint to ensure you always have the latest version.</Tip>
|
||||
<Tip>Copy the schema from the live endpoint so you always have the latest version.</Tip>
|
||||
|
||||
<!-- RESUME-JSON-SCHEMA:START -->
|
||||
```json /schema.json lines expandable
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: "Linking social accounts"
|
||||
description: "Connect or disconnect social sign-in providers like Google and GitHub to your Reactive Resume account so you can log in without a password."
|
||||
description: "Connect or disconnect social sign-in providers like Google and GitHub to your Reactive Resume account so you can sign in without a password."
|
||||
---
|
||||
|
||||
<Steps>
|
||||
@@ -9,8 +9,7 @@ description: "Connect or disconnect social sign-in providers like Google and Git
|
||||
</Step>
|
||||
|
||||
<Step title="Navigate to Authentication settings">
|
||||
Once you're in the dashboard, look for the sidebar navigation on the left. Under the <Badge>Settings</Badge> section,
|
||||
click on the <Badge>Authentication</Badge> link.
|
||||
In the dashboard sidebar on the left, under <Badge>Settings</Badge>, click the <Badge>Authentication</Badge> link.
|
||||
</Step>
|
||||
|
||||
<Step title="Find the social provider you want to link">
|
||||
|
||||
@@ -9,7 +9,7 @@ Use this guide when you want an AI client to manage the **Application Tracker**
|
||||
|
||||
<Steps>
|
||||
<Step title="Connect the MCP server">
|
||||
Follow [Using the MCP Server](/guides/using-the-mcp-server) to connect your MCP client with OAuth or an API key.
|
||||
Follow [Using the MCP server](/guides/using-the-mcp-server) to connect your MCP client with OAuth or an API key.
|
||||
</Step>
|
||||
|
||||
<Step title="Confirm the application tools are visible">
|
||||
@@ -27,7 +27,7 @@ Use this guide when you want an AI client to manage the **Application Tracker**
|
||||
|
||||
## Start with a pipeline review
|
||||
|
||||
Begin by asking the agent to inspect your current pipeline. This gives the agent valid application IDs and avoids duplicate records.
|
||||
Have the agent inspect your current pipeline first. That gives it valid application IDs and avoids duplicate records.
|
||||
|
||||
```text
|
||||
List my active applications grouped by stage. Include company, role, tags, follow-up date, linked resume name, and whether a resume or cover-letter PDF is attached.
|
||||
|
||||
@@ -3,13 +3,13 @@ title: "Moving items between sections"
|
||||
description: "Move resume items between sections or across pages in the Reactive Resume builder to reorganize content and split lengthy sections cleanly."
|
||||
---
|
||||
|
||||
If you have a long work history or extensive project list, you may want to split items across multiple pages or reorganize them into different sections. The **Move to** feature lets you do exactly that—quickly relocate any item to another section or page with just a few clicks.
|
||||
If you have a long work history or a long list of projects, you may want to split items across multiple pages or reorganize them into different sections. The **Move to** feature relocates any item to another section or page.
|
||||
|
||||
## Why move items?
|
||||
|
||||
- **Split lengthy sections**: If your Experience section spans more than one page, you can move older roles to a custom section on page 2.
|
||||
- **Reorganize content**: Move a project from "Projects" to a custom "Open Source" section, or relocate a skill to a different grouping.
|
||||
- **Fine-tune page layout**: Control exactly which items appear on which page for a polished, balanced resume.
|
||||
- Split long sections. If your Experience section spans more than one page, move older roles to a custom section on page 2.
|
||||
- Reorganize content. Move a project from "Projects" to a custom "Open Source" section, or a skill to a different grouping.
|
||||
- Control the page layout. Choose exactly which items appear on which page.
|
||||
|
||||
## How to move an item
|
||||
|
||||
@@ -60,7 +60,7 @@ If you have a long work history or extensive project list, you may want to split
|
||||
</Frame>
|
||||
|
||||
<Tip>
|
||||
If a custom section of the same type doesn't exist on your target page, Reactive Resume will **automatically create one** for you. This makes it easy to split sections across pages without manual setup.
|
||||
If a custom section of the same type doesn't exist on your target page, Reactive Resume creates one for you, so you can split a section across pages without setting it up first.
|
||||
</Tip>
|
||||
|
||||
</Step>
|
||||
@@ -78,9 +78,9 @@ If you have a long work history or extensive project list, you may want to split
|
||||
</Step>
|
||||
</Steps>
|
||||
|
||||
## Example: Splitting Work Experience across pages
|
||||
## Example: splitting work experience across pages
|
||||
|
||||
A common use case is when your work history is too long to fit on a single page. Here's how to handle it:
|
||||
A common case is a work history that is too long to fit on a single page.
|
||||
|
||||
<Steps>
|
||||
<Step title="Identify items to move">
|
||||
@@ -113,18 +113,18 @@ A common use case is when your work history is too long to fit on a single page.
|
||||
## Tips for organizing multi-page resumes
|
||||
|
||||
<Tip>
|
||||
**Keep it logical**: Maintain chronological order within each page. Move complete job entries rather than splitting a
|
||||
single role across pages.
|
||||
Keep chronological order within each page, and move complete job entries rather than splitting a single role across
|
||||
pages.
|
||||
</Tip>
|
||||
|
||||
<Tip>
|
||||
**Use custom section names**: After moving items to a new custom section, you can rename it (e.g., "Earlier
|
||||
Experience" or "Additional Projects") to provide context for recruiters.
|
||||
After moving items to a new custom section, rename it (e.g., "Earlier Experience" or "Additional Projects") so
|
||||
recruiters know what they are looking at.
|
||||
</Tip>
|
||||
|
||||
<Warning>
|
||||
Moving items reorganizes your content but doesn't affect the data itself. You can always move items back or to
|
||||
different sections as needed.
|
||||
Moving items reorganizes your content but doesn't change the data itself. You can always move items back, or to a
|
||||
different section.
|
||||
</Warning>
|
||||
|
||||
## Troubleshooting
|
||||
@@ -135,7 +135,7 @@ Make sure you're clicking the dropdown menu on a **section item** (like an indiv
|
||||
|
||||
### The destination I want isn't listed
|
||||
|
||||
The Move to submenu shows destinations compatible with the item type. For example, an Experience item can only be moved to other Experience-type sections. If you need to change an item's type entirely, you may need to recreate it in the desired section.
|
||||
The Move to submenu shows destinations compatible with the item type. For example, an Experience item can only be moved to other Experience-type sections. If you need to change an item's type entirely, recreate it in the section you want.
|
||||
|
||||
### My custom section wasn't created
|
||||
|
||||
|
||||
@@ -3,7 +3,7 @@ title: "Selecting the right page format"
|
||||
description: "Compare the A4, Letter, and Free-Form page format options in Reactive Resume and pick the right size, margins, and orientation for your resume."
|
||||
---
|
||||
|
||||
Reactive Resume offers three page format options: **A4**, **Letter**, and **Free-Form**. Each format affects how your resume is rendered and exported as a PDF. This guide explains the differences and helps you choose the right format for your situation.
|
||||
Reactive Resume has three page formats: **A4**, **Letter**, and **Free-Form**. The format you pick changes how your resume is rendered and exported as a PDF.
|
||||
|
||||
## Available formats
|
||||
|
||||
@@ -31,7 +31,7 @@ Choose Letter if you're applying to jobs in North America.
|
||||
|
||||
### Free-Form
|
||||
|
||||
Free-Form is a modern format designed for digital-first resumes. Instead of conforming to a physical page size, Free-Form produces a **single continuous page** with no height limit. The width matches A4 (210mm), but the height extends as needed to fit all your content.
|
||||
Free-Form is built for resumes that are only read on a screen. Instead of matching a physical page size, it produces a **single continuous page** with no height limit. The width matches A4 (210mm), and the height extends to fit all your content.
|
||||
|
||||
| Property | Value |
|
||||
| -------- | ------------- |
|
||||
@@ -39,26 +39,26 @@ Free-Form is a modern format designed for digital-first resumes. Instead of conf
|
||||
| Height | Unlimited |
|
||||
|
||||
<Info>
|
||||
With Free-Form, there are no page breaks. Your entire resume renders as one seamless document, regardless of how much
|
||||
content you have.
|
||||
With Free-Form, there are no page breaks. Your resume renders as one continuous document, no matter how much content
|
||||
you have.
|
||||
</Info>
|
||||
|
||||
## Why Free-Form exists
|
||||
|
||||
The reality of modern job applications is that **nobody prints resumes anymore**. Your resume is almost always viewed digitally—on a screen, in an applicant tracking system (ATS), or parsed by AI-powered screening tools.
|
||||
Most resumes are never printed. Yours is almost always read digitally: on a screen, in an applicant tracking system (ATS), or by an AI screening tool.
|
||||
|
||||
When your resume is processed digitally:
|
||||
|
||||
- **ATS parsers** extract text content regardless of page dimensions
|
||||
- **AI scanners** analyze the full document as a single unit
|
||||
- **Recruiters** scroll through PDFs on their screens rather than printing them
|
||||
- **PDF parsing tools** read the entire content regardless of page height
|
||||
- ATS parsers extract the text regardless of page dimensions
|
||||
- AI scanners analyze the full document as a single unit
|
||||
- Recruiters scroll through PDFs on their screens rather than printing them
|
||||
- PDF parsing tools read the whole file regardless of page height
|
||||
|
||||
Since physical page constraints no longer matter for most use cases, Free-Form lets you focus on content rather than worrying about fitting everything into arbitrary page limits.
|
||||
Since physical page limits no longer apply in those cases, Free-Form lets you focus on the content instead of fitting it into a fixed page height.
|
||||
|
||||
<Tip>
|
||||
If you don't plan on printing your resume, Free-Form is often the simplest choice. You never have to worry about
|
||||
content overflowing or awkward page breaks.
|
||||
If you don't plan on printing your resume, Free-Form is usually the simplest choice. Nothing overflows, and there are
|
||||
no awkward page breaks.
|
||||
</Tip>
|
||||
|
||||
## How to change your page format
|
||||
@@ -69,7 +69,7 @@ Since physical page constraints no longer matter for most use cases, Free-Form l
|
||||
</Step>
|
||||
|
||||
<Step title="Open the right sidebar">
|
||||
In the resume builder, look for the right sidebar on the right side of the screen.
|
||||
The sidebar sits on the right edge of the resume builder.
|
||||
</Step>
|
||||
|
||||
<Step title="Navigate to the Page section">
|
||||
@@ -92,8 +92,6 @@ Since physical page constraints no longer matter for most use cases, Free-Form l
|
||||
|
||||
## Choosing the right format
|
||||
|
||||
Use this quick reference to decide which format fits your needs:
|
||||
|
||||
| Situation | Recommended Format |
|
||||
| --------------------------------------- | ------------------ |
|
||||
| Applying to jobs in North America | Letter |
|
||||
@@ -105,8 +103,8 @@ Use this quick reference to decide which format fits your needs:
|
||||
| Traditional industries (law, finance) | A4 or Letter |
|
||||
|
||||
<Warning>
|
||||
If you switch from Free-Form to A4 or Letter, your content will be split across multiple pages. Review the result
|
||||
carefully to ensure page breaks don't occur in awkward places.
|
||||
If you switch from Free-Form to A4 or Letter, your content is split across multiple pages. Review the result and
|
||||
check that the page breaks don't fall in awkward places.
|
||||
</Warning>
|
||||
|
||||
## Example PDFs
|
||||
@@ -138,17 +136,17 @@ Download these sample resumes to see how different formats affect the final PDF
|
||||
|
||||
<AccordionGroup>
|
||||
<Accordion title="Does Free-Form work with ATS systems?">
|
||||
Yes. ATS systems parse the text content of your PDF, not the page dimensions. Free-Form resumes are fully compatible with applicant tracking systems.
|
||||
Yes. An ATS parses the text in your PDF, not the page dimensions. Free-Form resumes work with applicant tracking systems.
|
||||
</Accordion>
|
||||
|
||||
<Accordion title="Can I switch formats after creating my resume?">
|
||||
Absolutely. You can change the format at any time from the Page section in the right sidebar. Your content is
|
||||
preserved—only the layout changes.
|
||||
Yes. You can change the format at any time from the Page section in the right sidebar. Your content is preserved.
|
||||
Only the layout changes.
|
||||
</Accordion>
|
||||
|
||||
<Accordion title="What if a job posting asks for a 'one-page resume'?">
|
||||
If the employer specifically requests a one-page resume and expects a traditional format, use A4 or Letter and ensure
|
||||
your content fits within a single page. See [Fitting content on a page](/guides/fitting-content-on-a-page) for tips.
|
||||
If the employer asks for a one-page resume and expects a traditional format, use A4 or Letter and fit your content on
|
||||
a single page. See [Fitting content on a page](/guides/fitting-content-on-a-page) for tips.
|
||||
</Accordion>
|
||||
|
||||
<Accordion title="Does Free-Form affect the file size?">
|
||||
@@ -157,6 +155,6 @@ Download these sample resumes to see how different formats affect the final PDF
|
||||
</Accordion>
|
||||
|
||||
<Accordion title="Which format should I use for LinkedIn?">
|
||||
LinkedIn doesn't display uploaded resumes in their original format—it extracts the content. Free-Form works perfectly for LinkedIn uploads.
|
||||
LinkedIn doesn't display uploaded resumes in their original format; it extracts the content. Free-Form works fine for LinkedIn uploads.
|
||||
</Accordion>
|
||||
</AccordionGroup>
|
||||
|
||||
@@ -9,12 +9,11 @@ description: "Register WebAuthn passkeys on your Reactive Resume account to sign
|
||||
</Step>
|
||||
|
||||
<Step title="Navigate to Authentication settings">
|
||||
Once you're in the dashboard, look for the sidebar navigation on the left. Under the <Badge>Settings</Badge> section,
|
||||
click on the <Badge>Authentication</Badge> link.
|
||||
In the dashboard sidebar on the left, under <Badge>Settings</Badge>, click the <Badge>Authentication</Badge> link.
|
||||
</Step>
|
||||
|
||||
<Step title="Register a new device">
|
||||
In the <Badge>Passkeys</Badge> section, click on the <Badge>Register New Device</Badge> button.
|
||||
In the <Badge>Passkeys</Badge> section, click the <Badge>Register New Device</Badge> button.
|
||||
</Step>
|
||||
|
||||
<Step title="Name your passkey">
|
||||
@@ -22,7 +21,7 @@ description: "Register WebAuthn passkeys on your Reactive Resume account to sign
|
||||
</Step>
|
||||
|
||||
<Step title="Complete the passkey prompt">
|
||||
Your browser or device will show a passkey prompt (WebAuthn). Follow the on-screen instructions to register your passkey using your biometric (Face ID / Touch ID / fingerprint) or device PIN.
|
||||
Your browser or device shows a passkey prompt (WebAuthn). What it asks for depends on the authenticator you are registering: a biometric (Face ID / Touch ID / fingerprint), your device PIN, or inserting and touching a security key.
|
||||
|
||||
<Info>
|
||||
Passkeys are tied to your device (or password manager) and are a more secure alternative to passwords.
|
||||
@@ -31,7 +30,7 @@ description: "Register WebAuthn passkeys on your Reactive Resume account to sign
|
||||
</Step>
|
||||
|
||||
<Step title="Manage passkeys (optional)">
|
||||
After registering, your passkey will show up in the list. You can rename it or delete it from the same section.
|
||||
After registering, your passkey appears in the list. You can rename it or delete it from the same section.
|
||||
|
||||
<Warning>
|
||||
Deleting a passkey cannot be undone. After deletion, you won't be able to sign in using that passkey anymore.
|
||||
|
||||
@@ -5,7 +5,7 @@ description: "Enable TOTP two-factor authentication on your Reactive Resume acco
|
||||
|
||||
<Steps>
|
||||
<Step title="Ensure you have a password set">
|
||||
In order to see the option to set up two-factor authentication, you need to set a password. If you haven't set a password yet, possibly because you created your account through signing in with Google or GitHub, you will not be able to follow along this guide.
|
||||
The option to set up two-factor authentication only appears once your account has a password. If you signed in with Google or GitHub and never set one, you cannot follow this guide until you do.
|
||||
|
||||
<Warning>
|
||||
Two-factor authentication requires a password to be set on your account. If you signed up using a social provider (Google or GitHub), you'll need to set a password first from the Authentication settings page.
|
||||
@@ -17,32 +17,31 @@ description: "Enable TOTP two-factor authentication on your Reactive Resume acco
|
||||
Head over to [https://rxresu.me](https://rxresu.me) and sign in with your account credentials.
|
||||
|
||||
<Tip>
|
||||
If you haven't created an account yet, follow the guide on [Creating an Account](/guides/creating-an-account).
|
||||
If you haven't created an account yet, follow the guide on [Creating an account](/guides/creating-an-account).
|
||||
</Tip>
|
||||
|
||||
</Step>
|
||||
|
||||
<Step title="Navigate to Authentication settings">
|
||||
Once you're in the dashboard, look for the sidebar navigation on the left. Under the <Badge>Settings</Badge> section,
|
||||
click on the <Badge>Authentication</Badge> link.
|
||||
In the dashboard sidebar on the left, under <Badge>Settings</Badge>, click the <Badge>Authentication</Badge> link.
|
||||
</Step>
|
||||
|
||||
<Step title="Click on Enable 2FA">
|
||||
On the Authentication page, find the <Badge>Two-Factor Authentication</Badge> section and click on the{" "}
|
||||
On the Authentication page, find the <Badge>Two-Factor Authentication</Badge> section and click the{" "}
|
||||
<Badge>Enable 2FA</Badge> button.
|
||||
</Step>
|
||||
|
||||
<Step title="Enter your password">
|
||||
You will be asked to re-enter your password to authenticate that it's really you. Enter your password and click continue.
|
||||
You are asked to re-enter your password to confirm it's really you. Enter it and click continue.
|
||||
|
||||
<Info>
|
||||
This password verification step ensures that only authorized users can enable two-factor authentication on your account.
|
||||
The password check prevents someone else from enabling two-factor authentication on your account.
|
||||
</Info>
|
||||
|
||||
</Step>
|
||||
|
||||
<Step title="Scan the QR code">
|
||||
After entering your password, you should be shown a QR code. Scan it with your authenticator device and enter the 6-digit code that the app provides to continue.
|
||||
After entering your password, you are shown a QR code. Scan it with your authenticator device and enter the 6-digit code the app gives you to continue.
|
||||
|
||||
<Tip>
|
||||
Popular authenticator apps you can use include:
|
||||
@@ -54,13 +53,13 @@ description: "Enable TOTP two-factor authentication on your Reactive Resume acco
|
||||
</Tip>
|
||||
|
||||
<Info>
|
||||
You can also copy the secret key above the QR code and paste it into your authenticator app if you prefer manual entry.
|
||||
If you prefer manual entry, copy the secret key above the QR code and paste it into your authenticator app.
|
||||
</Info>
|
||||
|
||||
</Step>
|
||||
|
||||
<Step title="Save your backup codes">
|
||||
Once verified, you'll be prompted to save backup codes. You can use each code only once, and they're useful if you ever happen to lose access to your authenticator device.
|
||||
Once verified, you are prompted to save backup codes. Each code works only once, and they let you sign in if you lose access to your authenticator device.
|
||||
|
||||
<Warning>
|
||||
Make sure to copy and store these backup codes in a safe place. If you lose your authenticator device and don't have backup codes, you may lose access to your account.
|
||||
@@ -69,10 +68,10 @@ description: "Enable TOTP two-factor authentication on your Reactive Resume acco
|
||||
</Step>
|
||||
|
||||
<Step title="Sign in with 2FA">
|
||||
The next time you sign in, you will be asked for a one-time code from your authenticator app. Enter the 6-digit code displayed in your authenticator app to complete the sign-in process.
|
||||
The next time you sign in, you are asked for a one-time code from your authenticator app. Enter the 6-digit code shown there to finish signing in.
|
||||
|
||||
<Tip>
|
||||
If you've lost access to your authenticator device, you can use one of your backup codes to sign in. Remember that each backup code can only be used once.
|
||||
If you have lost access to your authenticator device, use one of your backup codes to sign in. Each backup code can only be used once.
|
||||
</Tip>
|
||||
|
||||
</Step>
|
||||
|
||||
@@ -3,9 +3,9 @@ title: "Sharing your resume publicly"
|
||||
description: "Publish your resume at a public URL, share it with recruiters, track views and downloads, and optionally protect it 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.
|
||||
Reactive Resume can publish your resume at a **public URL**. Anyone with the link can open it, so you can send it to recruiters, collaborators, or people visiting your portfolio. Public resume URLs are not search-indexed by default.
|
||||
|
||||
## Key benefits of public sharing
|
||||
## What public sharing gives you
|
||||
|
||||
<CardGroup cols={2}>
|
||||
<Card title="Always up-to-date" icon="arrows-rotate">
|
||||
@@ -18,7 +18,7 @@ Reactive Resume lets you share your resume via a **public URL** that anyone can
|
||||
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.
|
||||
One URL you can paste into an email signature, LinkedIn, a portfolio, or a job application.
|
||||
</Card>
|
||||
</CardGroup>
|
||||
|
||||
@@ -32,7 +32,7 @@ Reactive Resume lets you share your resume via a **public URL** that anyone can
|
||||
<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.
|
||||
Turn on the **Allow Public Access** switch. Your resume is then reachable at its public URL.
|
||||
|
||||
<Frame caption="Sharing section in the resume builder">
|
||||
<img
|
||||
@@ -63,20 +63,20 @@ Reactive Resume lets you share your resume via a **public URL** that anyone can
|
||||
|
||||
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** - The public page shows an identity header with your name, headline, and picture, and a prominent **Download PDF** action
|
||||
4. **Link previews look right** - Reactive Resume generates per-resume Open Graph and Twitter card previews, so links you paste into LinkedIn, Slack, iMessage, and similar apps show your name and headline instead of a generic placeholder
|
||||
5. **Views are tracked** - Visits are counted in your resume statistics (see below)
|
||||
1. They see the live version. The page renders your current resume data, including your latest changes.
|
||||
2. No account is required. Visitors don't need a Reactive Resume account to view or download your resume.
|
||||
3. They can download a PDF. The public page shows an identity header with your name, headline, and picture, plus a **Download PDF** action.
|
||||
4. Link previews work. Reactive Resume generates per-resume Open Graph and Twitter card previews, so links you paste into LinkedIn, Slack, iMessage, and similar apps show your name and headline instead of a generic placeholder.
|
||||
5. 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.
|
||||
Changes you make in the builder show up immediately on the public URL. There is no separate "publish" step. 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.
|
||||
When your resume is public, Reactive Resume counts public views, so you can tell whether people are opening the link you shared.
|
||||
|
||||
### Where to find statistics
|
||||
|
||||
@@ -90,7 +90,7 @@ You'll see public view information such as:
|
||||
| **Downloads** | Number of times a visitor downloaded your resume as a PDF |
|
||||
| **Last viewed** | The date when your resume was last viewed |
|
||||
|
||||
Each metric also shows a 30-day sparkline and the change compared to the previous period, so you can spot whether interest is rising or falling after you share the link.
|
||||
Each metric also shows a 30-day sparkline and the change against the previous period, so you can see whether interest rose or fell after you shared the link.
|
||||
|
||||
<Info>
|
||||
Statistics are only shown after public sharing is enabled. If you turn off public access, existing stats are
|
||||
@@ -113,7 +113,7 @@ Owner self-visits while you are signed in to your account are not included in th
|
||||
|
||||
## 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.
|
||||
To share your resume with specific people while keeping it away from everyone else, add password protection.
|
||||
|
||||
When password protection is enabled:
|
||||
|
||||
@@ -131,7 +131,7 @@ When password protection is enabled:
|
||||
<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.
|
||||
Type a password (6-64 characters) and confirm it. Viewers have to enter this password to see your resume.
|
||||
</Step>
|
||||
|
||||
<Step title="Share the password separately">
|
||||
@@ -151,7 +151,7 @@ If you no longer need password protection:
|
||||
2. Click **Remove Password**
|
||||
3. Confirm the action
|
||||
|
||||
Your resume will become accessible to anyone with the public URL.
|
||||
Your resume is then open to anyone with the public URL.
|
||||
|
||||
## Use cases for public sharing
|
||||
|
||||
@@ -161,7 +161,7 @@ Your resume will become accessible to anyone with the public URL.
|
||||
</Accordion>
|
||||
|
||||
<Accordion title="Email signature" icon="envelope">
|
||||
Include your resume link in your email signature. Anyone you correspond with can quickly access your resume.
|
||||
Include your resume link in your email signature, so anyone you write to can open it.
|
||||
</Accordion>
|
||||
|
||||
<Accordion title="Portfolio website" icon="globe">
|
||||
@@ -174,7 +174,7 @@ Your resume will become accessible to anyone with the public URL.
|
||||
</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.
|
||||
Share your resume URL via QR code or NFC. Update the resume before the event and everyone gets the current version.
|
||||
</Accordion>
|
||||
|
||||
<Accordion title="Confidential job search" icon="lock">
|
||||
@@ -197,13 +197,13 @@ When public access is disabled:
|
||||
- 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.
|
||||
To hide your resume temporarily, use password protection instead of turning off public access. The URL stays 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.
|
||||
The builder dock has 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
|
||||
@@ -214,7 +214,7 @@ The builder dock includes a **Copy URL** shortcut. It copies the same public URL
|
||||
|
||||
<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.
|
||||
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 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?">
|
||||
@@ -231,6 +231,6 @@ The builder dock includes a **Copy URL** shortcut. It copies the same public URL
|
||||
</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.
|
||||
Your public URL changes to match the new username, and the old URLs stop working immediately. Update any links you have already shared.
|
||||
</Accordion>
|
||||
</AccordionGroup>
|
||||
|
||||
@@ -3,7 +3,7 @@ title: "Tracking job applications"
|
||||
description: "Use the Application Tracker to record jobs, link the resume you sent, manage follow-ups, and move applications through your hiring pipeline."
|
||||
---
|
||||
|
||||
The **Application Tracker** helps you keep your job search connected to the resumes you create in Reactive Resume. Each application can store the company, role, stage, job posting, resume, cover letter, contacts, notes, and follow-up details.
|
||||
The **Application Tracker** keeps your job search tied to the resumes you build in Reactive Resume. Each application can store the company, role, stage, job posting, resume, cover letter, contacts, notes, and follow-up details.
|
||||
|
||||
## Open the Application Tracker
|
||||
|
||||
@@ -45,8 +45,8 @@ The **Application Tracker** helps you keep your job search connected to the resu
|
||||
</Step>
|
||||
|
||||
<Step title="Link or upload the resume you sent">
|
||||
Choose a Reactive Resume from the **Resume** field when you want to keep a live link to the resume. You can also upload
|
||||
the exact resume PDF you sent.
|
||||
Pick a Reactive Resume in the **Resume** field to keep a live link to it. You can also upload the exact resume PDF you
|
||||
sent.
|
||||
</Step>
|
||||
|
||||
<Step title="Attach a cover letter">
|
||||
@@ -75,11 +75,11 @@ If you have an AI provider configured, paste a job posting URL at the top of the
|
||||
|
||||
If auto-fill fails or the posting is private, paste the job description manually.
|
||||
|
||||
For AI setup, see [Using Artificial Intelligence](/guides/using-ai).
|
||||
For AI setup, see [Using artificial intelligence](/guides/using-ai).
|
||||
|
||||
## Understand application stages
|
||||
|
||||
Applications move through fixed stages:
|
||||
Applications move through a fixed set of stages:
|
||||
|
||||
| Stage | Use it when |
|
||||
| --- | --- |
|
||||
@@ -156,6 +156,6 @@ For setup and prompt examples, see [Managing applications with MCP](/guides/mana
|
||||
|
||||
## Archive or delete applications
|
||||
|
||||
Archive applications you want to hide from the active board without deleting their history. Use the **Archived** toggle to view archived applications and unarchive them later.
|
||||
Archive an application to hide it from the active board without losing its history. Use the **Archived** toggle to see archived applications and unarchive them later.
|
||||
|
||||
Delete an application only when you no longer need its record. Deleting an application removes its timeline and cannot be undone.
|
||||
|
||||
@@ -5,14 +5,14 @@ description: "Undo and redo edits with keyboard shortcuts in the Reactive Resume
|
||||
|
||||
Reactive Resume keeps two layers of change history for every resume:
|
||||
|
||||
- **Undo and redo** — a live timeline of the changes you've made in the current builder session.
|
||||
- **Version history** — server-side snapshots taken at meaningful moments, kept even after you close the builder.
|
||||
- **Undo and redo**: a live timeline of the changes you've made in the current builder session.
|
||||
- **Version history**: server-side snapshots taken at meaningful moments, kept even after you close the builder.
|
||||
|
||||
Use undo for a quick correction. Use version history to jump back to a template switch, an import, or an AI edit you made earlier.
|
||||
|
||||
## Undo and redo
|
||||
|
||||
Every change in the builder is undoable — typing, drag-and-drop reordering, template and layout switches, and edits applied by the AI assistant.
|
||||
Every change in the builder is undoable: typing, drag-and-drop reordering, template and layout switches, and edits applied by the AI assistant.
|
||||
|
||||
<Steps>
|
||||
<Step title="Open your resume in the builder">
|
||||
@@ -27,7 +27,7 @@ Every change in the builder is undoable — typing, drag-and-drop reordering, te
|
||||
| `Cmd/Ctrl+Z` | Undo the last change |
|
||||
| `Cmd/Ctrl+Shift+Z` | Redo the last undone change |
|
||||
|
||||
Rapid typing collapses into a single step, so undo feels natural.
|
||||
Rapid typing collapses into a single step, so one undo removes a phrase rather than one letter.
|
||||
</Step>
|
||||
</Steps>
|
||||
|
||||
@@ -37,11 +37,11 @@ Every change in the builder is undoable — typing, drag-and-drop reordering, te
|
||||
a template switch.
|
||||
</Tip>
|
||||
|
||||
Undo history lives in your browser for the current session. Reloading the builder clears it — use version history for longer-range recovery.
|
||||
Undo history lives in your browser for the current session. Reloading the builder clears it, so use version history for anything older.
|
||||
|
||||
## Version history
|
||||
|
||||
Reactive Resume automatically snapshots your resume at key moments:
|
||||
Reactive Resume snapshots your resume automatically:
|
||||
|
||||
- when you import a resume;
|
||||
- when you switch templates;
|
||||
|
||||
@@ -8,14 +8,13 @@ description: "Update your Reactive Resume profile information, including your di
|
||||
Head over to [https://rxresu.me](https://rxresu.me) and sign in with your account credentials.
|
||||
|
||||
<Tip>
|
||||
If you haven't created an account yet, follow the guide on [Creating an Account](/guides/creating-an-account).
|
||||
If you haven't created an account yet, follow the guide on [Creating an account](/guides/creating-an-account).
|
||||
</Tip>
|
||||
|
||||
</Step>
|
||||
|
||||
<Step title="Navigate to Profile settings">
|
||||
Once you're in the dashboard, look for the sidebar navigation on the left. Under the <Badge>Settings</Badge> section,
|
||||
click on the <Badge>Profile</Badge> link.
|
||||
In the dashboard sidebar on the left, under <Badge>Settings</Badge>, click the <Badge>Profile</Badge> link.
|
||||
</Step>
|
||||
|
||||
<Step title="Update your information">
|
||||
@@ -35,7 +34,7 @@ description: "Update your Reactive Resume profile information, including your di
|
||||
If you've updated your email address, check your current email inbox for a verification link. Click on the link to confirm the email change.
|
||||
|
||||
<Tip>
|
||||
Make sure to check your spam folder if you don't see the verification email in your inbox. The verification link is required to complete the email address change.
|
||||
Check your spam folder if the verification email isn't in your inbox. The email address change only completes after you click the link.
|
||||
</Tip>
|
||||
|
||||
</Step>
|
||||
|
||||
@@ -1,9 +1,9 @@
|
||||
---
|
||||
title: "Using the AI Agent Workspace"
|
||||
title: "Using the AI Agent workspace"
|
||||
description: "Start an isolated AI draft in the Reactive Resume Agent workspace, chat with the agent, review proposed resume patches, and resume prior threads."
|
||||
---
|
||||
|
||||
The AI Agent workspace is a dedicated place to work with an AI assistant on a resume draft. It keeps the conversation, tool activity, and read-only resume preview in one full-screen view.
|
||||
The AI Agent workspace is where you work with an AI assistant on a resume draft. It keeps the conversation, the tool activity, and a read-only resume preview in one full-screen view.
|
||||
|
||||
<Info>
|
||||
Agent threads edit an AI draft copy of your resume. Your original resume is not changed when you start from an existing resume.
|
||||
@@ -11,7 +11,7 @@ The AI Agent workspace is a dedicated place to work with an AI assistant on a re
|
||||
|
||||
## Before you start
|
||||
|
||||
You need at least one AI provider that is tested and enabled in **Dashboard -> Settings -> Integrations**. For setup, see [Using Artificial Intelligence](/guides/using-ai).
|
||||
You need at least one AI provider that is tested and enabled in **Dashboard → Settings → Integrations**. For setup, see [Using artificial intelligence](/guides/using-ai).
|
||||
|
||||
If you self-host Reactive Resume, the agent workspace also requires the server-side agent configuration described in [Self-hosting with Docker](/self-hosting/docker).
|
||||
|
||||
@@ -76,7 +76,7 @@ The agent works best with concrete instructions:
|
||||
- "Compare this draft against a product manager role and update the keywords."
|
||||
- "Ask me before changing anything that looks uncertain."
|
||||
|
||||
You can attach files or images from the composer. The agent can read uploaded attachments when they are relevant to your request.
|
||||
You can attach files or images from the composer. The agent reads uploaded attachments when they are relevant to your request.
|
||||
|
||||
<Note>
|
||||
Text input is supported. Voice input is not supported in the agent workspace yet.
|
||||
@@ -96,7 +96,7 @@ Open the line to inspect the raw JSON Patch and use **Restore** if you want to r
|
||||
|
||||
If the agent needs a decision, it may show a question card with recommended answers. Click the answer you want to send it back to the agent.
|
||||
|
||||
This is useful when the agent finds ambiguous instructions, missing job context, or a change that depends on your preference.
|
||||
That happens when your instructions are ambiguous, job context is missing, or a change depends on your preference.
|
||||
|
||||
## Use the resume preview
|
||||
|
||||
|
||||
@@ -9,13 +9,13 @@ Reactive Resume includes two AI-assisted builder workflows:
|
||||
- The **ATS Check** section can add an optional AI review of your writing on top of its deterministic report.
|
||||
|
||||
<Info>
|
||||
These features require a tested and enabled AI provider in **Dashboard -> Settings -> Integrations**. For setup, see
|
||||
[Using Artificial Intelligence](/guides/using-ai).
|
||||
These features require a tested and enabled AI provider in **Dashboard → Settings → Integrations**. For setup, see
|
||||
[Using artificial intelligence](/guides/using-ai).
|
||||
</Info>
|
||||
|
||||
## Review the writing from the ATS check
|
||||
|
||||
The **ATS Check** section in the right sidebar runs without AI: its checks are deterministic and run in your browser. Once a deep check has produced a report, it offers an optional AI review of the writing — weak phrasing, bullets that describe duties rather than outcomes, and where a rewrite would land better.
|
||||
The **ATS Check** section in the right sidebar runs without AI: its checks are deterministic and run in your browser. Once a deep check has produced a report, it offers an optional AI review of the writing: weak phrasing, bullets that describe duties rather than outcomes, and where a rewrite would land better.
|
||||
|
||||
The review sends the text already extracted from your rendered PDF to the provider you pick, and returns no score. See [Using the ATS checker](/guides/using-the-ats-checker).
|
||||
|
||||
@@ -23,13 +23,13 @@ The review sends the text already extracted from your rendered PDF to the provid
|
||||
|
||||
Click the **Sparkle** button in the builder header, next to the resume name, to open the assistant.
|
||||
|
||||
The assistant opens as a side panel next to your resume. It uses the same chat interface as the AI Agent workspace, but stays scoped to the resume you are editing — its edits land in the builder immediately, appear in the preview, and are captured in undo history and version history.
|
||||
The assistant opens as a side panel next to your resume. It uses the same chat interface as the AI Agent workspace, but stays scoped to the resume you are editing. Its edits land in the builder immediately, appear in the preview, and are captured in undo history and version history.
|
||||
|
||||
If AI is unavailable, the panel shows a link to **Integrations** so you can configure a provider.
|
||||
|
||||
<Tip>
|
||||
The Sparkle button is the in-builder assistant. The chat-bubble icon on the floating dock opens the full **AI Agent**
|
||||
workspace in a new page — useful for longer, standalone conversations that create their own draft. See [Using the AI
|
||||
workspace in a new page, which suits longer, standalone conversations that create their own draft. See [Using the AI
|
||||
Agent Workspace](/guides/using-ai-agent).
|
||||
</Tip>
|
||||
|
||||
@@ -62,7 +62,7 @@ You can:
|
||||
- move between proposals with **Prev** and **Next**;
|
||||
- **Accept all** or **Reject all** from the split-button menu.
|
||||
|
||||
Accepted edits are saved through the normal update path, so they show up in the preview, in undo history, and in version history. If you change your mind, use `Cmd/Ctrl+Z` or restore an earlier snapshot from the clock menu — see [Undoing changes and version history](/guides/undoing-changes-and-version-history).
|
||||
Accepted edits are saved through the normal update path, so they show up in the preview, in undo history, and in version history. If you change your mind, use `Cmd/Ctrl+Z` or restore an earlier snapshot from the clock menu. See [Undoing changes and version history](/guides/undoing-changes-and-version-history).
|
||||
|
||||
<Warning>
|
||||
Review AI proposals before accepting them. AI can introduce wording that is inaccurate, too generic, or not aligned
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
title: "Using Artificial Intelligence"
|
||||
title: "Using artificial intelligence"
|
||||
description: "Configure an OpenAI, Anthropic, Gemini, OpenRouter, or Ollama provider to power AI edits, resume reviews, agent drafts, and PDF imports."
|
||||
---
|
||||
|
||||
@@ -26,7 +26,7 @@ Reactive Resume uses AI providers for features such as AI-assisted resume change
|
||||
|
||||
## Add a provider
|
||||
|
||||
In the **AI Providers** section, fill out the **Add Provider** form. The form is staged: pick a **Provider** and paste an **API Key** first — advanced options like **Model** and **Base URL** are collapsed behind an **Advanced settings** toggle and only need changing for gateways, proxies, local providers, or OpenAI-compatible endpoints.
|
||||
In the **AI Providers** section, fill out the **Add Provider** form. The form is staged: pick a **Provider** and paste an **API Key** first. **Model** and **Base URL** sit behind the **Advanced settings** toggle, and you only need them for gateways, proxies, local providers, or OpenAI-compatible endpoints.
|
||||
|
||||
| Field | Description |
|
||||
| --- | --- |
|
||||
@@ -36,7 +36,7 @@ In the **AI Providers** section, fill out the **Add Provider** form. The form is
|
||||
| **Model** *(advanced)* | The exact model name expected by that provider. |
|
||||
| **Base URL** *(advanced)* | The provider endpoint. Leave the default unless you use a gateway, proxy, local provider, or OpenAI-compatible endpoint. |
|
||||
|
||||
Click **Save Provider** when the form is complete. Reactive Resume tests the connection automatically as part of the save, so you'll see a success or failure status immediately without a separate click.
|
||||
Click **Save Provider** when the form is complete. The connection is tested as part of the save, so the success or failure status appears right away.
|
||||
|
||||
<Frame caption="Saved AI provider in Integrations">
|
||||
<img
|
||||
@@ -91,4 +91,4 @@ After a provider is tested and enabled, you can use AI in:
|
||||
- **Agent** workflows that create isolated AI drafts;
|
||||
- **PDF and Microsoft Word imports** from the dashboard import dialog.
|
||||
|
||||
For the builder workflow, see [Using AI in the builder](/guides/using-ai-in-the-builder). For the dedicated agent workspace, see [Using the AI Agent Workspace](/guides/using-ai-agent) and [AI Agent Tools](/guides/ai-agent-tools). For AI-assisted imports, see [Importing resumes](/guides/importing-resumes).
|
||||
For the builder workflow, see [Using AI in the builder](/guides/using-ai-in-the-builder). For the dedicated agent workspace, see [Using the AI Agent workspace](/guides/using-ai-agent) and [AI Agent tools](/guides/ai-agent-tools). For AI-assisted imports, see [Importing resumes](/guides/importing-resumes).
|
||||
|
||||
@@ -1,16 +1,16 @@
|
||||
---
|
||||
title: "Using Private Notes"
|
||||
description: "Learn how to use the Private Notes section in Reactive Resume to keep track of job applications, company details, and other personal reminders for each resume."
|
||||
title: "Using private notes"
|
||||
description: "Use the private notes section in Reactive Resume to track job applications, company details, and other personal reminders for each resume."
|
||||
---
|
||||
|
||||
## What are Private Notes?
|
||||
## What are private notes?
|
||||
|
||||
The **Private Notes** section is a dedicated space for storing personal information about a specific resume. This content is completely private and will never appear on your resume, whether viewed publicly or exported as a PDF.
|
||||
The **Notes** section stores personal information about one resume. Nothing you write there appears on the resume itself, whether it is viewed publicly or exported as a PDF.
|
||||
|
||||
Think of it as a built-in notebook attached to each resume where you can jot down anything relevant to your job search.
|
||||
It is a notebook attached to each resume, where you can jot down anything relevant to your job search.
|
||||
|
||||
<Info>
|
||||
Private Notes are stored with that resume's data and are only visible to you when editing the resume.
|
||||
Your notes are stored with that resume's data and are only visible to you when editing the resume.
|
||||
</Info>
|
||||
|
||||
## Where to find it
|
||||
@@ -26,7 +26,7 @@ In the resume builder, open the **right sidebar** and select **Notes** from the
|
||||
|
||||
## Use cases
|
||||
|
||||
Private Notes are designed to help you stay organized during your job search. Here are some practical ways to use them:
|
||||
Some practical ways to use them:
|
||||
|
||||
### Track job applications
|
||||
|
||||
@@ -42,13 +42,13 @@ Keep a record of where you've sent this particular resume:
|
||||
Paste links to the original job postings so you can quickly reference them when preparing for interviews or following up.
|
||||
|
||||
<Tip>
|
||||
Job postings often get taken down after a position is filled. Consider copying key requirements or responsibilities
|
||||
into your notes as a backup.
|
||||
Job postings often come down once a position is filled. Copy the main requirements or responsibilities into your notes
|
||||
as a backup.
|
||||
</Tip>
|
||||
|
||||
### Interview preparation
|
||||
|
||||
Store notes to help you prepare:
|
||||
Keep notes to help you prepare:
|
||||
|
||||
- Questions you want to ask the interviewer
|
||||
- Key points to highlight from your experience
|
||||
@@ -79,7 +79,7 @@ Track your follow-up schedule:
|
||||
</Step>
|
||||
|
||||
<Step title="Write your notes">
|
||||
Use the rich text editor to add your notes. You can format text with bold, italics, bullet points, and more.
|
||||
Use the rich text editor to write your notes. You can format text with bold, italics, bullet points, and more.
|
||||
</Step>
|
||||
|
||||
<Step title="Notes save automatically">
|
||||
@@ -90,15 +90,15 @@ Track your follow-up schedule:
|
||||
## Privacy guarantee
|
||||
|
||||
<Warning>
|
||||
Private Notes are for your eyes only. They will **never** appear in your exported files, on your public resume link, or
|
||||
Your notes are for your eyes only. They will **never** appear in your exported files, on your public resume URL, or
|
||||
in a printed version of your resume.
|
||||
</Warning>
|
||||
|
||||
This makes it safe to store sensitive information like salary expectations, candid thoughts about opportunities, or personal reminders that you wouldn't want an employer to see.
|
||||
That makes it safe to store sensitive details: salary expectations, candid thoughts about an opportunity, or reminders you would not want an employer to see.
|
||||
|
||||
## Tips for effective note-taking
|
||||
|
||||
- **Be consistent**: Use a similar format across all your resumes to make it easy to find information
|
||||
- **Date your entries**: Add dates when noting application submissions or follow-ups
|
||||
- **Keep it relevant**: Focus on information specific to this resume version and its target roles
|
||||
- **Update regularly**: Keep your notes current as your job search progresses
|
||||
- Use a similar format across all your resumes, so information is easy to find
|
||||
- Add dates when you note an application submission or a follow-up
|
||||
- Keep the notes specific to this version of the resume and the roles it targets
|
||||
- Update them as your job search moves along
|
||||
|
||||
@@ -9,12 +9,11 @@ description: "Create Reactive Resume API keys, authenticate REST requests with b
|
||||
</Step>
|
||||
|
||||
<Step title="Navigate to API Keys settings">
|
||||
Once you're in the dashboard, look for the sidebar navigation on the left. Under the <Badge>Settings</Badge> section,
|
||||
click on the <Badge>API Keys</Badge> link.
|
||||
In the dashboard sidebar on the left, under <Badge>Settings</Badge>, click the <Badge>API Keys</Badge> link.
|
||||
</Step>
|
||||
|
||||
<Step title="Open the API reference">
|
||||
On the API Keys page, click <Badge>API Documentation</Badge> to view the API reference.
|
||||
On the API Keys page, click <Badge>API Documentation</Badge> to open the API reference.
|
||||
|
||||
<Tip>
|
||||
You can also open it directly here: [API Reference](https://docs.rxresu.me/api-reference).
|
||||
@@ -31,7 +30,7 @@ description: "Create Reactive Resume API keys, authenticate REST requests with b
|
||||
</Step>
|
||||
|
||||
<Step title="Copy the API key (important)">
|
||||
After creating the key, you'll be shown the secret key once. Copy it and store it securely.
|
||||
The secret key is shown once, right after you create it. Copy it and store it somewhere safe.
|
||||
|
||||
<Warning>
|
||||
For security reasons, your API key is only displayed once. If you lose it, you must create a new one.
|
||||
|
||||
@@ -41,7 +41,7 @@ Employment gaps, writing style, and length are reported as **unscored tips**. Th
|
||||
|
||||
The report has three parts.
|
||||
|
||||
**A score from 0 to 100.** It is the weighted result of five categories: readability, layout, sections, contact details, and dates. A blocking problem puts a hard ceiling on it: a file with no text layer cannot score well because its margins are tidy.
|
||||
**A score from 0 to 100.** It is the weighted result of five categories: readability, layout, sections, contact details, and dates. A blocking problem puts a hard ceiling on it: a file with no text layer cannot score well just because its margins are tidy.
|
||||
|
||||
**A category breakdown.** Each category expands into the checks that ran, what failed, and what to do about it. Every finding cites evidence from your file: the text that triggered it and the page it sits on.
|
||||
|
||||
@@ -65,7 +65,7 @@ The **ATS Check** section in the builder's right sidebar has two tiers:
|
||||
|
||||
## Adding an AI review
|
||||
|
||||
After a report exists, you can optionally ask an AI provider to review the **writing**: weak phrasing, bullets that describe duties rather than outcomes, and where a rewrite would land better.
|
||||
Once a report exists, you can ask an AI provider to review the **writing**: weak phrasing, bullets that describe duties rather than outcomes, and where a rewrite would land better.
|
||||
|
||||
<Info>
|
||||
The AI review needs your own tested AI provider in **Dashboard → Settings → Integrations**. See [Using Artificial
|
||||
|
||||
@@ -1,9 +1,9 @@
|
||||
---
|
||||
title: "Using the builder dock"
|
||||
description: "Learn how to use the builder dock for undo and redo, zoom controls, page stacking, opening the AI Agent, and copying the public resume URL."
|
||||
description: "Use the builder dock for undo and redo, zoom controls, page stacking, opening the AI Agent, and copying the public resume URL."
|
||||
---
|
||||
|
||||
The builder dock is the floating toolbar at the bottom of the resume builder. It gives you quick access to undo and redo, preview controls, the AI Agent workspace, and the resume's public URL without leaving the resume canvas.
|
||||
The builder dock is the floating toolbar at the bottom of the resume builder. It holds undo and redo, preview controls, the AI Agent workspace, and the resume's public URL, so you can reach them without leaving the canvas.
|
||||
|
||||
<Frame caption="Resume builder with the floating dock">
|
||||
<img
|
||||
@@ -14,7 +14,7 @@ The builder dock is the floating toolbar at the bottom of the resume builder. It
|
||||
|
||||
## Undo and redo
|
||||
|
||||
The dock starts with **Undo** and **Redo** buttons. They apply to every change in the builder — typing, drag-and-drop, template switches, layout changes, and AI edits.
|
||||
The dock starts with **Undo** and **Redo** buttons. They apply to every change in the builder: typing, drag-and-drop, template switches, layout changes, and AI edits.
|
||||
|
||||
You can also use keyboard shortcuts:
|
||||
|
||||
@@ -23,14 +23,14 @@ You can also use keyboard shortcuts:
|
||||
| `Cmd/Ctrl+Z` | Undo the last change |
|
||||
| `Cmd/Ctrl+Shift+Z` | Redo the last undone change |
|
||||
|
||||
Rapid typing collapses into a single undo step, so undo feels natural.
|
||||
Rapid typing collapses into a single undo step, so one undo removes a phrase rather than one letter.
|
||||
|
||||
<Tip>
|
||||
When your cursor is inside a text field, the shortcut falls back to your browser's native input undo. Click outside the
|
||||
field, or use the dock buttons, to undo builder-wide changes.
|
||||
</Tip>
|
||||
|
||||
For longer-range recovery — such as jumping back to a template switch, an import, or an AI edit — see [Undoing changes and version history](/guides/undoing-changes-and-version-history).
|
||||
For longer-range recovery, such as jumping back to a template switch, an import, or an AI edit, see [Undoing changes and version history](/guides/undoing-changes-and-version-history).
|
||||
|
||||
## Zoom controls
|
||||
|
||||
@@ -52,13 +52,13 @@ Use the page-stacking button to switch between stacked pages (vertical) and side
|
||||
|
||||
## Open the AI Agent
|
||||
|
||||
Click the chat button to open the **AI Agent** workspace in a new page, pre-scoped to the current resume. Use the agent for larger, standalone conversations that create their own draft.
|
||||
Click the chat button to open the **AI Agent** workspace in a new page, pre-scoped to the current resume. The agent suits larger, standalone conversations that create their own draft.
|
||||
|
||||
For chatting about the open resume without leaving the builder, use the AI assistant in the builder header instead. See [Using AI in the builder](/guides/using-ai-in-the-builder).
|
||||
|
||||
## Copy the public URL
|
||||
|
||||
Click **Copy URL** to copy the resume's public link.
|
||||
Click **Copy URL** to copy the resume's public URL.
|
||||
|
||||
The URL is based on your username and the resume slug:
|
||||
|
||||
|
||||
@@ -1,9 +1,9 @@
|
||||
---
|
||||
title: "Using the MCP Server"
|
||||
title: "Using the MCP server"
|
||||
description: "Connect Reactive Resume to AI tools like Claude Desktop, Cursor, and Codex through the Model Context Protocol to edit and manage resumes via chat."
|
||||
---
|
||||
|
||||
The Reactive Resume MCP server lets you manage and modify your resumes and job applications through any MCP-compatible AI tool - Claude Desktop, Cursor, Codex, and more. It connects to the Reactive Resume API and exposes tools for resume editing, Application Tracker workflows, and AI-assisted job application tasks using natural language.
|
||||
The Reactive Resume MCP server lets you manage your resumes and job applications from any MCP-compatible AI tool: Claude Desktop, Cursor, Codex, and others. It connects to the Reactive Resume API and exposes tools for resume editing, Application Tracker workflows, and AI-assisted job application tasks, driven by natural language.
|
||||
|
||||
## What is MCP?
|
||||
|
||||
@@ -23,7 +23,7 @@ The [Model Context Protocol (MCP)](https://modelcontextprotocol.io) is a standar
|
||||
</Step>
|
||||
|
||||
<Step title="If using API key, create one">
|
||||
Head over to [https://rxresu.me](https://rxresu.me) (or your self-hosted instance), sign in, and navigate to **Settings → API Keys**. Click **Create a new API key**, give it a name, and copy the secret — it's only shown once.
|
||||
Head over to [https://rxresu.me](https://rxresu.me) (or your self-hosted instance), sign in, and navigate to **Settings → API Keys**. Click **Create a new API key**, give it a name, and copy the secret. It is shown only once.
|
||||
|
||||
For the full walkthrough, see [Using the API](/guides/using-the-api).
|
||||
|
||||
@@ -99,7 +99,7 @@ If your client only supports `command` / `args` (for example, local-only Claude
|
||||
| Codex | `~/.codex/config.toml` or `.codex/config.toml` ([docs](https://developers.openai.com/codex/mcp)) |
|
||||
| Other MCP clients | Refer to the client's documentation |
|
||||
|
||||
## Authentication Details (How Reactive Resume MCP Works)
|
||||
## Authentication details (how Reactive Resume MCP works)
|
||||
|
||||
Reactive Resume MCP accepts authentication in this order:
|
||||
|
||||
@@ -110,7 +110,7 @@ If neither is valid, the MCP endpoint responds with `401` and advertises OAuth m
|
||||
|
||||
- `WWW-Authenticate: Bearer resource_metadata="<instance>/.well-known/oauth-protected-resource"`
|
||||
|
||||
This lets OAuth-capable MCP clients discover and complete the OAuth flow automatically.
|
||||
OAuth-capable MCP clients use this to discover and complete the OAuth flow automatically.
|
||||
|
||||
### OAuth2 flow used by this server
|
||||
|
||||
@@ -123,7 +123,7 @@ Reactive Resume is configured as an OAuth authorization server for MCP clients:
|
||||
- If the user is signed in, `/auth/oauth` validates `client_id` and `redirect_uri`, issues an authorization code, and redirects back to the client.
|
||||
- PKCE parameters (`code_challenge`, `code_challenge_method`) are preserved in the authorization flow.
|
||||
|
||||
## Popular Client Setup
|
||||
## Popular client setup
|
||||
|
||||
### Cursor
|
||||
|
||||
@@ -162,7 +162,7 @@ Add server:
|
||||
codex mcp add reactive-resume --url https://rxresu.me/mcp
|
||||
```
|
||||
|
||||
Then log in with OAuth:
|
||||
Then sign in with OAuth:
|
||||
|
||||
```bash
|
||||
codex mcp login reactive-resume
|
||||
@@ -184,7 +184,7 @@ Add `https://rxresu.me/mcp` as a custom remote MCP connector, then connect with
|
||||
|
||||
Use `mcp-remote` bridge with API key (example shown above in **Method 2**).
|
||||
|
||||
## External References
|
||||
## External references
|
||||
|
||||
- [Cursor MCP docs](https://cursor.sh/docs/mcp)
|
||||
- [MCP quickstart for users (Claude Desktop example)](https://modelcontextprotocol.io/quickstart/user)
|
||||
@@ -192,7 +192,7 @@ Use `mcp-remote` bridge with API key (example shown above in **Method 2**).
|
||||
- [Claude custom connectors (remote MCP)](https://claude.com/docs/connectors/custom/remote-mcp)
|
||||
- [MCP Authorization spec](https://modelcontextprotocol.io/specification/latest/basic/authorization)
|
||||
|
||||
## Self-Hosting
|
||||
## Self-hosting
|
||||
|
||||
If you're running a self-hosted Reactive Resume instance, replace `https://rxresu.me/mcp` with your instance URL:
|
||||
|
||||
@@ -205,7 +205,7 @@ If you're running a self-hosted Reactive Resume instance, replace `https://rxres
|
||||
}
|
||||
```
|
||||
|
||||
## Available Tools
|
||||
## Available tools
|
||||
|
||||
Tool names use canonical unprefixed `snake_case` names.
|
||||
|
||||
@@ -246,20 +246,20 @@ Tool names use canonical unprefixed `snake_case` names.
|
||||
|
||||
Older clients may refer to prefixed or dot-separated names. Those names are no longer registered; update automations and saved prompts to the canonical names above.
|
||||
|
||||
## Available Resources
|
||||
## Available resources
|
||||
|
||||
Resources follow MCP conventions: **static** items appear in `resources/list`; **parameterized** access is declared in `resources/templates/list` and read via `resources/read` once you know the ID.
|
||||
|
||||
| Discovery | What you get |
|
||||
| ------------------------------------- | --------------------------------------------------------------------------------------------- |
|
||||
| `resources/list` | Static resources only — currently **`resume://_meta/schema`** (ResumeData JSON Schema) |
|
||||
| `resources/templates/list` | **`resume://{id}`** — template for reading full resume JSON by ID (not enumerated per resume) |
|
||||
| `list_resumes` (tool) | **Primary way to discover resume IDs** — resumes are not listed as separate MCP resources |
|
||||
| `resources/list` | Static resources only: currently **`resume://_meta/schema`** (ResumeData JSON Schema) |
|
||||
| `resources/templates/list` | **`resume://{id}`**: template for reading full resume JSON by ID (not enumerated per resume) |
|
||||
| `list_resumes` (tool) | **Primary way to discover resume IDs**; resumes are not listed as separate MCP resources |
|
||||
|
||||
| URI | Description |
|
||||
| ----------------------- | ------------------------------------------------------------------------ |
|
||||
| `resume://_meta/schema` | ResumeData JSON Schema — use for valid JSON Patch paths and value types |
|
||||
| `resume://{id}` | Full resume data as JSON — use an ID from `list_resumes` |
|
||||
| `resume://_meta/schema` | ResumeData JSON Schema; use for valid JSON Patch paths and value types |
|
||||
| `resume://{id}` | Full resume data as JSON; use an ID from `list_resumes` |
|
||||
|
||||
### Breaking change (schema URI)
|
||||
|
||||
@@ -267,21 +267,21 @@ The schema resource was previously `resume://schema`. It is now **`resume://_met
|
||||
|
||||
### Static server card (`/.well-known/mcp/server-card.json`)
|
||||
|
||||
`GET /.well-known/mcp/server-card.json` returns a JSON document ([SEP-1649](https://github.com/modelcontextprotocol/modelcontextprotocol/issues/1649)) with `serverInfo`, optional authentication metadata, and summaries of tools, resources, resource templates, and prompts. It is generated to match the live MCP server and can be used for discovery when a client cannot run a full capability scan against `/mcp/`.
|
||||
`GET /.well-known/mcp/server-card.json` returns a JSON document ([SEP-1649](https://github.com/modelcontextprotocol/modelcontextprotocol/issues/1649)) with `serverInfo`, optional authentication metadata, and summaries of tools, resources, resource templates, and prompts. It is generated to match the live MCP server, and a client that cannot run a full capability scan against `/mcp/` can use it for discovery.
|
||||
|
||||
## Available Prompts
|
||||
## Available prompts
|
||||
|
||||
Prompts are pre-built workflows that provide the AI with structured instructions and context. Each prompt embeds the resume data and the schema resource (`resume://_meta/schema`) automatically.
|
||||
Prompts are pre-built workflows that give the AI structured instructions and context. Each prompt embeds the resume data and the schema resource (`resume://_meta/schema`) automatically.
|
||||
|
||||
| Prompt | Description |
|
||||
| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
|
||||
| `build_resume` | Guide you step-by-step through building a resume from scratch — basics, summary, experience, education, skills, and design |
|
||||
| `build_resume` | Guide you step-by-step through building a resume from scratch: basics, summary, experience, education, skills, and design |
|
||||
| `improve_resume` | Review your resume and suggest concrete improvements to wording, impact, metrics, and structure |
|
||||
| `review_resume` | Get a structured, professional critique with a scorecard (1–10 across seven dimensions) and prioritized recommendations. **Read-only** — no changes are made |
|
||||
| `review_resume` | Get a structured, professional critique with a scorecard (1–10 across seven dimensions) and prioritized recommendations. **Read-only**; no changes are made |
|
||||
|
||||
## Usage Examples
|
||||
## Usage examples
|
||||
|
||||
Once your MCP client is connected, you can use natural language to interact with your resumes:
|
||||
Once your MCP client is connected, you can work with your resumes in natural language:
|
||||
|
||||
### Browsing
|
||||
|
||||
@@ -290,7 +290,7 @@ Once your MCP client is connected, you can use natural language to interact with
|
||||
- "What skills are listed on my resume?"
|
||||
- "Show me the stats for my resume"
|
||||
|
||||
### Tracking Applications
|
||||
### Tracking applications
|
||||
|
||||
- "Create an application for Senior Frontend Engineer at Acme, stage saved, source LinkedIn."
|
||||
- "List my archived applications tagged remote."
|
||||
@@ -302,7 +302,7 @@ Once your MCP client is connected, you can use natural language to interact with
|
||||
|
||||
For a complete workflow and prompt library, see [Managing applications with MCP](/guides/managing-applications-with-mcp).
|
||||
|
||||
### Creating & Managing
|
||||
### Creating and managing
|
||||
|
||||
- "Create a new resume called 'Frontend Engineer 2026'"
|
||||
- "Import this exported ResumeData JSON as a new resume"
|
||||
@@ -328,16 +328,15 @@ For a complete workflow and prompt library, see [Managing applications with MCP]
|
||||
- "Set the primary color to blue"
|
||||
- "Hide the interests section"
|
||||
|
||||
### Using Prompts
|
||||
### Using prompts
|
||||
|
||||
- "Help me build my resume from scratch" (uses `build_resume`)
|
||||
- "Review my resume and give me a score" (uses `review_resume`)
|
||||
- "Improve the wording on my resume" (uses `improve_resume`)
|
||||
|
||||
<Tip>
|
||||
The AI will use `read_resume` to inspect your current resume before making changes with `apply_resume_patch`. This
|
||||
ensures the correct JSON paths are used. Use `update_resume` for name, slug, tags, and public visibility (not for
|
||||
section content).
|
||||
The AI reads your current resume with `read_resume` before making changes with `apply_resume_patch`, so it targets the
|
||||
correct JSON paths. Use `update_resume` for name, slug, tags, and public visibility, not for section content.
|
||||
</Tip>
|
||||
|
||||
## Troubleshooting
|
||||
@@ -350,5 +349,5 @@ For a complete workflow and prompt library, see [Managing applications with MCP]
|
||||
| "API error (404)" | The resume ID doesn't exist. Use `list_resumes` to find valid IDs |
|
||||
| "API error (403)" | The resume is locked. Unlock it in the Reactive Resume dashboard |
|
||||
| Connection refused | Check that the URL is correct and the instance is running |
|
||||
| "ReferenceError: File is not defined" when using `mcp-remote` | You're running Node.js 18. `mcp-remote` requires **Node.js 20 or later** — upgrade with `nvm use 20` or `nvm alias default 20` |
|
||||
| "ReferenceError: File is not defined" when using `mcp-remote` | You're running Node.js 18. `mcp-remote` requires **Node.js 20 or later**; upgrade with `nvm use 20` or `nvm alias default 20` |
|
||||
| "Application documents must be PDF files" | `attach_application_document` only accepts `contentType: "application/pdf"` and base64-encoded PDF bytes |
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
title: "Using the Patch API"
|
||||
title: "Using the patch API"
|
||||
description: "Partially update a Reactive Resume with JSON Patch (RFC 6902) operations to add, remove, replace, and move fields without sending the full document."
|
||||
---
|
||||
|
||||
@@ -7,7 +7,7 @@ The Patch API lets you make small, targeted changes to your resume without sendi
|
||||
|
||||
This is based on the [JSON Patch (RFC 6902)](https://datatracker.ietf.org/doc/html/rfc6902) standard.
|
||||
|
||||
## When to Use PATCH vs PUT
|
||||
## When to use PATCH vs PUT
|
||||
|
||||
| Use case | Method |
|
||||
| -------------------------------------------- | --------- |
|
||||
@@ -35,7 +35,7 @@ All requests require your API key in the `x-api-key` header. See [Using the API]
|
||||
PATCH /api/openapi/resume/{id}
|
||||
```
|
||||
|
||||
### Request Body
|
||||
### Request body
|
||||
|
||||
The resume ID is taken from the URL path, so the request body only requires the `operations` array:
|
||||
|
||||
@@ -56,7 +56,7 @@ Each operation is an object with the following properties:
|
||||
|
||||
## Examples
|
||||
|
||||
### Replace a Basic Field
|
||||
### Replace a basic field
|
||||
|
||||
Update the resume holder's name and headline:
|
||||
|
||||
@@ -72,7 +72,7 @@ curl -X PATCH "https://rxresu.me/api/openapi/resume/YOUR_RESUME_ID" \
|
||||
}'
|
||||
```
|
||||
|
||||
### Add an Experience Entry
|
||||
### Add an experience entry
|
||||
|
||||
Append a new item to the experience section:
|
||||
|
||||
@@ -105,7 +105,7 @@ curl -X PATCH "https://rxresu.me/api/openapi/resume/YOUR_RESUME_ID" \
|
||||
insert at a specific position, use a numeric index like `/sections/experience/items/0` for the beginning.
|
||||
</Tip>
|
||||
|
||||
### Remove an Item from a Section
|
||||
### Remove an item from a section
|
||||
|
||||
Remove the second skill (index `1`) from the skills section:
|
||||
|
||||
@@ -120,7 +120,7 @@ curl -X PATCH "https://rxresu.me/api/openapi/resume/YOUR_RESUME_ID" \
|
||||
}'
|
||||
```
|
||||
|
||||
### Update Metadata (Template, Colors, Fonts)
|
||||
### Update metadata (template, colors, fonts)
|
||||
|
||||
Switch the template and update the primary color:
|
||||
|
||||
@@ -136,9 +136,9 @@ curl -X PATCH "https://rxresu.me/api/openapi/resume/YOUR_RESUME_ID" \
|
||||
}'
|
||||
```
|
||||
|
||||
### Test-Then-Replace (Optimistic Concurrency)
|
||||
### Test then replace (optimistic concurrency)
|
||||
|
||||
The `test` operation checks that a value matches before proceeding. If the test fails, the entire patch is rejected. This is useful to avoid overwriting changes made by another client:
|
||||
The `test` operation checks that a value matches before the rest of the patch runs. If the test fails, the whole patch is rejected, which keeps you from overwriting changes made by another client:
|
||||
|
||||
```bash
|
||||
curl -X PATCH "https://rxresu.me/api/openapi/resume/YOUR_RESUME_ID" \
|
||||
@@ -154,7 +154,7 @@ curl -X PATCH "https://rxresu.me/api/openapi/resume/YOUR_RESUME_ID" \
|
||||
|
||||
If `/basics/name` is not `"Albert Einstein"` at the time of the request, the entire patch will fail with a `400` error and no changes will be applied.
|
||||
|
||||
### Move an Item Within a Section
|
||||
### Move an item within a section
|
||||
|
||||
Move the first experience item to the third position:
|
||||
|
||||
@@ -169,7 +169,7 @@ curl -X PATCH "https://rxresu.me/api/openapi/resume/YOUR_RESUME_ID" \
|
||||
}'
|
||||
```
|
||||
|
||||
## Error Handling
|
||||
## Error handling
|
||||
|
||||
| Status | Error Code | Description |
|
||||
| ------ | -------------------------- | ------------------------------------------------------------------------------------------------------------------------- |
|
||||
@@ -185,7 +185,7 @@ curl -X PATCH "https://rxresu.me/api/openapi/resume/YOUR_RESUME_ID" \
|
||||
|
||||
## Tips
|
||||
|
||||
- **Fetch first, then patch.** Use `GET /resume/{id}` to inspect the current structure before crafting your operations. This helps you target the correct paths and array indices.
|
||||
- **Use `test` for safety.** When updating a value you expect to be a specific value, combine `test` + `replace` to avoid accidentally overwriting concurrent changes.
|
||||
- **Batch related changes.** You can send multiple operations in a single request. They are applied in order, so later operations can depend on earlier ones.
|
||||
- **The `-` index appends.** When adding items to arrays, use `-` as the index (e.g., `/sections/skills/items/-`) to append to the end.
|
||||
- Fetch first, then patch. Use `GET /resume/{id}` to inspect the current structure before writing your operations, so you target the correct paths and array indices.
|
||||
- Use `test` for safety. When you expect a field to hold a specific value, combine `test` + `replace` so you don't overwrite a concurrent change.
|
||||
- Batch related changes. You can send multiple operations in one request. They are applied in order, so a later operation can depend on an earlier one.
|
||||
- The `-` index appends. When adding items to arrays, use `-` as the index (e.g., `/sections/skills/items/-`) to append to the end.
|
||||
|
||||
@@ -3,7 +3,7 @@ title: "License"
|
||||
description: "Read the MIT license that covers Reactive Resume, an open-source resume builder you can freely use, modify, self-host, and redistribute."
|
||||
---
|
||||
|
||||
## Open Source License (MIT)
|
||||
## Open-source license (MIT)
|
||||
|
||||
Reactive Resume is open-source software. The project is published under the **MIT License**, which allows you to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the software.
|
||||
|
||||
@@ -13,7 +13,7 @@ For the upstream repository, see: [amruthpillai/reactive-resume](https://github.
|
||||
|
||||
---
|
||||
|
||||
## MIT License Text
|
||||
## MIT License text
|
||||
|
||||
MIT License
|
||||
|
||||
|
||||
@@ -5,7 +5,7 @@ description: "How the hosted Reactive Resume service handles your personal data,
|
||||
|
||||
## Overview
|
||||
|
||||
This Privacy Policy explains how **Reactive Resume** (the “Service”) collects, uses, stores, and shares information when you use it.
|
||||
This Privacy Policy explains how **Reactive Resume** (the "Service") collects, uses, stores, and shares information when you use it.
|
||||
|
||||
Reactive Resume is open-source and can be operated in different ways (for example, by the official hosted service, or by an organization/self-hosted deployment). The specific data controller for your use depends on who operates the instance you are using.
|
||||
|
||||
@@ -24,7 +24,7 @@ If you are self-hosting, **you** are the Service Operator and responsible for co
|
||||
|
||||
---
|
||||
|
||||
## What the Service Does
|
||||
## What the Service does
|
||||
|
||||
Reactive Resume is a resume builder that lets you:
|
||||
|
||||
@@ -36,7 +36,7 @@ Reactive Resume is a resume builder that lets you:
|
||||
|
||||
---
|
||||
|
||||
## Information We Collect
|
||||
## Information we collect
|
||||
|
||||
### Account information
|
||||
|
||||
@@ -102,7 +102,7 @@ These local-only values are stored in your browser and are not necessarily trans
|
||||
|
||||
---
|
||||
|
||||
## How We Use Information
|
||||
## How we use information
|
||||
|
||||
We use the information above to:
|
||||
|
||||
@@ -114,7 +114,7 @@ We use the information above to:
|
||||
|
||||
---
|
||||
|
||||
## Cookies and Similar Technologies
|
||||
## Cookies and similar technologies
|
||||
|
||||
The Service uses cookies primarily for functionality:
|
||||
|
||||
@@ -125,7 +125,7 @@ The Service does not include built-in behavioral advertising or third-party anal
|
||||
|
||||
---
|
||||
|
||||
## Sharing and Third Parties
|
||||
## Sharing and third parties
|
||||
|
||||
We share information only as needed to provide the Service:
|
||||
|
||||
@@ -147,7 +147,7 @@ If you enable AI features and provide your own API key, prompts and generated co
|
||||
|
||||
---
|
||||
|
||||
## Data Retention
|
||||
## Data retention
|
||||
|
||||
Retention depends on the Service Operator's configuration and your actions.
|
||||
|
||||
@@ -174,25 +174,25 @@ If you are self-hosting, you are responsible for:
|
||||
|
||||
---
|
||||
|
||||
## International Transfers
|
||||
## International transfers
|
||||
|
||||
If the Service Operator (or its vendors) stores or processes data in other countries, your information may be transferred internationally. The Service Operator is responsible for providing appropriate safeguards where required by law.
|
||||
|
||||
---
|
||||
|
||||
## Your Choices and Rights
|
||||
## Your choices and rights
|
||||
|
||||
Depending on your location, you may have rights to access, correct, delete, export, or restrict processing of your personal data. You can often exercise these rights directly in the Service (for example, by editing or deleting resumes), or by contacting the Service Operator.
|
||||
|
||||
---
|
||||
|
||||
## Children's Privacy
|
||||
## Children's privacy
|
||||
|
||||
The Service is not intended for children under the age of 13 (or the minimum age required in your jurisdiction). If you believe a child has provided personal data, contact the Service Operator.
|
||||
|
||||
---
|
||||
|
||||
## Changes to This Policy
|
||||
## Changes to this Policy
|
||||
|
||||
We may update this Privacy Policy from time to time. Changes will be posted on this page with an updated effective date.
|
||||
|
||||
|
||||
@@ -5,7 +5,7 @@ description: "Terms and conditions for using the hosted Reactive Resume service,
|
||||
|
||||
## Agreement
|
||||
|
||||
These Terms of Service (the “Terms”) govern your access to and use of **Reactive Resume** (the “Service”). By using the Service, you agree to these Terms.
|
||||
These Terms of Service (the "Terms") govern your access to and use of **Reactive Resume** (the "Service"). By using the Service, you agree to these Terms.
|
||||
|
||||
- **Service Operator**: Amruth Pillai
|
||||
- **Contact**: hello@amruthpillai.com
|
||||
@@ -34,7 +34,7 @@ You must be legally able to form a contract in your jurisdiction to use the Serv
|
||||
|
||||
---
|
||||
|
||||
## Accounts and Security
|
||||
## Accounts and security
|
||||
|
||||
- **Account information**: You agree to provide accurate information and keep it up to date.
|
||||
- **Credentials**: You are responsible for maintaining the confidentiality of your login credentials and for activities that occur under your account.
|
||||
@@ -48,7 +48,7 @@ The Service Operator may suspend or terminate accounts to protect the Service, o
|
||||
|
||||
### What you provide
|
||||
|
||||
“Content” includes the resume data you enter or import (text, links, personal details, etc.) and any files you upload (e.g., profile pictures).
|
||||
"Content" includes the resume data you enter or import (text, links, personal details, etc.) and any files you upload (e.g., profile pictures).
|
||||
|
||||
### Ownership
|
||||
|
||||
@@ -66,7 +66,7 @@ If you password-protect a resume, you are responsible for controlling distributi
|
||||
|
||||
---
|
||||
|
||||
## Acceptable Use
|
||||
## Acceptable use
|
||||
|
||||
You agree not to:
|
||||
|
||||
@@ -80,7 +80,7 @@ The Service Operator may remove Content or restrict access if needed to enforce
|
||||
|
||||
---
|
||||
|
||||
## Uploads, Storage, and Delivery
|
||||
## Uploads, storage, and delivery
|
||||
|
||||
Uploaded files may be stored on the Service Operator's infrastructure and may be served back to you (and, if your resume is public, to others). Depending on configuration, storage may be local filesystem storage or S3-compatible object storage.
|
||||
|
||||
@@ -94,7 +94,7 @@ When you request a PDF export, the Service renders the document in your own brow
|
||||
|
||||
---
|
||||
|
||||
## Third-Party Services (Optional)
|
||||
## Third-party services (optional)
|
||||
|
||||
The Service may integrate with third parties depending on configuration and your choices, including:
|
||||
|
||||
@@ -106,7 +106,7 @@ Your use of third-party services may be subject to their own terms and policies.
|
||||
|
||||
---
|
||||
|
||||
## API Keys (If Enabled)
|
||||
## API keys (if enabled)
|
||||
|
||||
If the Service allows you to create API keys:
|
||||
|
||||
@@ -116,7 +116,7 @@ If the Service allows you to create API keys:
|
||||
|
||||
---
|
||||
|
||||
## Intellectual Property and Open Source
|
||||
## Intellectual property and open source
|
||||
|
||||
Reactive Resume is open-source software licensed under the **MIT License**. These Terms govern **use of the Service**, not the open-source license for the code.
|
||||
|
||||
@@ -138,13 +138,13 @@ Upon termination, your ability to access Content may be removed. Retention/delet
|
||||
|
||||
## Disclaimers
|
||||
|
||||
THE SERVICE IS PROVIDED **“AS IS”** AND **“AS AVAILABLE”** WITHOUT WARRANTIES OF ANY KIND, WHETHER EXPRESS, IMPLIED, OR STATUTORY, INCLUDING IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT.
|
||||
THE SERVICE IS PROVIDED **"AS IS"** AND **"AS AVAILABLE"** WITHOUT WARRANTIES OF ANY KIND, WHETHER EXPRESS, IMPLIED, OR STATUTORY, INCLUDING IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT.
|
||||
|
||||
The Service Operator does not guarantee that the Service will be uninterrupted, error-free, or that exports will always succeed.
|
||||
|
||||
---
|
||||
|
||||
## Limitation of Liability
|
||||
## Limitation of liability
|
||||
|
||||
TO THE MAXIMUM EXTENT PERMITTED BY LAW, THE SERVICE OPERATOR WILL NOT BE LIABLE FOR INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES, OR ANY LOSS OF PROFITS, DATA, OR GOODWILL, ARISING OUT OF OR RELATED TO YOUR USE OF (OR INABILITY TO USE) THE SERVICE.
|
||||
|
||||
@@ -162,13 +162,13 @@ You agree to defend, indemnify, and hold harmless the Service Operator from and
|
||||
|
||||
---
|
||||
|
||||
## Changes to These Terms
|
||||
## Changes to these Terms
|
||||
|
||||
We may update these Terms from time to time. Updated Terms will be posted on this page with a new effective date. Continued use of the Service after changes become effective constitutes acceptance.
|
||||
|
||||
---
|
||||
|
||||
## Governing Law
|
||||
## Governing law
|
||||
|
||||
These terms are governed by the laws of the **Federal Republic of Germany**.
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: "Self-Hosting with Docker"
|
||||
description: "A comprehensive guide to self-host Reactive Resume with Docker (Postgres only), including a detailed environment variable reference and troubleshooting tips."
|
||||
title: "Self-hosting with Docker"
|
||||
description: "How to self-host Reactive Resume with Docker (Postgres only), with an environment variable reference and troubleshooting tips."
|
||||
---
|
||||
|
||||
<Info>
|
||||
@@ -9,7 +9,7 @@ description: "A comprehensive guide to self-host Reactive Resume with Docker (Po
|
||||
|
||||
## Overview
|
||||
|
||||
Reactive Resume can be self-hosted using Docker in a matter of minutes, and this guide will walk you through the process. Here are some of the services you'll need to get started:
|
||||
Reactive Resume can be self-hosted with Docker. These are the services you'll need:
|
||||
|
||||
<CardGroup cols={2}>
|
||||
<Card title="PostgreSQL">Stores accounts, resumes, and application data.</Card>
|
||||
@@ -315,8 +315,8 @@ openssl rand -hex 32
|
||||
- **`OAUTH_SCOPES`**: Space-separated scopes (defaults to `openid profile email`)
|
||||
|
||||
Configure endpoints using **one** of these methods:
|
||||
- **Option A — OIDC Discovery (preferred)**: Set `OAUTH_DISCOVERY_URL` to your provider's `.well-known/openid-configuration` URL
|
||||
- **Option B — Manual URLs**: Set all three: `OAUTH_AUTHORIZATION_URL`, `OAUTH_TOKEN_URL`, and `OAUTH_USER_INFO_URL`
|
||||
- **Option A (OIDC Discovery, preferred)**: Set `OAUTH_DISCOVERY_URL` to your provider's `.well-known/openid-configuration` URL
|
||||
- **Option B (manual URLs)**: Set all three: `OAUTH_AUTHORIZATION_URL`, `OAUTH_TOKEN_URL`, and `OAUTH_USER_INFO_URL`
|
||||
|
||||
</Accordion>
|
||||
|
||||
@@ -367,9 +367,9 @@ openssl rand -hex 32
|
||||
|
||||
## Updating your installation
|
||||
|
||||
To update your Reactive Resume installation to the latest available version, follow these steps:
|
||||
To update your Reactive Resume installation to the latest version:
|
||||
|
||||
1. **Back up your database and uploads first** (highly recommended before every update).
|
||||
1. **Back up your database and uploads first.** Do this before every update.
|
||||
|
||||
2. **Pull the latest images** for all services defined in your Docker Compose file.
|
||||
|
||||
@@ -398,11 +398,11 @@ This process updates app services and automatically runs DB migrations on startu
|
||||
|
||||
## Backups (recommended)
|
||||
|
||||
Regular backups are essential to protect your data. Reactive Resume stores data in two places: the PostgreSQL database and file uploads (either local storage or S3).
|
||||
Reactive Resume stores data in two places: the PostgreSQL database and file uploads (either local storage or S3). Back up both on a regular schedule.
|
||||
|
||||
### Database backups
|
||||
|
||||
Your PostgreSQL database contains all user accounts, resumes, and application data. For self-hosted deployments, you can use `pg_dump` to create periodic backups of your database and store them in a secure location. Many hosting providers also offer automated backup solutions for managed PostgreSQL instances, which handle scheduling, retention, and restoration for you.
|
||||
Your PostgreSQL database holds all user accounts, resumes, and application data. Use `pg_dump` to take periodic backups and store them somewhere secure. Many providers of managed PostgreSQL also offer automated backups that handle scheduling, retention, and restores for you.
|
||||
|
||||
### Upload backups
|
||||
|
||||
@@ -410,7 +410,7 @@ If you're using local storage (the `./data` directory), include this directory i
|
||||
|
||||
If you're using S3-compatible storage, consider enabling versioning on your bucket to protect against accidental deletions. Most S3 providers also support lifecycle rules for automatic cleanup of old versions and cross-region replication for disaster recovery.
|
||||
|
||||
## Health Checks
|
||||
## Health checks
|
||||
|
||||
Reactive Resume exposes a health check endpoint at `/api/health` that verifies the application and its dependencies. It checks **database** and **storage**; if either is unhealthy, the endpoint returns HTTP `503`.
|
||||
|
||||
@@ -444,7 +444,7 @@ This is particularly useful in high-availability setups where you have multiple
|
||||
|
||||
### Manually checking health
|
||||
|
||||
You can manually verify the health of your Reactive Resume instance:
|
||||
To check your instance yourself:
|
||||
|
||||
```bash
|
||||
# From outside the container
|
||||
@@ -454,7 +454,7 @@ curl -f http://localhost:3000/api/health
|
||||
docker compose ps
|
||||
```
|
||||
|
||||
A healthy response returns HTTP 200. Any other response (or a connection failure) indicates a problem that should be investigated in the JSON response body and container logs.
|
||||
A healthy response returns HTTP 200. If you get a different status code, the JSON response body says what failed. If the connection is refused or times out there is no response to read, so check the container and reverse-proxy logs instead.
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
title: "Docker Compose Examples"
|
||||
title: "Docker Compose examples"
|
||||
description: "Ready-to-use Docker Compose examples for self-hosting Reactive Resume with Postgres, Traefik, Caddy, Nginx Proxy Manager, and other common deployment stacks."
|
||||
---
|
||||
|
||||
@@ -9,25 +9,23 @@ description: "Ready-to-use Docker Compose examples for self-hosting Reactive Res
|
||||
|
||||
## Overview
|
||||
|
||||
Every self-hosted setup is unique. You might be running on a single VPS, a Kubernetes cluster, behind Cloudflare Tunnel, or using a specific reverse proxy like Traefik or nginx. This page provides real-world Docker Compose configurations for various deployment scenarios to help you get started faster.
|
||||
Self-hosted setups vary. You might run on a single VPS or a Kubernetes cluster, behind Cloudflare Tunnel, or behind a reverse proxy like Traefik or nginx. This page collects Docker Compose configurations for those cases.
|
||||
|
||||
These examples go beyond the basic setup in the [Self-Hosting with Docker](/self-hosting/docker) guide, showing production-ready configurations with reverse proxies, SSL termination, and other common patterns.
|
||||
They go further than the basic setup in the [Self-hosting with Docker](/self-hosting/docker) guide, with reverse proxies, SSL termination, and other common patterns.
|
||||
|
||||
<Info>
|
||||
**Help others by sharing your setup!** If you have a working configuration that isn't covered here, I'd love to
|
||||
include it. Simply [open a pull request](https://github.com/amruthpillai/reactive-resume) with your example added to
|
||||
this page. Your contribution helps the community and makes self-hosting easier for everyone.
|
||||
**Share your setup.** If you have a working configuration that isn't covered here, I'd love to include it. [Open a
|
||||
pull request](https://github.com/amruthpillai/reactive-resume) with your example added to this page.
|
||||
</Info>
|
||||
|
||||
---
|
||||
|
||||
## Docker with Traefik
|
||||
|
||||
This example uses [Traefik](https://traefik.io/) as a reverse proxy with automatic SSL certificate management via Let's Encrypt. Only the Reactive Resume app is exposed through Traefik—Postgres remains on an internal network.
|
||||
This example uses [Traefik](https://traefik.io/) as a reverse proxy with automatic SSL certificate management via Let's Encrypt. Postgres stays on an internal network. The Traefik dashboard is also routed, at `traefik.${DOMAIN}` behind basic auth — drop those labels if you do not want it reachable.
|
||||
|
||||
<Tip>
|
||||
Traefik automatically discovers services via Docker labels and handles SSL certificates, making it ideal for setups
|
||||
where you want minimal configuration.
|
||||
Traefik discovers services through Docker labels and handles SSL certificates, so it needs very little configuration.
|
||||
</Tip>
|
||||
|
||||
```yaml compose-traefik.yml lines expandable
|
||||
@@ -269,11 +267,11 @@ http {
|
||||
|
||||
## Docker Swarm
|
||||
|
||||
This example demonstrates a production-grade Docker Swarm deployment with multiple replicas, health checks, rolling updates, and Traefik integration. It includes SeaweedFS for S3-compatible storage and a PostgreSQL database with custom configuration.
|
||||
This example is a Docker Swarm deployment with health checks, rolling updates, and Traefik integration. It includes SeaweedFS for S3-compatible storage and a PostgreSQL database with custom configuration.
|
||||
|
||||
<Tip>
|
||||
Docker Swarm is great for multi-node deployments where you need high availability and easy scaling. The app service is
|
||||
configured with 2 replicas and rolling update strategy.
|
||||
Docker Swarm suits multi-node deployments that need high availability and simple scaling. Every service here starts
|
||||
at one replica; raise `deploy.replicas` on `reactive_resume` once you have more than one node.
|
||||
</Tip>
|
||||
|
||||
```yaml compose-swarm.yml lines expandable
|
||||
@@ -429,9 +427,9 @@ docker stack rm reactive_resume
|
||||
|
||||
---
|
||||
|
||||
## Contributing Your Setup
|
||||
## Contributing your setup
|
||||
|
||||
Have a different deployment setup that works well? Consider contributing it here. Some examples include:
|
||||
Have a different deployment setup that works well? Consider contributing it here. Some examples:
|
||||
|
||||
- Kubernetes / Helm charts
|
||||
- Cloudflare Tunnel
|
||||
|
||||
@@ -5,7 +5,7 @@ description: "Step-by-step guide to migrate a self-hosted Reactive Resume instan
|
||||
|
||||
## Overview
|
||||
|
||||
This guide walks you through migrating your Reactive Resume installation from **v4 to v5**. The migration process involves setting up a new v5 instance alongside your existing v4 instance, then transferring your users and resumes to the new system.
|
||||
To move a Reactive Resume installation from **v4 to v5**, you set up a new v5 instance alongside your existing v4 instance, then transfer your users and resumes across.
|
||||
|
||||
<Info>
|
||||
This page is for **v4 → v5 data migration** only. For normal v5 upgrades, use the [Self-Hosting with
|
||||
@@ -13,8 +13,8 @@ This guide walks you through migrating your Reactive Resume installation from **
|
||||
</Info>
|
||||
|
||||
<Warning>
|
||||
**Keep your v4 instance running** until you have successfully migrated all data to v5 and verified everything works
|
||||
correctly. This ensures you have a fallback in case anything goes wrong during the migration.
|
||||
**Keep your v4 instance running** until you have migrated all data to v5 and checked that everything works. That way
|
||||
you have a fallback if the migration goes wrong.
|
||||
</Warning>
|
||||
|
||||
## Prerequisites
|
||||
@@ -24,16 +24,16 @@ Before starting the migration, ensure you have:
|
||||
<CardGroup cols={2}>
|
||||
<Card title="Running v4 Instance">Your existing Reactive Resume v4 instance should be running and accessible.</Card>
|
||||
<Card title="New v5 Instance">
|
||||
A fresh Reactive Resume v5 instance set up and running. Follow the [Self-Hosting with Docker](/self-hosting/docker)
|
||||
A fresh Reactive Resume v5 instance set up and running. Follow the [Self-hosting with Docker](/self-hosting/docker)
|
||||
guide if you haven't done this yet.
|
||||
</Card>
|
||||
<Card title="Database Access">
|
||||
Access to both your v4 PostgreSQL database (source) and v5 PostgreSQL database (target).
|
||||
</Card>
|
||||
<Card title="Backup">A recent backup of your v4 database. Always backup before any migration.</Card>
|
||||
<Card title="Backup">A recent backup of your v4 database. Always back up before any migration.</Card>
|
||||
</CardGroup>
|
||||
|
||||
## Choosing a Migration Method
|
||||
## Choosing a migration method
|
||||
|
||||
The best migration approach depends on the size of your instance:
|
||||
|
||||
@@ -48,7 +48,7 @@ The best migration approach depends on the size of your instance:
|
||||
</Card>
|
||||
</CardGroup>
|
||||
|
||||
## Manual Migration (Small Instances)
|
||||
## Manual migration (small instances)
|
||||
|
||||
If you have only a few resumes to migrate, the simplest approach is to use the **Import Dialog** feature in v5.
|
||||
|
||||
@@ -58,7 +58,7 @@ If you have only a few resumes to migrate, the simplest approach is to use the *
|
||||
</Step>
|
||||
|
||||
<Step title="Import into v5">
|
||||
In your new v5 instance: 1. Log in or create a new account 2. Click **Create Resume** or use the **Import** option 3.
|
||||
In your new v5 instance: 1. Sign in or create a new account 2. Click **Create Resume** or use the **Import** option 3.
|
||||
Select the **Reactive Resume v4** format 4. Upload your exported JSON file The import process automatically converts
|
||||
the v4 format to v5.
|
||||
</Step>
|
||||
@@ -73,7 +73,7 @@ If you have only a few resumes to migrate, the simplest approach is to use the *
|
||||
between v4 and v5.
|
||||
</Tip>
|
||||
|
||||
## Automated Migration (Large Instances)
|
||||
## Automated migration (large instances)
|
||||
|
||||
For instances with many users and resumes, use the migration scripts to automate the process. The migration happens in two phases: first users, then resumes.
|
||||
|
||||
@@ -105,7 +105,7 @@ To run the migration scripts, you need the following installed on your host mach
|
||||
v4 and v5 databases; keep your actual v5 deployment on the latest version.
|
||||
</Info>
|
||||
|
||||
### Environment Setup
|
||||
### Environment setup
|
||||
|
||||
Create a `.env` file in the root of the repository with the following variables:
|
||||
|
||||
@@ -124,7 +124,7 @@ PRODUCTION_DATABASE_URL="postgresql://user:password@localhost:5432/reactive_resu
|
||||
|
||||
<Warning>`PRODUCTION_DATABASE_URL` is used only by these migration scripts. It is not a runtime app variable.</Warning>
|
||||
|
||||
### Step 1: Migrate Users
|
||||
### Step 1: Migrate users
|
||||
|
||||
The user migration script transfers all user accounts, authentication data, and two-factor settings from v4 to v5.
|
||||
|
||||
@@ -165,7 +165,7 @@ dotenvx run -- tsx scripts/migration/user.ts
|
||||
✅ User migration complete!
|
||||
```
|
||||
|
||||
### Step 2: Migrate Resumes
|
||||
### Step 2: Migrate resumes
|
||||
|
||||
After users are migrated, run the resume migration script. This script depends on the user ID mapping created in the previous step.
|
||||
|
||||
@@ -203,7 +203,7 @@ dotenvx run -- tsx scripts/migration/resume.ts
|
||||
✅ Resume migration complete!
|
||||
```
|
||||
|
||||
### Progress and Recovery
|
||||
### Progress and recovery
|
||||
|
||||
Both migration scripts support graceful shutdown and resume:
|
||||
|
||||
@@ -217,17 +217,17 @@ Both migration scripts support graceful shutdown and resume:
|
||||
running the scripts again.
|
||||
</Tip>
|
||||
|
||||
## Post-Migration Steps
|
||||
## Post-migration steps
|
||||
|
||||
After completing the migration:
|
||||
|
||||
<Steps>
|
||||
<Step title="Verify data integrity">
|
||||
Log into your v5 instance and spot-check several user accounts and resumes to ensure data transferred correctly.
|
||||
Sign in to your v5 instance and spot-check several user accounts and resumes to ensure data transferred correctly.
|
||||
</Step>
|
||||
|
||||
<Step title="Test functionality">
|
||||
- Create a test resume and export it as PDF - Verify social logins work (if configured) - Check that two-factor
|
||||
- Create a test resume and export it as PDF - Verify social sign-in works (if configured) - Check that two-factor
|
||||
authentication works for migrated users
|
||||
</Step>
|
||||
|
||||
@@ -240,7 +240,7 @@ After completing the migration:
|
||||
</Step>
|
||||
</Steps>
|
||||
|
||||
## Important Notes
|
||||
## Important notes
|
||||
|
||||
<AccordionGroup>
|
||||
<Accordion title="User passwords are preserved">
|
||||
|
||||
+14
-14
@@ -5,29 +5,29 @@ description: "Configure Single Sign-On for self-hosted Reactive Resume using cus
|
||||
|
||||
## Overview
|
||||
|
||||
Reactive Resume supports custom OAuth providers, allowing you to integrate with enterprise identity providers and self-hosted authentication solutions. This is particularly useful for organizations that want to:
|
||||
Reactive Resume supports custom OAuth providers, so you can sign in through an enterprise identity provider or a self-hosted authentication service. This helps organizations that want to:
|
||||
|
||||
- Use a centralized identity provider (Authentik, Authelia, Keycloak, etc.)
|
||||
- Enforce Single Sign-On (SSO) across all internal applications
|
||||
- Integrate with existing LDAP/Active Directory infrastructure
|
||||
|
||||
<Info>
|
||||
Custom OAuth is designed for **self-hosted instances**. If you're using the hosted version at
|
||||
Custom OAuth is for **self-hosted instances**. If you're using the hosted version at
|
||||
[rxresu.me](https://rxresu.me), you can use the built-in Google and GitHub sign-in options.
|
||||
</Info>
|
||||
|
||||
## Environment Variables
|
||||
## Environment variables
|
||||
|
||||
To enable a custom OAuth provider, you need to configure the following environment variables in your `.env` file:
|
||||
|
||||
### Required Variables
|
||||
### Required variables
|
||||
|
||||
| Variable | Description |
|
||||
| --------------------- | ------------------------------------------------- |
|
||||
| `OAUTH_CLIENT_ID` | The client ID provided by your OAuth provider |
|
||||
| `OAUTH_CLIENT_SECRET` | The client secret provided by your OAuth provider |
|
||||
|
||||
### Endpoint Configuration
|
||||
### Endpoint configuration
|
||||
|
||||
You must configure endpoints using **one** of these two methods:
|
||||
|
||||
@@ -60,7 +60,7 @@ You must configure endpoints using **one** of these two methods:
|
||||
</Tab>
|
||||
</Tabs>
|
||||
|
||||
### Optional Variables
|
||||
### Optional variables
|
||||
|
||||
| Variable | Description | Default |
|
||||
| ------------------------------------- | -------------------------------------------------------------------------------------- | ---------------------- |
|
||||
@@ -112,16 +112,16 @@ https://resume.example.com/api/auth/callback/custom
|
||||
{provider}` (for example `.../google`, `.../github`, `.../linkedin`).
|
||||
</Info>
|
||||
|
||||
## URL and Proxy Requirements
|
||||
## URL and proxy requirements
|
||||
|
||||
- Set `APP_URL` to the exact public URL users access (prefer HTTPS in production).
|
||||
- Auth metadata, JWKS, and OAuth callback URLs are derived from `APP_URL`.
|
||||
- Behind a reverse proxy, forward `Host` and `X-Forwarded-Proto` correctly, or cookie/session behavior may break.
|
||||
- `trustedOrigins` are derived from `APP_URL`, so alternate domains are not automatically trusted.
|
||||
|
||||
## Profile Mapping
|
||||
## Profile mapping
|
||||
|
||||
Reactive Resume automatically maps user profile data from the OAuth provider. The following fields are used:
|
||||
Reactive Resume maps user profile data from the OAuth provider using these fields:
|
||||
|
||||
| Reactive Resume Field | OAuth Profile Fields (in order of preference) |
|
||||
| --------------------- | --------------------------------------------- |
|
||||
@@ -134,7 +134,7 @@ Reactive Resume automatically maps user profile data from the OAuth provider. Th
|
||||
The OAuth provider **must** return an email address. If no email is provided, authentication will fail with an error.
|
||||
</Info>
|
||||
|
||||
## Provider-Specific Setup
|
||||
## Provider-specific setup
|
||||
|
||||
### Authentik
|
||||
|
||||
@@ -248,7 +248,7 @@ OAUTH_DISCOVERY_URL="https://keycloak.example.com/realms/myrealm/.well-known/ope
|
||||
</Step>
|
||||
</Steps>
|
||||
|
||||
### Generic OIDC Provider
|
||||
### Generic OIDC provider
|
||||
|
||||
For any other OIDC-compliant provider:
|
||||
|
||||
@@ -259,7 +259,7 @@ OAUTH_CLIENT_SECRET="your-client-secret"
|
||||
OAUTH_DISCOVERY_URL="https://sso.example.com/.well-known/openid-configuration"
|
||||
```
|
||||
|
||||
### Non-OIDC Provider (Manual Configuration)
|
||||
### Non-OIDC provider (manual configuration)
|
||||
|
||||
For providers that don't support OIDC discovery:
|
||||
|
||||
@@ -273,7 +273,7 @@ OAUTH_USER_INFO_URL="https://provider.example.com/oauth/userinfo"
|
||||
OAUTH_SCOPES="openid profile email"
|
||||
```
|
||||
|
||||
## Complete Example
|
||||
## Complete example
|
||||
|
||||
Here's a complete `.env` snippet showing custom OAuth alongside other authentication options:
|
||||
|
||||
@@ -351,7 +351,7 @@ OAUTH_DISCOVERY_URL="https://auth.company.com/application/o/reactive-resume/.wel
|
||||
</Accordion>
|
||||
</AccordionGroup>
|
||||
|
||||
## Security Considerations
|
||||
## Security considerations
|
||||
|
||||
<CardGroup cols={2}>
|
||||
<Card title="Use HTTPS" icon="lock">
|
||||
|
||||
@@ -1,38 +1,38 @@
|
||||
---
|
||||
title: "AI Resume Builder"
|
||||
title: "AI resume builder"
|
||||
description: "Use Reactive Resume as an AI resume builder with bring-your-own OpenAI, Anthropic, Gemini, OpenRouter, or Ollama providers for edits and drafts."
|
||||
---
|
||||
|
||||
Reactive Resume can be used as an AI-assisted resume builder, but AI is optional and bring-your-own-provider: you configure the provider, model, endpoint, and API key you want Reactive Resume to use.
|
||||
Reactive Resume works as an AI-assisted resume builder, but the AI is optional and bring-your-own-provider: you configure the provider, model, endpoint, and API key you want it to use.
|
||||
|
||||
## What AI does in Reactive Resume
|
||||
|
||||
AI features can help with AI-assisted changes in the builder, an optional review of your writing in the ATS checker, AI agent drafts, and supported import workflows. The core resume builder — and the ATS checker itself — still works without AI.
|
||||
AI can make assisted changes in the builder, review your writing in the ATS checker, produce agent drafts, and support import workflows. The builder and the ATS checker both work without it.
|
||||
|
||||
Use these guides for the full setup:
|
||||
|
||||
- [Using Artificial Intelligence](/guides/using-ai)
|
||||
- [Using artificial intelligence](/guides/using-ai)
|
||||
- [Using AI in the builder](/guides/using-ai-in-the-builder)
|
||||
- [Using the AI Agent Workspace](/guides/using-ai-agent)
|
||||
- [AI Agent Tools](/guides/ai-agent-tools)
|
||||
- [Using the AI Agent workspace](/guides/using-ai-agent)
|
||||
- [AI Agent tools](/guides/ai-agent-tools)
|
||||
|
||||
## Bring your own provider
|
||||
|
||||
Reactive Resume supports configuring an AI provider from the Integrations settings. The provider settings include the provider type, model, base URL when needed, and API key.
|
||||
You configure an AI provider from the Integrations settings: the provider type, the model, a base URL when one is needed, and the API key.
|
||||
|
||||
This is not positioned as a hosted AI-writing product. You choose whether to enable AI, which provider to connect, and when to send resume content to that provider.
|
||||
This is not a hosted AI-writing product. You decide whether to enable AI, which provider to connect, and when to send resume content to it.
|
||||
|
||||
## Where AI fits in the workflow
|
||||
|
||||
AI assistance is most useful after you already have resume content or structured source material. You can review suggestions, apply changes in the builder, or use agent drafts as isolated workspaces before deciding what belongs in your final resume.
|
||||
AI helps most once you already have resume content or structured source material. Review its suggestions, apply changes in the builder, or use agent drafts as separate workspaces before deciding what belongs in the final resume.
|
||||
|
||||
## When not to use AI
|
||||
|
||||
Do not use AI features if you do not want resume content sent to the provider you configure. Do not rely on AI output as final application material without review, and use the regular builder when you need direct manual control over exact wording.
|
||||
Do not use AI features if you do not want your resume content sent to the provider you configure. Do not treat AI output as final application material without reviewing it, and use the regular builder when you need exact control over the wording.
|
||||
|
||||
## Next action
|
||||
|
||||
Configure and test a provider with [Using Artificial Intelligence](/guides/using-ai). Then use [Using AI in the builder](/guides/using-ai-in-the-builder) for in-place assistance or [Using the AI Agent Workspace](/guides/using-ai-agent) for draft-based work.
|
||||
Configure and test a provider with [Using artificial intelligence](/guides/using-ai). Then use [Using AI in the builder](/guides/using-ai-in-the-builder) for in-place help, or [Using the AI Agent workspace](/guides/using-ai-agent) for draft-based work.
|
||||
|
||||
<Warning>
|
||||
Review AI-generated resume content before using it in applications. You are responsible for the accuracy of the final
|
||||
|
||||
@@ -1,21 +1,21 @@
|
||||
---
|
||||
title: "API and MCP Resume Automation"
|
||||
title: "API and MCP resume automation"
|
||||
description: "Automate resume workflows in Reactive Resume with API keys, the Patch API, the MCP server, AI agent tools, and the JSON resume schema."
|
||||
---
|
||||
|
||||
Reactive Resume supports automation through authenticated API access and an MCP server that lets compatible tools work with resumes and job applications. Agents can list, read, create, import, duplicate, and patch resumes, then track applications, move opportunities through stages, add notes and follow-ups, attach sent documents, and run Application Copilot actions.
|
||||
Reactive Resume supports automation through authenticated API access and an MCP server, so compatible tools can work with your resumes and job applications. Agents can list, read, create, import, duplicate, and patch resumes. They can also track applications, move opportunities through stages, add notes and follow-ups, attach sent documents, and run Application Copilot actions.
|
||||
|
||||
## Automation options
|
||||
|
||||
Use the API when you want direct programmatic access from scripts, services, or integrations. Use MCP when you want an AI tool or agent that supports the Model Context Protocol to work with your resumes through exposed tools.
|
||||
Use the API for direct programmatic access from scripts, services, or integrations. Use MCP when you want an AI tool or agent that speaks the Model Context Protocol to work with your resumes through exposed tools.
|
||||
|
||||
Key docs:
|
||||
|
||||
- [Using the API](/guides/using-the-api)
|
||||
- [Using the Patch API](/guides/using-the-patch-api)
|
||||
- [Using the MCP Server](/guides/using-the-mcp-server)
|
||||
- [AI Agent Tools](/guides/ai-agent-tools)
|
||||
- [JSON Resume Schema](/guides/json-resume-schema)
|
||||
- [Using the patch API](/guides/using-the-patch-api)
|
||||
- [Using the MCP server](/guides/using-the-mcp-server)
|
||||
- [AI Agent tools](/guides/ai-agent-tools)
|
||||
- [JSON Resume schema](/guides/json-resume-schema)
|
||||
|
||||
## Common automation workflows
|
||||
|
||||
@@ -33,11 +33,11 @@ You can build workflows that:
|
||||
- Score a linked resume against a job description and create a tailored resume copy.
|
||||
- Draft cover letters and recruiter follow-ups from saved application context.
|
||||
|
||||
The Patch API is the safest starting point for targeted resume updates because it is designed around explicit changes to existing resume data.
|
||||
Start with the Patch API for targeted resume updates. It is the safest option because it is built around explicit changes to existing resume data.
|
||||
|
||||
## Authentication and scope
|
||||
|
||||
API requests use API keys. MCP can use OAuth2 in clients that support it, with API keys available as a fallback. If you self-host, use your own instance URL for API and MCP endpoints.
|
||||
API requests use API keys. MCP can use OAuth2 in clients that support it, with API keys as a fallback. If you self-host, use your own instance URL for the API and MCP endpoints.
|
||||
|
||||
<Info>
|
||||
Automation changes affect the resumes available to the authenticated account or instance. Test workflows on a copy of a
|
||||
@@ -46,8 +46,8 @@ API requests use API keys. MCP can use OAuth2 in clients that support it, with A
|
||||
|
||||
## When not to use automation
|
||||
|
||||
Do not start with API or MCP automation when you only need to edit one resume manually. The builder is usually faster for one-off changes, template selection, and visual review. Avoid automation for important resume updates unless you can test the exact changes on a copy first.
|
||||
Do not reach for API or MCP automation when you only need to edit one resume by hand. The builder is faster for one-off changes, template selection, and visual review. Avoid automation for important resume updates unless you can test the exact changes on a copy first.
|
||||
|
||||
## Next action
|
||||
|
||||
For scripts and integrations, create an API key with [Using the API](/guides/using-the-api), then use [Using the Patch API](/guides/using-the-patch-api) for targeted edits. For agent workflows, start with [Using the MCP Server](/guides/using-the-mcp-server).
|
||||
For scripts and integrations, create an API key with [Using the API](/guides/using-the-api), then use [Using the patch API](/guides/using-the-patch-api) for targeted edits. For agent workflows, start with [Using the MCP server](/guides/using-the-mcp-server).
|
||||
|
||||
@@ -1,39 +1,39 @@
|
||||
---
|
||||
title: "Export and Share Resumes"
|
||||
title: "Export and share resumes"
|
||||
description: "Export Reactive Resume resumes as PDF, DOCX, Markdown, or JSON files and share password-protected public URLs with recruiters and hiring managers."
|
||||
---
|
||||
|
||||
Reactive Resume lets you export resumes as PDFs and, when useful, share a public resume URL with human recipients such as recruiters, hiring managers, collaborators, or your own portfolio visitors. Public resume URLs are not search-indexed by default.
|
||||
Reactive Resume exports resumes as PDFs, and it can also give you a public resume URL to send to a person: a recruiter, a hiring manager, a collaborator, or a visitor to your portfolio. Public resume URLs are not search-indexed by default.
|
||||
|
||||
## Export a PDF
|
||||
|
||||
PDF export is the right choice when an application requires a file upload or when you want a fixed document to send by email.
|
||||
Export a PDF when an application requires a file upload, or when you want a fixed document to send by email.
|
||||
|
||||
See [Exporting your resume](/guides/exporting-your-resume) for the export workflow.
|
||||
|
||||
## When to export
|
||||
|
||||
Export a PDF when a job application requires an uploaded document, when you need a fixed copy for records, or when you want to send a file that will not change after you submit it.
|
||||
Export a PDF when a job application requires an uploaded document, when you need a fixed copy for your records, or when you want to send a file that will not change after you submit it.
|
||||
|
||||
## When to share a link
|
||||
|
||||
Share a public resume URL when a human recipient can open a link and you want them to see the current version of your resume.
|
||||
Share a public resume URL when the recipient can open a link and you want them to see the current version of your resume.
|
||||
|
||||
## Share a public resume URL
|
||||
|
||||
Public sharing creates a URL you can send to someone else. The public page shows the current version of your resume and can include a download option for viewers.
|
||||
Public sharing creates a URL you can send to someone else. The page shows the current version of your resume and can offer a download to viewers.
|
||||
|
||||
Public resume URLs are intended for human recipients who receive or discover the link from you.
|
||||
Public resume URLs are meant for people who get the link from you or find it through you.
|
||||
|
||||
## When not to share only a link
|
||||
|
||||
Do not send only a public URL when an application explicitly requires a PDF or document upload. Do not use public sharing for restricted audiences unless you also use password protection or keep the resume private until you are ready to share it.
|
||||
Do not send only a public URL when an application requires a PDF or document upload. Do not use public sharing for a restricted audience unless you turn on password protection, or keep the resume private until you are ready.
|
||||
|
||||
See [Sharing your resume publicly](/guides/sharing-your-resume-publicly) for setup, password protection, statistics, and how to turn public access off.
|
||||
|
||||
## Use the builder dock
|
||||
|
||||
The builder dock includes shortcuts that support common editing and sharing actions from the resume builder.
|
||||
The builder dock has shortcuts for common editing and sharing actions inside the resume builder.
|
||||
|
||||
See [Using the builder dock](/guides/using-the-builder-dock) for the available actions.
|
||||
|
||||
@@ -48,4 +48,4 @@ See [Using the builder dock](/guides/using-the-builder-dock) for the available a
|
||||
|
||||
## Next action
|
||||
|
||||
Use [Exporting your resume](/guides/exporting-your-resume) if you need a file, or [Sharing your resume publicly](/guides/sharing-your-resume-publicly) if a link is acceptable.
|
||||
Use [Exporting your resume](/guides/exporting-your-resume) if you need a file, or [Sharing your resume publicly](/guides/sharing-your-resume-publicly) if a link will do.
|
||||
|
||||
@@ -1,9 +1,9 @@
|
||||
---
|
||||
title: "Free Resume Builder"
|
||||
title: "Free resume builder"
|
||||
description: "Reactive Resume is a free resume builder with no paywalls or premium tiers for creating, editing, exporting, and sharing unlimited resumes online."
|
||||
---
|
||||
|
||||
Reactive Resume is a free resume builder for creating resumes in a browser, choosing a template, exporting a PDF, and sharing a human-readable public URL when you want someone else to view it. Public resume URLs are shareable for human recipients and are not search-indexed by default.
|
||||
Reactive Resume is a free resume builder. Write your resume in a browser, pick a template, export a PDF, and share a public URL when you want someone else to read it. Public resume URLs are meant for people you send them to, and they are not search-indexed by default.
|
||||
|
||||
## What you can do for free
|
||||
|
||||
@@ -13,11 +13,11 @@ Reactive Resume is a free resume builder for creating resumes in a browser, choo
|
||||
- Export your resume as a PDF.
|
||||
- Share a public resume URL with recruiters, hiring managers, or collaborators.
|
||||
|
||||
Start with [Introduction](/getting-started) for the product overview or follow the [Quickstart](/getting-started/quickstart) to create your first resume on [rxresu.me](https://rxresu.me).
|
||||
Start with [Introduction](/getting-started) for the product overview, or follow the [Quickstart](/getting-started/quickstart) to create your first resume on [rxresu.me](https://rxresu.me).
|
||||
|
||||
## Builder workflow
|
||||
|
||||
Reactive Resume focuses on the core resume workflow: add your profile, work history, education, skills, projects, and other sections, then adjust layout and template choices before exporting.
|
||||
Reactive Resume sticks to the core resume workflow: add your profile, work history, education, skills, projects, and other sections, then adjust the layout and template before exporting.
|
||||
|
||||
Useful guides:
|
||||
|
||||
@@ -28,21 +28,21 @@ Useful guides:
|
||||
|
||||
## When to use this path
|
||||
|
||||
Use the hosted app when you want to create a resume quickly without running infrastructure. It fits personal resume editing, template selection, PDF export, and sharing a public resume URL with people who need to review your resume.
|
||||
Use the hosted app when you want a resume quickly and do not want to run any infrastructure. It covers personal resume editing, template selection, PDF export, and sharing a public URL with people who need to read your resume.
|
||||
|
||||
## When not to use this path
|
||||
|
||||
Do not rely on the hosted app alone if your organization requires a controlled deployment, custom auth, or specific data residency rules. In that case, review [Self-hosting with Docker](/self-hosting/docker). If an application requires a file upload, export a PDF instead of sending only a public URL.
|
||||
Do not rely on the hosted app alone if your organization requires a controlled deployment, custom auth, or specific data residency rules. Review [Self-hosting with Docker](/self-hosting/docker) instead. If an application requires a file upload, export a PDF rather than sending only a public URL.
|
||||
|
||||
## Export and sharing options
|
||||
|
||||
You can download a PDF for applications that require a file. You can also enable a public resume URL for human recipients when a link is more convenient than an attachment.
|
||||
Download a PDF for applications that need a file. You can also turn on a public resume URL when a link is more convenient than an attachment.
|
||||
|
||||
Public resume URLs are for sharing with people you choose to send the link to. For details, see [Exporting your resume](/guides/exporting-your-resume) and [Sharing your resume publicly](/guides/sharing-your-resume-publicly).
|
||||
Public resume URLs are for the people you send the link to. For details, see [Exporting your resume](/guides/exporting-your-resume) and [Sharing your resume publicly](/guides/sharing-your-resume-publicly).
|
||||
|
||||
## Next action
|
||||
|
||||
Open [rxresu.me](https://rxresu.me) to create a resume, or follow [Creating your first resume](/guides/creating-your-first-resume) if you want the guided workflow.
|
||||
Open [rxresu.me](https://rxresu.me) to create a resume, or follow [Creating your first resume](/guides/creating-your-first-resume) for the guided workflow.
|
||||
|
||||
## Related resources
|
||||
|
||||
|
||||
@@ -1,19 +1,19 @@
|
||||
---
|
||||
title: "Open-Source Resume Builder"
|
||||
title: "Open-source resume builder"
|
||||
description: "Learn how Reactive Resume works as an open-source resume builder with public source code, an MIT license, and self-hosting support."
|
||||
---
|
||||
|
||||
Reactive Resume is an open-source resume builder: its source code is public, it is licensed under MIT, and you can use the hosted app or run your own instance.
|
||||
Reactive Resume is an open-source resume builder. The source code is public, the license is MIT, and you can either use the hosted app or run your own instance.
|
||||
|
||||
## What open source means here
|
||||
|
||||
The project repository is available on [GitHub](https://github.com/amruthpillai/reactive-resume). You can inspect the code, report issues, contribute improvements, and review how the resume builder, API, self-hosting setup, and documentation are implemented.
|
||||
The project repository is on [GitHub](https://github.com/amruthpillai/reactive-resume). You can read the code, report issues, contribute improvements, and see how the builder, the API, the self-hosting setup, and the documentation are put together.
|
||||
|
||||
The license is documented in [License](/legal/license).
|
||||
|
||||
## Product capabilities
|
||||
|
||||
Reactive Resume includes a browser-based builder, resume templates, PDF export, public sharing links for human recipients, API access, MCP support, and optional AI-assisted workflows. Public resume URLs are shareable for human recipients and are not search-indexed by default. The main user workflow starts in the hosted app at [rxresu.me](https://rxresu.me) or on a self-hosted deployment.
|
||||
Reactive Resume has a browser-based builder, resume templates, PDF export, public sharing links, API access, MCP support, and optional AI-assisted workflows. Public resume URLs are meant for the people you share them with and are not search-indexed by default. The main workflow starts in the hosted app at [rxresu.me](https://rxresu.me) or on your own deployment.
|
||||
|
||||
Helpful starting points:
|
||||
|
||||
@@ -24,15 +24,15 @@ Helpful starting points:
|
||||
|
||||
## When to use this path
|
||||
|
||||
Use the open-source path when you want transparency, want to inspect how resume data and exports are handled, want to contribute fixes or translations, or need the option to run your own deployment.
|
||||
Use the open-source path when you want to see how resume data and exports are handled, contribute fixes or translations, or keep the option of running your own deployment.
|
||||
|
||||
## When not to use this path
|
||||
|
||||
Do not start with the source code if your immediate goal is only to build a resume. Use [rxresu.me](https://rxresu.me) or the [Quickstart](/getting-started/quickstart) first. Do not assume open source automatically covers your compliance needs; if you operate an instance, review the self-hosting and privacy docs.
|
||||
Do not start with the source code if you only want to build a resume. Use [rxresu.me](https://rxresu.me) or the [Quickstart](/getting-started/quickstart) first. Do not assume open source covers your compliance needs on its own; if you run an instance, read the self-hosting and privacy docs.
|
||||
|
||||
## Contribution and customization
|
||||
|
||||
If you want to contribute or understand the codebase, start with the contributor docs. They describe the local development setup, package layout, and project conventions.
|
||||
To contribute or to understand the codebase, start with the contributor docs. They cover the local development setup, the package layout, and the project conventions.
|
||||
|
||||
<CardGroup cols={2}>
|
||||
<Card title="Development setup" icon="code" href="/contributing/development">
|
||||
@@ -51,4 +51,4 @@ If you want to contribute or understand the codebase, start with the contributor
|
||||
|
||||
## Next action
|
||||
|
||||
If you want to contribute, set up the project with [Development setup](/contributing/development). If you want to operate it yourself, start with [Self-hosting with Docker](/self-hosting/docker).
|
||||
To contribute, set up the project with [Development setup](/contributing/development). To run it yourself, start with [Self-hosting with Docker](/self-hosting/docker).
|
||||
|
||||
@@ -1,40 +1,40 @@
|
||||
---
|
||||
title: "Privacy-Focused Resume Builder"
|
||||
description: "Reactive Resume's privacy-focused design: open source transparency, self-hosting, public sharing controls, and optional bring-your-own AI providers."
|
||||
title: "Privacy-focused resume builder"
|
||||
description: "Reactive Resume's privacy-focused design: open-source transparency, self-hosting, public sharing controls, and optional bring-your-own AI providers."
|
||||
---
|
||||
|
||||
Reactive Resume is a privacy-focused resume builder because it is open source, can be self-hosted, supports private-by-default resume editing, and makes sharing and optional AI features explicit choices.
|
||||
Reactive Resume is a privacy-focused resume builder: the code is open source, you can self-host it, editing is private by default, and both sharing and AI are choices you make yourself.
|
||||
|
||||
## Privacy controls in the resume workflow
|
||||
|
||||
Resumes are edited inside your account. When you want someone else to view a resume, you can enable a public URL and send that link to human recipients. Public resume URLs are not search-indexed by default. Public access can be turned off again, and public resumes can optionally require a password.
|
||||
You edit resumes inside your account. When you want someone else to read one, turn on a public URL and send them the link. Public resume URLs are not search-indexed by default. You can turn public access off again, and a public resume can require a password.
|
||||
|
||||
For the sharing workflow, see [Sharing your resume publicly](/guides/sharing-your-resume-publicly). For account-level security, see [Setting up two-factor authentication](/guides/setting-up-two-factor-authentication) and [Setting up passkeys](/guides/setting-up-passkeys).
|
||||
For the sharing workflow, see [Sharing your resume publicly](/guides/sharing-your-resume-publicly). For account security, see [Setting up two-factor authentication](/guides/setting-up-two-factor-authentication) and [Setting up passkeys](/guides/setting-up-passkeys).
|
||||
|
||||
## When to use this path
|
||||
|
||||
Use this path when you want to understand the privacy tradeoffs before choosing hosted use, self-hosting, public sharing, API automation, or optional AI features. It is especially useful if your resume contains sensitive job-search information or if you plan to share links selectively.
|
||||
Use this path when you want to understand the tradeoffs before choosing hosted use, self-hosting, public sharing, API automation, or AI features. It matters most if your resume holds sensitive job-search information, or if you plan to share links with only a few people.
|
||||
|
||||
## When not to use this path
|
||||
|
||||
Do not treat public sharing as private access control by itself. Use password protection or keep the resume private if the link should only be opened by specific people. Do not enable AI features unless you are comfortable sending relevant prompts and resume content to the provider you configure.
|
||||
Do not treat public sharing as access control. Use password protection, or keep the resume private, if only specific people should open the link. Do not turn on AI features unless you are comfortable sending the prompts and resume content to the provider you configure.
|
||||
|
||||
## Open source and self-hosting
|
||||
|
||||
The source code is available on [GitHub](https://github.com/amruthpillai/reactive-resume), so you can inspect how the application works. If you need direct control over infrastructure, storage, auth providers, and deployment policy, you can self-host Reactive Resume.
|
||||
The source code is on [GitHub](https://github.com/amruthpillai/reactive-resume), so you can read how the application works. If you need direct control over infrastructure, storage, auth providers, and deployment policy, run your own instance.
|
||||
|
||||
Start with:
|
||||
|
||||
- [Self-hosting with Docker](/self-hosting/docker)
|
||||
- [Self-hosting examples](/self-hosting/examples)
|
||||
- [Single sign-on](/self-hosting/sso)
|
||||
- [Privacy policy](/legal/privacy-policy)
|
||||
- [Privacy Policy](/legal/privacy-policy)
|
||||
|
||||
## Optional AI features
|
||||
|
||||
AI features are optional. Reactive Resume does not need AI to create, edit, export, or share a resume. When you choose to use AI-assisted features, you configure a provider and key for the provider you want to use.
|
||||
AI is optional. Reactive Resume does not need it to create, edit, export, or share a resume. If you do want AI help, you configure the provider and the key yourself.
|
||||
|
||||
For setup details, see [Using Artificial Intelligence](/guides/using-ai), [Using AI in the builder](/guides/using-ai-in-the-builder), and [Using the AI Agent Workspace](/guides/using-ai-agent).
|
||||
For setup details, see [Using artificial intelligence](/guides/using-ai), [Using AI in the builder](/guides/using-ai-in-the-builder), and [Using the AI Agent workspace](/guides/using-ai-agent).
|
||||
|
||||
<Info>
|
||||
Review the privacy policy for the instance you use. If you self-host, you are responsible for the deployment's data
|
||||
@@ -43,4 +43,4 @@ For setup details, see [Using Artificial Intelligence](/guides/using-ai), [Using
|
||||
|
||||
## Next action
|
||||
|
||||
Review [Privacy Policy](/legal/privacy-policy), then choose either [Sharing your resume publicly](/guides/sharing-your-resume-publicly) for link controls or [Self-hosting with Docker](/self-hosting/docker) for infrastructure control.
|
||||
Read the [Privacy Policy](/legal/privacy-policy), then go to [Sharing your resume publicly](/guides/sharing-your-resume-publicly) for link controls or [Self-hosting with Docker](/self-hosting/docker) for infrastructure control.
|
||||
|
||||
@@ -1,13 +1,13 @@
|
||||
---
|
||||
title: "Self-Hosted Resume Builder"
|
||||
title: "Self-hosted resume builder"
|
||||
description: "Run Reactive Resume as a self-hosted resume builder with Docker Compose, PostgreSQL, optional object storage, Single Sign-On, and v4 to v5 migration."
|
||||
---
|
||||
|
||||
Reactive Resume can be run as a self-hosted resume builder when you want to operate the app on your own infrastructure instead of using the hosted instance.
|
||||
You can run Reactive Resume on your own infrastructure instead of using the hosted instance.
|
||||
|
||||
## When self-hosting is a good fit
|
||||
|
||||
Self-hosting is useful when you need control over deployment, domain, database, storage, email delivery, authentication providers, and operational policies. The Docker guide is the main setup path for most deployments.
|
||||
Self-hosting helps when you need control over the deployment, domain, database, storage, email delivery, authentication providers, and operational policy. The Docker guide is the main setup path for most deployments.
|
||||
|
||||
Start here:
|
||||
|
||||
@@ -26,13 +26,13 @@ A typical self-hosted deployment uses:
|
||||
- Optional S3-compatible storage for uploads.
|
||||
- Optional SSO or custom OAuth configuration.
|
||||
|
||||
The Docker guide includes the environment variable reference and a Compose example.
|
||||
The Docker guide has the environment variable reference and a Compose example.
|
||||
|
||||
## Feature considerations
|
||||
|
||||
Some features require extra configuration. For example, saved AI providers need server-side encryption configuration, and the AI Agent workspace uses Redis. Self-hosted deployments can also expose API and MCP endpoints from their own domain.
|
||||
Some features need extra configuration. Saved AI providers need server-side encryption configured, and the AI Agent workspace uses Redis. Self-hosted deployments can also expose API and MCP endpoints from their own domain.
|
||||
|
||||
For automation setup on self-hosted instances, see [Using the API](/guides/using-the-api) and [Using the MCP Server](/guides/using-the-mcp-server).
|
||||
For automation setup on a self-hosted instance, see [Using the API](/guides/using-the-api) and [Using the MCP server](/guides/using-the-mcp-server).
|
||||
|
||||
<Tip>
|
||||
Replace hosted URLs such as <code>https://rxresu.me</code> with your own instance URL when following API, MCP, or
|
||||
|
||||
Reference in New Issue
Block a user