Editing and layout

The document structure

Experiencer renders a semantic tree rather than a blank canvas. The standard hierarchy uses sections, rows, columns, grids, and entries. Select a node in the résumé or structure sidebar before using an add, move, duplicate, or delete command.

• A section groups a major résumé area.
• A row arranges related content horizontally within the available width.
• A column divides a row into vertical regions.
• A grid repeats structured cells using a defined column layout.
• An entry holds a piece of résumé content.
• A page break begins the following content on a new printed page.

Some commands are only valid for particular parents or selections. If an action is unavailable, select the containing node and confirm that the requested child type belongs there.

Edit values safely

Select visible text to edit it. Markdown may be supported for text emphasis and links in fields designed for rich text. Keep critical contact and employment text as actual text rather than images so it remains selectable and extractable.

Use Undo and Redo for recent editor changes. Save a portable JSON copy before a large structural or CSS rewrite.

Themes, fonts, and CSS

The Theme menu changes the editor interface. Template typography and spacing come from the document’s built-in CSS plus any document-authored CSS shown in the CSS sidebar.

Built-in fonts travel with the supported application export path. Optional remote fonts can require a network request when a résumé is viewed. Verify a final PDF after changing fonts, because metrics can affect wrapping and pagination.

Prefer normal document flow for résumé content. Positioning content out of flow can make the visual result disagree with text extraction order.

Page size and page breaks

Choose Letter or A4 before final layout work. A page-size change alters usable width and height, which can move headings or entries across page boundaries.

Insert explicit page breaks only where a new page is intentional. Avoid using repeated blank rows or large margins as a page-break substitute. After every pagination change, use File → Print and the ATS readability check.

Visual editor constraints

Experiencer shows browser-rendered HTML and CSS. A printer or PDF destination can apply its own margins, headers, footers, scale, and background settings. The editor cannot guarantee identical output from every browser and printer driver.

Keep the content hierarchy logical, avoid very long unbroken URLs, and verify narrow columns for overflow. The résumé preview is the source of truth for layout; the structure sidebar is the source of truth for reading order.

Next: Export or print the result.