Skip to content

A one-of-a-kind resume builder that keeps your privacy in mind. Completely secure, customizable, portable, open-source and free forever. Try it out today!

docs: refresh product guides and contributor documentation

Amruth Pillaiaef0476fe68f
diff --git a/docs/changelog/index.mdx b/docs/changelog/index.mdx
index 8770de3af..5e6e05496 100644
--- a/docs/changelog/index.mdx
+++ b/docs/changelog/index.mdx
@@ -1558,7 +1558,7 @@ production deployments.
- **No more Browserless / Chromium dependency.** From v5.1.0 onwards, you do **not** need to run a `printer`, Browserless, or headless Chrome service alongside Reactive Resume. PDF generation is now performed entirely in your browser via `@react-pdf/renderer`. The `BROWSERLESS_TOKEN`, `PRINTER_ENDPOINT`, `PRINTER_APP_URL`, and `FLAG_DEBUG_PRINTER` environment variables are no longer read and can be removed from your `.env`.
- **Database migrations.** This release ships several new schema migrations to bring the resume model up to date. They run automatically on container start, but you should **back up your PostgreSQL database before upgrading** in case rollback is needed.
- **Custom CSS has been removed.** Because the resume PDF is no longer produced by a headless browser, raw CSS no longer applies to the exported document. A first-class template-customization story is on the roadmap for a future release.
-- **Job Listings has been removed.** The JSearch/RapidAPI-backed job listings feature and its settings were removed in the v5.1.0 transition. The old job-search settings path now redirects to **Integrations**. To tailor a resume, paste a job description into the AI Agent; see [Using the AI Agent workspace](/guides/using-ai-agent#tailor-a-resume-to-a-supplied-job-description).
+- **Job Listings has been removed.** The JSearch/RapidAPI-backed job listings feature and its settings were removed in the v5.1.0 transition. The old job-search settings path now redirects to **Integrations**. To tailor a resume, paste a job description into the AI Agent. For the current workflow, see [Tailoring a resume for a job](/guides/tailoring-a-resume-for-a-job).
</Note>
@@ -1898,7 +1898,7 @@ production deployments.
<Update label="v5.0.5" description="31st January 2026">
## Features & Improvements
-- Implemented Cover Letter functionality as a custom section in the resume builder. [(link)](/guides/adding-a-cover-letter)
+- Implemented Cover Letter functionality as a custom section in the resume builder. Cover letters are separate documents in v6; see [Writing a cover letter](/guides/writing-a-cover-letter) for the current workflow.
- Added full-screen mode to the rich text editor for distraction-free writing.
- Introduced a new custom section type: `summary`, enabling users to add extra summary sections.
- Added `useFormBlocker` hook to prevent dialogs from being closed with unsaved form changes.
diff --git a/docs/contributing/architecture.mdx b/docs/contributing/architecture.mdx
index a4e80bed9..aaaddaea7 100644
--- a/docs/contributing/architecture.mdx
+++ b/docs/contributing/architecture.mdx
@@ -1,24 +1,27 @@
---
title: "Project architecture"
-description: "How the Reactive Resume monorepo fits together: the web and server apps, shared packages, runtime boundaries, and where new code belongs."
+description: "How the Reactive Resume monorepo fits together: web, server and native apps, shared packages, runtime boundaries, and where new code belongs."
---
Reactive Resume is a TypeScript monorepo managed with pnpm workspaces and Turborepo. This page explains how the pieces fit together, so you can find the code behind a feature and know where a change belongs. To get a working checkout first, see [Development setup](/contributing/development).
## The big picture
-There are two apps and a set of shared packages:
+There are three apps and a set of shared packages:
- **`apps/web`** is a client-rendered React 19 single-page app built with Vite, TanStack Router, TanStack Query, Tailwind CSS, and Lingui for translations.
- **`apps/server`** is a Hono application on Node.js. It serves the API, authentication, the MCP server, uploads, OpenAPI, and the built web app.
-- **`packages/*`** hold everything the apps share: API business logic, authentication, database access, schemas, PDF and DOCX rendering, and UI primitives.
+- **`apps/mobile`** is an Expo / React Native app for iOS and Android, with Expo Router navigation and a native Forme PDF renderer.
+- **`packages/*`** hold everything the apps share: API business logic, authentication, database access, schemas, document rendering and export, and UI primitives.
-The browser talks to the server through [oRPC](https://orpc.unnoq.com/) at `/api/rpc`. [Better Auth](https://www.better-auth.com/) handles sign-in, sessions, passkeys, two-factor authentication, API keys, and the OAuth provider used by MCP clients. [Drizzle](https://orm.drizzle.team/) talks to PostgreSQL.
+The browser and native app talk to the same server through [oRPC](https://orpc.unnoq.com/) at `/api/rpc`. The browser sends session cookies; the native client sends the signed-in server's bearer token. [Better Auth](https://www.better-auth.com/) handles sign-in, sessions, passkeys, two-factor authentication, API keys, and the OAuth provider used by MCP clients. [Drizzle](https://orm.drizzle.team/) talks to PostgreSQL.
```mermaid
flowchart TD
Browser["Browser: apps/web SPA"] -->|"oRPC /api/rpc"| Server
Browser -->|"Forme (WebAssembly)"| BrowserPDF["PDF in the browser"]
+ Mobile["Native app: apps/mobile"] -->|"oRPC /api/rpc"| Server
+ Mobile -->|"packages/forme-native"| NativePDF["PDF on the device"]
MCPClient["MCP client"] -->|"/mcp"| Server
subgraph Server["apps/server (Hono)"]
@@ -41,6 +44,7 @@ flowchart TD
- **Development.** `pnpm dev` starts Vite on `PORT` (default `3000`), the Hono server on `SERVER_PORT` (default `3001`), and the email template preview on port `3002`. Vite proxies `/api`, `/mcp`, `/uploads`, `/.well-known`, and `/schema.json` to Hono, so you always open `http://localhost:3000`.
- **Docker.** The production image runs one Node.js process on port `3000`. Hono mounts the API, auth, MCP, and static routes, then serves the built web app.
- **Vercel.** One project deploys two services: `frontend` serves the static web build from the CDN, and `backend` runs the same Hono app in a Node.js Function. See [Deployment checks](/contributing/deployment-checks).
+- **Native apps.** `pnpm dev:mobile` starts Expo. The installed app connects to its selected server; it does not run the Hono server or database on the device. Keep server contracts backward compatible because older app builds remain in use.
There is no request-time React server rendering. The web build prerenders the marketing homepage for each locale, and `apps/server/src/static/web.ts` serves HTML shells with OpenGraph, canonical, and JSON-LD metadata injected.
@@ -50,28 +54,31 @@ The server checks the environment, applies database migrations, and verifies the
## Workspace map
-| Workspace | What it owns |
-| --------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `apps/web` | Routes (`src/routes`, file-based), user-facing features (`src/features`), the PDF.js preview and public viewer, the PWA, and the oRPC browser client |
-| `apps/server` | Hono route composition (`src/http`), RPC and OpenAPI adapters, the MCP transport, static and upload handlers, SEO for HTML shells, and startup checks |
-| `packages/api` | oRPC procedures and business logic, one folder per feature under `src/features/*` |
-| `packages/auth` | Better Auth configuration, helpers, and types |
-| `packages/db` | Drizzle client and schema; generated migrations live in the root `migrations/` folder |
-| `packages/env` | Server environment validation; loads the root `.env` |
-| `packages/schema` | Zod schemas for resumes, cover letters, applications, pages, and templates |
-| `packages/resume` | Pure resume logic with no database, HTTP, or DOM dependencies, such as JSON Patch helpers and social network icons |
-| `packages/pdf` | Resume templates (which also lay out cover letters), the Forme adapter, font resolution, custom-style support, and browser and server PDF adapters |
-| `packages/docx` | DOCX export |
-| `packages/mcp` | MCP tools, prompts, resources, and the server card |
-| `packages/ai` | AI provider types, prompts, and model-facing helpers |
-| `packages/import` | Resume importers |
-| `packages/ui` | Shared UI primitives and hooks in the Base UI / shadcn style |
-| `packages/fonts` | Font metadata |
-| `packages/email` | Email transport and templates |
-| `packages/utils` | Narrow cross-cutting helpers behind explicit export subpaths |
-| `packages/config` | Shared TypeScript and tooling configuration |
-| `packages/dsh-plugin` | A separately built and published plugin that connects a DeepSeek Harness session to Reactive Resume over MCP |
-| `tooling` | Development-only scripts: PDF translation catalog, semantic CSS reference, icon builds, deployment smoke test |
+| Workspace | What it owns |
+| ----------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `apps/web` | Routes (`src/routes`, file-based), user-facing features (`src/features`), the PDF.js preview and public viewer, the PWA, and the oRPC browser client |
+| `apps/server` | Hono route composition (`src/http`), RPC and OpenAPI adapters, the MCP transport, static and upload handlers, SEO for HTML shells, and startup checks |
+| `apps/mobile` | Expo Router screens (`app`), native workflows (`src/features`), account-scoped drafts, the bearer-token API client and device UI |
+| `packages/api` | oRPC procedures and business logic, one folder per feature under `src/features/*` |
+| `packages/auth` | Better Auth configuration, helpers, and types |
+| `packages/db` | Drizzle client and schema; generated migrations live in the root `migrations/` folder |
+| `packages/env` | Server environment validation; loads the root `.env` |
+| `packages/schema` | Zod schemas for resumes, cover letters, applications, pages, and templates |
+| `packages/resume` | Pure resume logic with no database, HTTP, or DOM dependencies, such as JSON Patch helpers and social network icons |
+| `packages/pdf` | Resume templates (which also lay out cover letters), the Forme adapter, font resolution, custom-style support, and browser and server PDF adapters |
+| `packages/docx` | DOCX export |
+| `packages/odt` | ODT export |
+| `packages/forme-native` | Native Forme renderer and its iOS/Android bindings |
+| `packages/mcp` | MCP tools, prompts, resources, and the server card |
+| `packages/ai` | AI provider types, prompts, and model-facing helpers |
+| `packages/import` | Resume importers |
+| `packages/ui` | Shared UI primitives and hooks in the Base UI / shadcn style |
+| `packages/fonts` | Font metadata |
+| `packages/email` | Email transport and templates |
+| `packages/utils` | Narrow cross-cutting helpers behind explicit export subpaths |
+| `packages/config` | Shared TypeScript and tooling configuration |
+| `packages/dsh-plugin` | A separately built and published plugin that connects a DeepSeek Harness session to Reactive Resume over MCP |
+| `tooling` | Development-only scripts: PDF translation catalog, semantic CSS reference, icon builds, deployment smoke test |
Internal packages are consumed as source through the `exports` map in each `package.json`, which points at `src` files. Don't expect a `dist` folder unless a package builds one explicitly.
@@ -84,12 +91,15 @@ Turbo hashes shared Vitest configuration and setup files, tracks transitive sour
| You are changing | Put it here |
| ----------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
| A page, loader, or user workflow | A route in `apps/web/src/routes` plus the feature folder in `apps/web/src/features/<area>` |
+| A native screen or device workflow | `apps/mobile/app` and `apps/mobile/src/features/<area>`; share domain behavior through workspace packages |
| An authenticated API procedure or business rule | `packages/api/src/features/<area>` |
| Pure resume data behavior | `packages/resume` |
| The shape of resume data | `packages/schema` first, then API DTOs, importers, PDF templates, and web forms that use it |
| A PDF template or rendering behavior | `packages/pdf` |
| PDF.js canvas or viewer UI | `apps/web/src/features/resume` (never `packages/pdf`) |
| DOCX export | `packages/docx` |
+| ODT export | `packages/odt` |
+| Native PDF engine or platform bindings | `packages/forme-native` |
| An MCP tool, prompt, or resource | `packages/mcp` |
| A generic UI primitive or hook | `packages/ui`; workflow-specific UI stays in its web feature |
| A database column or table | `packages/db/src/schema/*`, then `pnpm db:generate` |
@@ -106,6 +116,7 @@ Turborepo enforces these rules with `pnpm exec turbo boundaries`:
- Import other workspaces by package name and export subpath, such as `@reactive-resume/pdf/browser`. Never reach into another workspace's `src` through a relative path, `@reactive-resume/*/src/*`, or a TypeScript path alias.
- Each workspace's `turbo.json` declares tags. `app:web` and `app:server` mark the apps. `runtime:server` marks server-only packages (API, auth, database, environment, email, MCP), `runtime:browser` marks browser-only UI, and `runtime:universal` marks environment-neutral domain packages.
+- The native app uses `app:mobile`. It shares environment-neutral schemas and domain logic, and imports the API router only as a type; server implementation and browser-only UI do not belong in the native bundle.
- Runtime-specific code sits behind explicit subpaths such as `@reactive-resume/pdf/browser`, `@reactive-resume/pdf/server`, and `@reactive-resume/env/server`. Keep root exports environment-neutral unless the whole package is server-only.
- Wildcard exports are reserved for leaf libraries with a file-like surface: `@reactive-resume/ui/components/*`, `@reactive-resume/ui/hooks/*`, and the schema model files. Everything else uses explicit exports.
@@ -131,7 +142,7 @@ Keep helpers inside the feature that uses them. Don't reintroduce technical-laye
## PDF rendering
-`packages/pdf` renders every PDF. Templates are React components built from the package's primitives. The code in `src/forme` renders them with a small React reconciler and converts the result into a [Forme](https://www.formepdf.com/) document. The Forme engine, compiled to WebAssembly, lays out and draws the pages. No Chromium, Browserless, or print service is involved.
+`packages/pdf` owns the shared resume templates and their conversion to [Forme](https://www.formepdf.com/) documents. Templates are React components built from the package's primitives; `src/forme` renders them with a small React reconciler. The browser and server use Forme's WebAssembly engine to lay out and draw pages, while the native app uses `packages/forme-native`. No Chromium, Browserless, or print service is involved.
- `@reactive-resume/pdf/browser` creates PDFs in the browser. The editor's download and preview use it.
- `@reactive-resume/pdf/server` creates PDFs on the server, for the public resume download and API exports.
@@ -177,4 +188,4 @@ A letter-only document prints no resume header unless `renderOptions.includeCove
- [Development setup](/contributing/development): run the app locally and learn the everyday commands.
- [Deployment checks](/contributing/deployment-checks): how CI verifies the Vercel build and how to smoke-test an installation.
-- [Contributing translations](/contributing/translations): Crowdin, the glossary, and catalog commands.
+- [Contributing translations](/contributing/translations): the glossary, web and native catalogs, and translation review.
diff --git a/docs/contributing/development.mdx b/docs/contributing/development.mdx
index 681bed655..29c12ce3e 100644
--- a/docs/contributing/development.mdx
+++ b/docs/contributing/development.mdx
@@ -10,7 +10,7 @@ This guide takes you from a fresh clone to a running local copy of Reactive Resu
You need:
- **[Node.js](https://nodejs.org/) 24.** The version is pinned in `.nvmrc` and the root `engines` field, so `nvm use` or `fnm use` picks it up.
-- **[pnpm](https://pnpm.io/installation) 12.** The root `packageManager` field pins the exact version (currently `[email protected]`), and pnpm switches to it automatically when you run it inside the repository.
+- **[pnpm](https://pnpm.io/installation) 12.** Use the exact version in the root `packageManager` field. pnpm switches to that version automatically when you run it inside the repository.
- **[Docker](https://docs.docker.com/get-docker/) with Docker Compose** for PostgreSQL, Redis, and S3-compatible storage. Start the Docker daemon first.
- **[Git](https://git-scm.com/).**
@@ -234,7 +234,7 @@ const label = t`Download PDF`;
<Trans>Your resume is ready.</Trans>;
```
-Then run `pnpm lingui:extract`. It updates the catalogs in `apps/web/locales/*.po` and regenerates the PDF section-title catalog. You only add English strings; translators handle the rest on Crowdin. See [Contributing translations](/contributing/translations).
+Then run `pnpm lingui:extract`. It updates the web catalogs in `apps/web/locales/*.po` and regenerates the PDF section-title catalog. For native app strings, also run `pnpm --filter mobile lingui:extract`. Fill and review the affected translations in both apps before release; the repository has no automatic Crowdin synchronization workflow. See [Contributing translations](/contributing/translations).
## Code style
diff --git a/docs/contributing/translations.mdx b/docs/contributing/translations.mdx
index 99bb8a020..3d208b568 100644
--- a/docs/contributing/translations.mdx
+++ b/docs/contributing/translations.mdx
@@ -1,16 +1,16 @@
---
title: "Contributing translations"
-description: "Help translate Reactive Resume on Crowdin: read the glossary, keep placeholders intact, request a new language, and update catalogs in a checkout."
+description: "Help translate the web and native apps: follow the glossary, preserve placeholders, review catalogs, and contribute changes in a pull request."
---
-Reactive Resume is available in more than 50 languages, and every translation comes from volunteers. If you speak a language other than English, you can help people build their resume in it. You don't need to write code: translations happen in your browser on Crowdin.
+Reactive Resume is available in more than 50 languages. If you speak a language other than English, you can help people build their resume in it by reviewing interface translations. The web and native apps have separate catalogs, with shared wording reused where the messages match.
## How translations reach the app
-1. Developers write every interface string in English. The strings are collected in one source catalog, `apps/web/locales/en-US.po`.
-2. Translators work on that catalog in the [Reactive Resume project on Crowdin](https://crowdin.com/project/reactive-resume).
-3. After each change to the `main` branch, a GitHub workflow uploads the source catalog, downloads the latest translations, and opens a pull request titled "Sync Translations from Crowdin".
-4. Once that pull request is merged, your translations ship with the next release of the app. There's usually a delay of a few days to a few weeks, depending on the release cycle.
+1. Developers write interface strings in English. Extraction updates the source catalogs at `apps/web/locales/en-US.po` and `apps/mobile/locales/en-US.po`.
+2. Contributors fill and review the target `.po` catalogs. Native extraction also copies matching web translations into empty native entries; existing native translations stay intact.
+3. A pull request carries the reviewed catalogs and any changed PDF translation files. The repository no longer has an automatic Crowdin synchronization workflow: changes on Crowdin need a maintainer to import them before they reach the app.
+4. Merged translations ship with a subsequent release or compatible mobile update. A Crowdin suggestion or a merged catalog change alone does not mean the deployed app has updated.
The same translations also label the default section headings in downloaded PDFs, such as "Experience" and "Education", and the word "Present" in date ranges.
@@ -20,7 +20,9 @@ Most of the interface is made of short, standalone labels like `Board`, `Resume`
The [glossary](https://github.com/reactive-resume/reactive-resume/blob/main/GLOSSARY.md) explains what each recurring term means in Reactive Resume, lists the wrong senses that earlier translations used, and names the terms that stay in English: the product name, technology names such as PDF, DOCX, JSON, API, and MCP, AI provider names, and template names such as Azurill and Pikachu. Read the entry for a term before you translate it.
-## Translate on Crowdin
+## Suggest translations on Crowdin
+
+The [Reactive Resume project on Crowdin](https://crowdin.com/project/reactive-resume) remains linked from the repository. Before working there, coordinate with a maintainer about importing your changes: the former automatic upload/download workflow is no longer present. For a contribution that can be reviewed directly in the repository, use [Updating catalogs in a checkout](#updating-catalogs-in-a-checkout).
<Steps>
<Step title="Create a Crowdin account">
@@ -83,34 +85,54 @@ Translate the text inside each set of braces, keep `#` where the number goes, an
## Request a new language
-First check whether your language is already listed in the [Crowdin project](https://crowdin.com/project/reactive-resume). If it isn't:
+First check the configured locales in `apps/web/lingui.config.ts` and `packages/utils/src/locale.ts`. If your language isn't listed:
1. Open a new issue on [GitHub](https://github.com/reactive-resume/reactive-resume/issues/new/choose).
2. Title it "Add [language name] translation".
3. Include the language name and its locale code, such as `ja-JP` for Japanese.
-Once a maintainer adds the language, you can start translating it on Crowdin.
+Once a maintainer adds the locale configuration and extracts its catalogs, you can contribute translations for both apps. `zu-ZA` is reserved for the generated pseudo-locale used in testing; it is not a Zulu translation catalog.
## Updating catalogs in a checkout
This section is for developers working in the repository.
-After you add or change user-facing strings with Lingui macros, extract them:
+After you add or change user-facing strings with Lingui macros, extract the web catalogs first, then the native catalogs:
+
+```bash
+pnpm --filter web lingui:extract
+pnpm --filter mobile lingui:extract
+```
+
+The web command updates `apps/web/locales/*.po`. The native command updates `apps/mobile/locales/*.po` and seeds empty matching messages from the web catalogs. The root `pnpm lingui:extract` shortcut extracts web strings and regenerates PDF translations; it does not extract native strings.
+
+Fill the empty active translations in the affected target catalogs and review any changed wording. If you update web translations after native extraction, run `pnpm --filter mobile exec node scripts/seed-locales.mjs` again to copy them into matching empty native entries. It does not replace existing native translations, so review those separately when wording needs to change.
+
+Check that both catalogs contain translations before fallback:
+
+```bash
+pnpm --filter web exec lingui check missing --mode catalog
+pnpm --filter mobile exec lingui check missing --mode catalog
+```
+
+A successful compile or an English fallback does not prove that a target catalog is complete. Follow the placeholder and plural rules above when resolving missing messages.
+
+Then regenerate the PDF translations:
```bash
-pnpm lingui:extract
+pnpm pdf:translations
```
-This updates every catalog in `apps/web/locales/*.po` and then runs `pnpm pdf:translations`, which regenerates two files from the catalogs:
+This produces two files from the web catalogs:
- `packages/pdf/src/section-title-catalog.json`: default section titles for PDFs.
- `packages/schema/src/resume/present-labels.json`: the translated word for "Present" in date ranges.
`pnpm check` and `pnpm build` also regenerate them. Commit the generated files together with the catalog changes. Edit the `.po` files, never the JSON; a test in `tooling/locales` fails when the two drift apart.
-Only edit `en-US.po` by extracting it from code. Other catalogs arrive through the Crowdin pull request, so change translations on Crowdin rather than in the repository, or your edit is overwritten by the next sync.
+Update English source catalogs by extracting messages from code, rather than editing the extracted text by hand. Target catalogs can be edited and reviewed in the repository. Include both the web and native catalog changes where the same user-facing wording appears; do not replace unrelated translations.
-To add a new locale, a maintainer adds its code to `locales` in `apps/web/lingui.config.ts`, to `localeSchema` in `packages/utils/src/locale.ts`, and to `localeMap` in `apps/web/src/libs/locale.ts`, then runs `pnpm lingui:extract`.
+To add a new locale, a maintainer adds its code to `locales` in `apps/web/lingui.config.ts`, to `localeSchema` in `packages/utils/src/locale.ts`, and to `localeMap` in `apps/web/src/libs/locale.ts`, then extracts both apps. The native configuration reads its locale list from `localeSchema`.
## Related pages
diff --git a/docs/docs.json b/docs/docs.json
index d63c477e7..03384afb0 100644
--- a/docs/docs.json
+++ b/docs/docs.json
@@ -119,6 +119,7 @@
"group": "Design",
"pages": [
"guides/choosing-a-template",
+ "guides/changing-how-entries-look",
"guides/customizing-typography",
"guides/choosing-colors",
"guides/selecting-page-format",
diff --git a/docs/guides/adding-an-application.mdx b/docs/guides/adding-an-application.mdx
index 3b352d8fd..808c0d623 100644
--- a/docs/guides/adding-an-application.mdx
+++ b/docs/guides/adding-an-application.mdx
@@ -1,6 +1,6 @@
---
title: "Adding an application"
-description: "Save a job from its link or posting, then prepare a resume or record what you already submitted."
+description: "Save a job from a link, pasted posting or optional keyword search, then prepare a resume or record what you already submitted."
---
Save a job as soon as you find one you like, or record an application you've already submitted. Paste the job link or posting text, check the role and company, and save it. A saved posting gives [Check](/guides/checking-your-resume), [the assistant](/guides/using-the-assistant) and [your cover letter](/guides/writing-a-cover-letter) context for this job.
@@ -36,13 +36,41 @@ Saving a job and preparing a resume manually work without an AI connection or an
</Step>
</Steps>
-<Frame caption="The Add an application dialog with pasted posting text">
+<Frame caption="The Save a job dialog with pasted posting text, ready to save or prepare a resume">
<img
src="/images/guides/adding-an-application/add-an-application-dialog.webp"
- alt="Add an application dialog with posting text pasted, a hint to fill in the role and company, Role set to Level Designer, Company set to Brightline Studios, the Stage control on Applied, and the Add and Add and tailor a resume buttons"
+ alt="Save a job dialog with posting text, Role and Company fields, stage choices, Location, Salary, a resume selector, and Save job and Save and prepare resume buttons"
/>
</Frame>
+## Find a posting with keyword search
+
+If search is available on your installation, the **Save a job** dialog also shows **Search job postings**. Search needs a configured **Web access** connection or server-provided search; an AI provider alone does not enable it. Check **Settings → AI & developer → Web access**, or ask your administrator if the server provides search. You can always paste a link or posting instead.
+
+<Steps>
+ <Step title="Search for a role">
+ Enter a role, company or location under **Search job postings**, then select **Search**. Search runs only when you
+ select the button or press Enter in that field.
+ </Step>
+ <Step title="Choose a posting">
+ Review the result title and description. **View posting** opens the source page in a new tab. Select **Use posting**
+ to put its address into **Job link or posting text**. This clears any role, company, location and salary already in
+ the dialog; it does not read or save the posting.
+ </Step>
+ <Step title="Read and review">
+ Select **Read posting**, then review **Saved description** and the role, company, location and salary. Correct
+ missing or inaccurate details. If the page cannot be read, use **Paste description instead**.
+ </Step>
+ <Step title="Save the job">
+ Choose the appropriate stage, then select **Save job**, **Record application** or **Save and prepare resume**, as
+ described above. Search results are not saved as applications until you choose to save.
+ </Step>
+</Steps>
+
+Search sends your search terms to the configured web search service. Reading a link retrieves its public page through the selected web reader or the built-in reader. If you have a usable default AI provider, **Read posting** also sends the posting text to it to suggest job details. Saving a job never submits an application or contacts the employer.
+
+If search fails or finds nothing useful, change your keywords or paste a posting link directly. For searches that run on a schedule, see [Finding roles automatically](/guides/finding-roles-automatically).
+
## What gets read from a posting
What **Read posting** can fill depends on what you paste and whether you already have a usable [AI connection](/guides/using-ai):
diff --git a/docs/guides/changing-appearance-and-language.mdx b/docs/guides/changing-appearance-and-language.mdx
index 77c890a49..47787e288 100644
--- a/docs/guides/changing-appearance-and-language.mdx
+++ b/docs/guides/changing-appearance-and-language.mdx
@@ -67,6 +67,10 @@ The interface language doesn't translate your resume. Each resume has its own **
Go to **Settings → Preferences** and pick your timezone under **Timezone**. Interview times, reminders and schedules in Career use it. New accounts start on UTC; when your device is set to another timezone, **Use this device's timezone** switches to it in one step. The change is saved at once.
+## Turn off haptic feedback
+
+In the Android and iPhone apps, many taps, such as choosing a design option, give a small vibration. To turn this off, open **Settings → Preferences** and switch off **Haptic feedback** under **Feedback**. The setting applies to this device only. The website has no haptic setting.
+
## Reduce motion
Reactive Resume has no motion switch of its own. It follows your operating system's reduced-motion setting: turn that on, and the app replaces movement with simple fades. Nothing in the app animates on its own without you doing something first.
diff --git a/docs/guides/changing-how-entries-look.mdx b/docs/guides/changing-how-entries-look.mdx
new file mode 100644
index 000000000..7c6e79cec
--- /dev/null
+++ b/docs/guides/changing-how-entries-look.mdx
@@ -0,0 +1,132 @@
+---
+title: "Changing how entries look"
+description: "Choose a header layout for your Experience, Education and Volunteer entries, lead with the position instead of the company, and add an accent line, bar or band."
+---
+
+The **Entries** settings change the header of each entry: the lines with the company or school, the position, the location and the dates. Use them to fit more on a page, to put your job title first, or to make each entry stand out.
+
+These settings apply to the whole resume. They work with every template and stay the same when you switch templates. Your content doesn't change.
+
+## Open the Entries settings
+
+<Steps>
+ <Step title="Open your resume">From **Documents**, open the resume you want to change.</Step>
+ <Step title="Switch to Design">
+ Select **Design** in the editor bar. In the web editor, you can also press <kbd>2</kbd> while you're not typing in a
+ field.
+ </Step>
+ <Step title="Go to Entries">
+ In a computer or tablet browser, select **Entries** in the row of links at the top of the Design panel, or scroll to
+ the **Entries** group below **Template**. On a phone, and in the Android and iPhone apps, tap the **Entries** tab in
+ the design sheet.
+ </Step>
+</Steps>
+
+<Frame caption="The Entries group, with Date column and the Rule accent selected">
+ <img
+ src="/images/guides/changing-how-entries-look/entries-panel.webp"
+ alt="The Entries group in the Design panel, showing Stacked, One line, Compact, Date column and Eyebrow layout tiles, a Row order box with Company above Position and a swap button, and an Accent control with None, Rule, Bar and Band"
+ />
+</Frame>
+
+## Choose a header layout
+
+Under **Header layout**, select one of the five tiles. Each tile sketches the layout, and the page updates straight away.
+
+| Layout | What it does |
+| --------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **Stacked** | Two rows: the company and location, then the position and dates. This is the default. |
+| **One line** | Puts the company, the position and the dates on one line, wrapping onto the next when they don't fit. Education adds a line with the grade and location. |
+| **Compact** | Puts the company and the dates on the first row, then the position and location together on one line. |
+| **Date column** | Sets the dates in a narrow column at the start, with the company, position and location beside them. |
+| **Eyebrow** | Puts the position and location in a small line in the accent color above a larger company name. |
+
+The layouts apply to **Experience**, **Education** and **Volunteer** entries. A few things change what you see:
+
+- **Date column also moves other dates.** With **Date column**, the dates of **Projects**, **Awards**, **Certifications** and **Publications** move into the column too. Those sections keep their usual header with every other layout.
+- **Narrow entries can fall back to Stacked.** **One line** and **Date column** need the full width of the main column. Entries in the sidebar, or in a section split into more than one column, use **Stacked** instead of either of those layouts. **Compact** and **Eyebrow** work everywhere.
+
+To split a section into columns or move it to the sidebar, see [Arranging the layout](/guides/arranging-the-layout).
+
+## Lead with the position
+
+By default, each entry starts with the company or school. To put your job title first instead:
+
+<Steps>
+ <Step title="Find Row order">
+ **Row order** shows the two header rows in their current order, for example "Company · Location" above "Position ·
+ Date".
+ </Step>
+ <Step title="Select the swap button">
+ Select the swap button (⇅), labelled **Swap rows: lead with position**. Every Experience entry now starts with the
+ position, in every layout.
+ </Step>
+</Steps>
+
+Select the button again (**Swap rows: lead with company**) to put the company back first.
+
+- **Education** swaps the school and the area of study the same way.
+- **Volunteer** entries always start with the organization.
+- An entry with no position or area of study keeps the company or school first.
+
+In the web editor on a computer or tablet, you can also swap the rows from the page. Select an Experience or Education entry, then select **Swap rows** on its **Editing** tag. The tag is hidden on phones, so use **Row order** there.
+
+## Add an accent
+
+Under **Accent**, choose how the accent color marks each entry header:
+
+| Accent | What it does |
+| -------- | ----------------------------------- |
+| **None** | No decoration. This is the default. |
+| **Rule** | A line under the header. |
+| **Bar** | A bar at the start of the header. |
+| **Band** | A light tint behind the header. |
+
+In a colored sidebar, the accent uses the sidebar's text color instead of the accent color. To change the accent color itself, see [Choosing colors](/guides/choosing-colors).
+
+## What Word and OpenDocument files keep
+
+PDF downloads, printing and the editor page all use your **Entries** settings. Word (`.docx`) and OpenDocument (`.odt`) downloads follow **Row order** only. They keep their plain layout, without header layouts or accents. See [Downloading your resume](/guides/exporting-your-resume).
+
+Custom styles still apply on top of these settings. See [Applying custom styles](/applying-custom-styles).
+
+## Go back to the default look
+
+There is no separate reset for **Entries**. To return to **Stacked**, company first and no accent, either change the three settings back by hand, or reset the whole design:
+
+<Steps>
+ <Step title="Open Advanced">
+ On a computer or tablet, open **Advanced** at the bottom of the Design panel. On a phone, and in the apps, it's at
+ the bottom of the **Page** tab.
+ </Step>
+ <Step title="Select Reset design defaults">A message confirms the reset and offers **Undo**.</Step>
+</Steps>
+
+<Warning>
+ **Reset design defaults** resets more than **Entries**. Fonts, text size, line height, colors, level style, sidebar
+ width, margins, spacing and the icon and underline switches go back to their defaults too. Your template, paper size,
+ language, date format, section placement and custom CSS stay as they are. See [Reset the design
+ settings](/guides/choosing-a-template#reset-the-design-settings).
+</Warning>
+
+<Note>
+ If the controls are greyed out, the resume is locked. Open the document name menu at the top left and select **Unlock
+ editing**.
+</Note>
+
+## Related guides
+
+<CardGroup cols={2}>
+ <Card title="Choosing a template" icon="layout-template" href="/guides/choosing-a-template">
+ Pick the overall layout before you fine-tune entries.
+ </Card>
+ <Card title="Choosing colors" icon="palette" href="/guides/choosing-colors">
+ Set the accent color the Eyebrow layout and accents use.
+ </Card>
+ <Card title="Arranging the layout" icon="layout-template" href="/guides/arranging-the-layout">
+ Move sections to the sidebar or split them into columns.
+ </Card>
+ <Card title="Editing entries" icon="list" href="/guides/editing-entries">
+ Fill in the positions, dates and locations the header shows.
+ </Card>
+</CardGroup>
diff --git a/docs/guides/choosing-a-template.mdx b/docs/guides/choosing-a-template.mdx
index db1739e4a..66bd676d6 100644
--- a/docs/guides/choosing-a-template.mdx
+++ b/docs/guides/choosing-a-template.mdx
@@ -239,46 +239,11 @@ In a single-column header, Onyx and Lapras are the templates that put the pictur
## Change how entries look
-The **Entries** group, below **Template**, arranges the header of each entry: the lines with the company or school,
-the position, the location and the dates. These settings work with every template and stay when you switch templates.
-
-### Header layout
-
-| Layout | What it does |
-| --------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **Stacked** | Two rows: the company and location, then the position and dates. This is the default. |
-| **One line** | Puts the company, the position and the dates on one line, wrapping onto the next when they don't fit. Education adds a line with the grade and location. |
-| **Compact** | Puts the company and the dates on the first row, then the position and location together on one line. |
-| **Date column** | Sets the dates in a narrow column at the start, with the company, position and location beside them. |
-| **Eyebrow** | Puts the position and location in a small line in the accent color above a larger company name. |
-
-**One line** and **Date column** need the full width of the main column. In the sidebar, or in a section split into
-more than one column, entries use **Stacked** instead. **Date column** also moves the dates of Projects, Awards,
-Certifications and Publications into the column.
-
-### Row order
-
-**Row order** shows the two header rows, for example "Company · Location" above "Position · Date". Select the swap
-button (⇅) to put the position first in every layout, and select it again to put the company back. Education
-swaps the school and the field of study the same way. Volunteer entries always start with the organization, and an entry
-with nothing to swap keeps the company or school first.
-
-In the web editor, you can also swap the rows from the page: select an Experience or Education entry, then select
-**Swap rows** on its **Editing** tag.
-
-### Accent
-
-**Accent** adds the accent color to each entry header: **None** (the default), **Rule** (a line under it), **Bar** (a bar
-at its start) or **Band** (a light tint behind it). In a colored sidebar, the accent uses the sidebar's text color
-instead.
-
-The **Entries** group works the same way on a phone and in the Android and iPhone apps, where it is a tab in the design
-sheet. DOCX and ODT downloads follow **Row order** but keep their plain layout, without header layouts or accents. Custom
-styles still apply on top of these settings; see [Applying custom styles](/applying-custom-styles).
+The **Entries** group, below **Template**, arranges the header of each Experience, Education and Volunteer entry: its layout, whether the company or the position comes first, and an accent. These settings work with every template and stay when you switch templates. See [Changing how entries look](/guides/changing-how-entries-look).
## Reset the design settings
-If you have changed a lot of design settings and want a clean slate, open **Advanced** at the bottom of the Design panel and select **Reset design defaults**. This resets fonts, text size, line height, colors, level style, the **Entries** settings, sidebar width, margins, spacing and the icon and underline switches. Your template, paper size, language, date format, section placement and custom CSS stay as they are. A message offers **Undo**.
+If you have changed a lot of design settings and want a clean slate, open **Advanced** at the bottom of the Design panel and select **Reset design defaults**. On a phone, and in the Android and iPhone apps, **Advanced** is at the bottom of the design sheet's **Page** tab. This resets fonts, text size, line height, colors, level style, the **Entries** settings, sidebar width, margins, spacing and the icon and underline switches. Your template, paper size, language, date format, section placement and custom CSS stay as they are. A message offers **Undo**.
The reset doesn't depend on the template: every template goes back to the same standard settings (IBM Plex Serif at 10 pt, a red accent, circle levels, stacked entry headers and hidden section icons). Pick a font pairing and accent color again afterwards if you want a different starting point.
@@ -290,6 +255,9 @@ The reset doesn't depend on the template: every template goes back to the same s
## Related guides
<CardGroup cols={2}>
+ <Card title="Changing how entries look" icon="list" href="/guides/changing-how-entries-look">
+ Choose a header layout, lead with the position and add an accent.
+ </Card>
<Card title="Customizing typography" icon="font" href="/guides/customizing-typography">
Pick a font pairing, text size and density.
</Card>
diff --git a/docs/guides/editing-on-mobile.mdx b/docs/guides/editing-on-mobile.mdx
index a502d1c6a..7a981fcfc 100644
--- a/docs/guides/editing-on-mobile.mdx
+++ b/docs/guides/editing-on-mobile.mdx
@@ -63,14 +63,14 @@ When you type in a description or the summary, the formatting toolbar docks just
### Change the design
-The **Design** tab keeps the page visible in the top half of the screen, so you can see each change as you make it. The settings sit in a sheet with five tabs: **Template**, **Entries**, **Type**, **Color** and **Page**. The **Advanced** settings are at the bottom of the **Page** tab.
+The **Design** tab keeps the page visible in the top half of the screen, so you can see each change as you make it. The settings sit in a sheet with five tabs: **Template**, **Entries**, **Type**, **Color** and **Page**. The **Advanced** settings are at the bottom of the **Page** tab. **Entries** sets the layout, row order and accent of entry headers; see [Changing how entries look](/guides/changing-how-entries-look). Because the **Editing** tag is hidden on phones, its **Swap rows** button is too; use **Row order** in the **Entries** tab instead.
To see more of the settings, tap the handle at the top of the sheet (**Raise the design sheet**). Tap it again to lower it.
-<Frame caption="The design sheet over the lower half of the page">
+<Frame caption="The raised phone design sheet: all five tabs, with Entries open">
<img
src="/images/guides/editing-on-mobile/phone-design-sheet.webp"
- alt="The Design view on a phone with the resume page above and a sheet below showing Template, Type, Color and Page tabs and a strip of template thumbnails"
+ alt="The raised phone design sheet showing Template, Entries, Type, Color and Page tabs, with Entries selected and its five header layouts, Row order and Accent controls visible"
style={{ maxWidth: "360px", margin: "0 auto" }}
/>
</Frame>
@@ -113,12 +113,13 @@ The native app uses **Write**, **Page**, **Design**, **Check** and **Share**. It
- **Recover unsynced work.** **Documents** shows **Unsynced on this device** when local edits have not reached the server. Open the document there to continue, including after restarting without a connection. These edits belong to the signed-in account; sign-out warns before removing unsynced work.
- **Share a PDF.** Select **Download** to open **Download & history**, review **File name**, then choose **Share PDF**. **File format** offers other exports. Choose a storage provider in the system share sheet to save the file. **History** keeps saved versions separate.
-- **Publish a web page.** Open the **Share** mode, then **Publish**. The same address, password, contact privacy, primary resume and custom-domain controls are available as on the website. **Preview web page** opens the page in the app's browser. Public resume links also open in a browser. Sharing needs a connection; local PDF exports can work offline when their fonts and images are cached. See [Sharing your resume as a web page](/guides/sharing-your-resume-publicly).
+- **Publish a web page.** Open the **Share** mode, then turn on **Public link**. The website uses a **Publish** button instead; both make the same page public. The same address, password, contact privacy, primary resume and custom-domain controls are available as on the website. **Preview web page** opens the page in the app's browser. Public resume links also open in a browser. Sharing needs a connection; local PDF exports can work offline when their fonts and images are cached. See [Sharing your resume as a web page](/guides/sharing-your-resume-publicly).
- **Save a job quickly.** Enter **Company**, **Role / title** and **Stage**, then select **Save job**. Open **More details** for optional fields. Application and follow-up dates use the native date picker; **Clear date** removes an optional follow-up date.
- **Keep unfinished forms.** Dismissing an edited job or interview form asks whether to **Discard** or **Keep editing**. Save and Cancel remain at the bottom. While a save runs, wait for its result before leaving.
- **Choose the next task.** Application details offer a task such as **Prepare application**, **Prepare for interview**, or **Draft a follow-up**. Stage progress is informational; select **Change stage** to edit it.
- **Switch Knowledge views.** **Facts**, **Stories** and **Preferences** appear together. Workspace tabs reveal the selected destination and provide arrows when the full strip does not fit.
- **Refresh saved information.** Pull down in Documents, Applications (including Board, Calendar and Insights), Career or account settings. In Board, pull inside a stage column. Check also supports pulling down to rerun its local checks.
+- **Turn off haptics.** Open **Settings → Preferences**, then switch off **Haptic feedback** under **Feedback**. The setting applies to this device only.
- **Choose any timezone.** Open **Settings → Preferences → Timezone**, then search by region or city. **Show more** reveals another batch of timezones. Interview forms offer the same searchable list and can keep a separate timezone for an interview.
- **Return from document options.** Rename, duplicate, notes and details offer **Back** to return to the document menu. Swipe the sheet down to dismiss it.
diff --git a/docs/guides/editor-overview.mdx b/docs/guides/editor-overview.mdx
index dbbc3e7d7..e93d9fac9 100644
--- a/docs/guides/editor-overview.mdx
+++ b/docs/guides/editor-overview.mdx
@@ -56,7 +56,7 @@ Select the document name to open the document menu.
The mode switcher in the middle of the bar changes what the panel shows. The page stays in view in every mode.
- **Write** is for content: your name and contact details, the summary, and every section and entry. See [Filling in your details](/guides/filling-in-your-details) and [Managing sections](/guides/managing-sections).
-- **Design** is for the look of the page: template, fonts, colors, page format and layout. See [Choosing a template](/guides/choosing-a-template).
+- **Design** is for the look of the page: template, entry headers, fonts, colors, page format and layout. See [Choosing a template](/guides/choosing-a-template) and [Changing how entries look](/guides/changing-how-entries-look).
- **Check** reviews the resume for problems, and can compare it with a job posting. See [Checking your resume](/guides/checking-your-resume).
- **Share** publishes the resume as a web page and sets its address and privacy. The page area previews the web page instead of the PDF. See [Sharing your resume as a web page](/guides/sharing-your-resume-publicly).
@@ -66,7 +66,7 @@ When you're not typing in a field, press <kbd>1</kbd>, <kbd>2</kbd>, <kbd>3</kbd
The page on the right is a live preview of the PDF you'll download. Each page has a label above it, such as **Page 1**.
-- **Click a line on the page to edit it.** Hovering over the page tints the block under the pointer. Clicking it selects that entry, marks it with an **Editing** tag, and opens it in the Write panel. Clicking your name or contact details opens the Basics card. Press <kbd>Esc</kbd> to clear the selection.
+- **Click a line on the page to edit it.** Hovering over the page tints the block under the pointer. Clicking it selects that entry, marks it with an **Editing** tag, and opens it in the Write panel. On an Experience or Education entry, the tag also offers **Swap rows**, which puts the position or the company first in every entry. Clicking your name or contact details opens the Basics card. Press <kbd>Esc</kbd> to clear the selection.
- **Proposed edits** from the assistant or from Check appear on the page, with old text struck through and new text highlighted. Nothing changes until you accept them.
- **Overflow warning.** If your content runs onto an extra page, the label above the first page says so, for example "Runs onto page 2 by about 6 lines", and offers **Fit to one page**. See [Fitting content on a page](/guides/fitting-content-on-a-page).
diff --git a/docs/guides/exporting-your-resume.mdx b/docs/guides/exporting-your-resume.mdx
index 30f17342f..69eefd680 100644
--- a/docs/guides/exporting-your-resume.mdx
+++ b/docs/guides/exporting-your-resume.mdx
@@ -64,8 +64,8 @@ A few things you may see on this tab:
## What each file contains
- **PDF** keeps your template, fonts, colors, layout and page breaks. Hidden sections and entries are left out.
-- **Word** keeps your content, headings and lists in an editable document. Visual details such as columns, colors and icons are simplified, your photo isn't included, and hidden content is left out.
-- **OpenDocument** is the same editable, simplified document as Word, saved as the open `.odt` standard for LibreOffice, OpenOffice and other open-source editors. Your photo isn't included.
+- **Word** keeps your content, headings and lists in an editable document. Visual details such as columns, colors and icons are simplified, your photo isn't included, and hidden content is left out. Entries follow your **Row order** setting, but not the header layouts or accents; see [Changing how entries look](/guides/changing-how-entries-look).
+- **OpenDocument** keeps your content in an editable, simplified document saved as the open `.odt` standard for LibreOffice, OpenOffice and other open-source editors. It follows **Row order** without the entry header layouts or accents. Your photo isn't included.
- **Markdown** keeps headings, lists, links, bold and italic text. It leaves out hidden content and all visual design.
- **JSON** keeps everything: every section and entry, hidden ones included, your design settings and your private notes. To restore it, select **New**, then **Import a resume**, and choose the file. Importing creates a new resume; it doesn't overwrite one.
diff --git a/docs/guides/importing-applications-from-csv.mdx b/docs/guides/importing-applications-from-csv.mdx
index a455fee1d..fd7052a0d 100644
--- a/docs/guides/importing-applications-from-csv.mdx
+++ b/docs/guides/importing-applications-from-csv.mdx
@@ -96,8 +96,9 @@ Up to 500 applications import at a time. If your file has more, the summary says
<Steps>
<Step title="Open Export to CSV">Select the import/export button, then **Export to CSV…**.</Step>
<Step title="Choose what to export">
- Under **Applications to export**, choose **Current filters** (the applications matching your current search, closed
- ones included) or **All applications (including closed)**.
+ Under **Applications to export**, choose **Current filters** to export applications matching your search and **Show
+ closed** setting. Closed applications are included only when **Show closed** is on. Choose **All applications
+ (including closed)** to include every application regardless of those settings.
</Step>
<Step title="Limit by date, if you like">
Set **Application date from** and **Application date to** to export only applications from that period. Leave them
@@ -113,7 +114,9 @@ Up to 500 applications import at a time. If your file has more, the summary says
/>
</Frame>
-The file is named `applications-YYYY-MM-DD.csv` and opens in any spreadsheet app. It has these columns: Company, Role, Stage, Lane, Lane Category, Lane Closed Reason, Stage Date, Application Date, Location, Salary, Source, URL, Tags, Contacts, Notes, Closed Reason, Stage History, Timeline, Created At and Updated At.
+The file is named `applications-YYYY-MM-DD.csv` and opens in any spreadsheet app. It has these columns: Company, Role, Stage, Lane, Lane Category, Lane Closed Reason, Stage Date, Application Date, Location, Salary, Source, URL, Job Description, Posting Source, Tags, Contacts, Notes, Closed Reason, Stage History, Timeline, Created At and Updated At.
+
+**Job Description** contains the saved posting text. **Posting Source** contains its source metadata as JSON, such as how and when it was retrieved and whether it was clipped, when available. The export also includes your contacts, notes and timeline, so treat the downloaded file as private application data and check it before sharing.
**Stage** is always one of the standard stages, so other spreadsheets and older versions can read it. **Lane** is the name of your own stage, **Lane Category** what it counts as, and **Lane Closed Reason** its preset outcome, if any.
diff --git a/docs/guides/managing-applications-with-mcp.mdx b/docs/guides/managing-applications-with-mcp.mdx
index aa865cf63..7b8354cb4 100644
--- a/docs/guides/managing-applications-with-mcp.mdx
+++ b/docs/guides/managing-applications-with-mcp.mdx
@@ -109,12 +109,9 @@ Attach this PDF as the resume I sent to Northwind Games.
Remove the cover-letter PDF from the Blue Harbor Studio application.
```
-`attach_application_document` accepts one resume PDF and one cover-letter PDF per application, up to 10 MB each, sent as base64. Attaching a new file replaces the old one.
+`attach_application_document` accepts one resume PDF and one cover-letter PDF per application, up to 10 MiB each. Inline `dataBase64` is limited to 3 MiB of encoded text (about 2.25 MiB of file bytes). For a larger PDF, upload it under your account first and supply its owned `storagePath` instead. Supply exactly one of `dataBase64` or `storagePath`; external URLs and other users' files cannot be used. See [File limits and references](/guides/using-the-mcp-server#file-limits-and-references).
-<Warning>
- Anyone with the address of an attached PDF can download it without signing in. Attaching a file never sends it to an
- employer.
-</Warning>
+Attaching a new file replaces the old one. Downloading an attached PDF requires authentication as its owner with read permission; other requests receive a 404 response. Attaching a file never sends it to an employer.
If your client can't read files from your computer, attach the PDF in the app instead. See [Managing an application](/guides/managing-an-application).
@@ -169,13 +166,14 @@ Use Reactive Resume MCP for job applications. Call list_applications before crea
## Troubleshooting
-| Problem | What to do |
-| -------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| The client can't see application tools | Reconnect the server and ask the client to refresh its tools. |
-| The client creates duplicates | Ask it to list applications first and match on company and role before creating one. |
-| A stage change to `rejected` or an archive request fails | Those no longer exist. Use the `closed` stage with a reason. |
-| Attaching a document fails | Only PDFs up to 10 MB are accepted. Attach from the app if your client can't read the file. |
-| Scoring, tailoring or drafting fails | Check that a default AI provider is set up and tested. For scoring and tailoring, also check that the application has a job description and a linked resume. |
+| Problem | What to do |
+| -------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| The client can't see application tools | Reconnect the server and ask the client to refresh its tools. |
+| The client creates duplicates | Ask it to list applications first and match on company and role before creating one. |
+| A stage change to `rejected` or an archive request fails | Those no longer exist. Use the `closed` stage with a reason. |
+| Attaching a document fails | Use a PDF up to 10 MiB. Inline base64 allows 3 MiB encoded (about 2.25 MiB of file bytes); use an owned `storagePath` for larger PDFs. Attach from the app if your client can't read the file. |
+| An attached PDF returns 404 | Authenticate as the file's owner with read permission. The address alone does not grant access to a signed-out browser or another account. |
+| Scoring, tailoring or drafting fails | Check that a default AI provider is set up and tested. For scoring and tailoring, also check that the application has a job description and a linked resume. |
## Related guides
diff --git a/docs/guides/scheduling-interviews.mdx b/docs/guides/scheduling-interviews.mdx
index c01234812..78947963e 100644
--- a/docs/guides/scheduling-interviews.mdx
+++ b/docs/guides/scheduling-interviews.mdx
@@ -31,10 +31,10 @@ You can start from the application or from the calendar.
In **Applications**, select the **Calendar** tab.
</Step>
<Step title="Start scheduling">
- Select **Schedule interview**, or hover over a day and select **+** to start on that day.
+ Select **Schedule interview**. In the web app, you can also hover over a day and select **+** to start on that day.
</Step>
<Step title="Choose the application">
- Under **Application**, pick the application the interview belongs to. Closed applications aren't listed.
+ Under **Application**, pick the application the interview belongs to. Closed applications aren't listed. In the native mobile app, select **Continue** to open the interview form.
</Step>
</Steps>
</Tab>
@@ -86,7 +86,7 @@ Open the application's workspace and choose **Prepare** for a timed plan, briefi
## Use the Calendar view
-The **Calendar** tab shows one month of interviews across all your applications.
+In the web app, the **Calendar** tab shows one month of interviews across your applications.
- Use the arrows to change month, and **This month** to come back to today.
- Each day shows up to three interviews, with the time and company. Select **+_n_ more** to see the rest of a busy day.
@@ -100,7 +100,18 @@ The **Calendar** tab shows one month of interviews across all your applications.
/>
</Frame>
-The calendar follows the page's search and **Show closed** settings, so interviews for closed applications are hidden unless **Show closed** is on. The Calendar view isn't available on phones; use each application's **Next step** instead.
+The web calendar follows the page's search and **Show closed** settings, so interviews for closed applications are hidden unless **Show closed** is on. In a narrow phone browser, the web app hides the Calendar tab; use each application's **Next step** instead.
+
+### In the native mobile app
+
+Open **Applications** and choose **Calendar** in the view selector below the heading. Calendar is available on phones and tablets, alongside **List**, **Board** and **Insights**.
+
+- Use the arrows to change month, or **This month** to return to today.
+- Select a day to see its interviews and follow-ups. On phones, dots mark days with events and the day's agenda appears below the month. On a wide tablet layout, the agenda appears beside it.
+- Select an interview or follow-up card to edit it, or **View application** to open its application details. **Coming up** lists upcoming events by day.
+- Select **Schedule interview**, choose an application and select **Continue** to open the interview form.
+
+The native calendar follows your application search and shows only open applications. It uses your account timezone to place events on their days.
## Set a follow-up reminder
diff --git a/docs/guides/sharing-your-resume-publicly.mdx b/docs/guides/sharing-your-resume-publicly.mdx
index 1b7dd3322..22bace044 100644
--- a/docs/guides/sharing-your-resume-publicly.mdx
+++ b/docs/guides/sharing-your-resume-publicly.mdx
@@ -29,6 +29,11 @@ The **Share** mode publishes your resume as a web page that anyone you send the
**Open web page** opens it in a new tab, and **QR code** shows a code that opens the link, handy for a printed card or a slide. In the mobile app, **Preview web page** opens the page in the app's browser, even before you publish it.
+<Note>
+ In the Android and iPhone apps, there is no **Publish** button. Open **Share** and turn on the **Public link** switch
+ instead. The address, **Copy**, **Share via…**, **Open web page** and **QR code** work the same way.
+</Note>
+
## What visitors see
- **On a computer**, the resume sits on the page like a sheet of paper, in your template.
@@ -127,7 +132,7 @@ signed-in session. The numbers aren't a list of readers or proof that a recruite
## Stop sharing
-Turn off **Public link** in Share. The page stops working immediately, and visitors see **This resume isn't shared right now.** Your address is kept, so publishing again brings the same address back. Moving the resume to Trash also stops its page.
+Turn off **Public link** in Share, on the website or in the apps. The page stops working immediately, and visitors see **This resume isn't shared right now.** Your address is kept, so publishing again brings the same address back. Moving the resume to Trash also stops its page.
<Note>
While a resume is locked, you can't change its Share settings. Select the resume's name in the editor bar, then
diff --git a/docs/guides/tracking-job-applications.mdx b/docs/guides/tracking-job-applications.mdx
index a63752bd9..b894be176 100644
--- a/docs/guides/tracking-job-applications.mdx
+++ b/docs/guides/tracking-job-applications.mdx
@@ -41,7 +41,7 @@ You can close an application from any stage. Closing asks for a reason (**Not se
## Choosing a view
-Use the tabs above the list to switch views. Your choice is kept in the page address, so a bookmark opens the same view.
+In the web app, use the tabs above the list to switch views. Your choice is kept in the page address, so a bookmark opens the same view. In the native mobile app, open **Applications** and use the view selector below the heading: **List**, **Board**, **Calendar** or **Insights**. All four views are available on phones and tablets.
<Tabs>
<Tab title="List">
@@ -70,17 +70,17 @@ Use the tabs above the list to switch views. Your choice is kept in the page add
Charts about how your applications are going: how far they get, how often and how quickly people reply, and where your applications come from. See [Viewing application insights](/guides/viewing-application-insights).
</Tab>
<Tab title="Calendar">
- A month calendar of your interviews, with a list of upcoming ones beside it. See [Scheduling interviews](/guides/scheduling-interviews).
+ A month calendar of your interviews, with a list of upcoming ones beside it in the web app. The native mobile app also shows follow-ups, with the selected day and **Coming up** below the month on phones. See [Scheduling interviews](/guides/scheduling-interviews).
</Tab>
</Tabs>
-On phones, the page shows **List** and **Insights** only, and list rows show the company and next step on a second line.
+In a narrow phone browser, the web page shows **List** and **Insights** only, and list rows show the company and next step on a second line. This browser layout restriction does not apply to the native mobile app.
## Finding applications
Type in **Search applications** to filter the list as you type. Search looks at the role, company, location, contact names and tags. If nothing matches, select **Clear search**.
-**Show closed** adds closed applications to the List, Board and Calendar views. Insights always counts every application.
+In the web app, **Show closed** adds closed applications to the List, Board and Calendar views. The native mobile calendar shows only open applications. Insights always counts every application.
## Acting on several applications at once
diff --git a/docs/images/guides/adding-an-application/add-an-application-dialog.webp b/docs/images/guides/adding-an-application/add-an-application-dialog.webp
index 88e4c9bbf..b5b8a7d33 100644
Binary files a/docs/images/guides/adding-an-application/add-an-application-dialog.webp and b/docs/images/guides/adding-an-application/add-an-application-dialog.webp differ
diff --git a/docs/images/guides/changing-how-entries-look/entries-panel.webp b/docs/images/guides/changing-how-entries-look/entries-panel.webp
new file mode 100644
index 000000000..4c0b39a00
Binary files /dev/null and b/docs/images/guides/changing-how-entries-look/entries-panel.webp differ
diff --git a/docs/images/guides/editing-on-mobile/phone-design-sheet.webp b/docs/images/guides/editing-on-mobile/phone-design-sheet.webp
index a552e41eb..9eaf1fb77 100644
Binary files a/docs/images/guides/editing-on-mobile/phone-design-sheet.webp and b/docs/images/guides/editing-on-mobile/phone-design-sheet.webp differ
diff --git a/docs/self-hosting/cloudflare.mdx b/docs/self-hosting/cloudflare.mdx
index 5d036f599..d3bc694c0 100644
--- a/docs/self-hosting/cloudflare.mdx
+++ b/docs/self-hosting/cloudflare.mdx
@@ -34,7 +34,7 @@ Durable Object requests, active duration, and SQLite storage have their own incl
## Before you start
-You need a Cloudflare account with Workers Paid and R2 enabled, Node.js 24, pnpm 12.11.2, and a PostgreSQL database reachable by Hyperdrive. Keep PostgreSQL TLS enabled. Run the commands below from the repository root.
+You need a Cloudflare account with Workers Paid and R2 enabled, Node.js 24, the pnpm version pinned in the root `packageManager` field, and a PostgreSQL database reachable by Hyperdrive. Keep PostgreSQL TLS enabled. Run the commands below from the repository root.
```bash
pnpm install --frozen-lockfile
diff --git a/docs/self-hosting/environment-variables.mdx b/docs/self-hosting/environment-variables.mdx
index fff146ded..bc53db60c 100644
--- a/docs/self-hosting/environment-variables.mdx
+++ b/docs/self-hosting/environment-variables.mdx
@@ -233,6 +233,14 @@ pair`. Passwordless (`nopass`) ACL users keep an explicitly empty password: `red
Saved AI providers and Assistant conversations are kept in PostgreSQL, so they remain available without Redis.
+## Career scheduling
+
+| Variable | Default | Description |
+| ------------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `CRON_SECRET` | unset | Authenticates `GET` and `POST /api/career/run` with `Authorization: Bearer <secret>`. At least 16 characters; generate it with `openssl rand -hex 32`. Required for Vercel Cron or an external HTTP scheduler. Node.js/Docker and Cloudflare schedule internally without this token. |
+
+Without `CRON_SECRET`, the HTTP runner returns `404`; an invalid bearer token returns `401`. On Vercel, set the secret in the Production environment and redeploy so Vercel Cron can supply it. Users must still opt in to each schedule. See [Career scheduling](/contributing/career-platform#operate-scheduled-work) for deployment timing and verification, and [Self-hosting on Vercel](/self-hosting/vercel#scheduled-career-work) for its setup.
+
## Web access
The built-in reader is active without credentials. Search and enhanced reading use one optional connection: