Customize Greenhouse job pages

Block themes: edit job pages in the Site Editor

On WordPress 6.7 or newer with a block theme, the plugin adds block templates for its pages. Find them under Appearance → Editor → Templates:

Each taxonomy with an archive slug gets its own archive template. Edit a template like any other: add, move or remove blocks, or change their settings.

Your version always wins. A template you save in the Site Editor is used instead of the plugin’s, and so is one your theme ships in its templates folder under the same name, such as single-ghjb_job.html, archive-ghjb_job.html or taxonomy-ghjb_location.html.

When you build your own archive template, the Jobs archive pattern in the Greenhouse Jobs category inserts the breadcrumbs, title, filters and list in one go.

The plugin’s blocks in these templates render with the PHP templates below, so overriding one of those changes the block too.

Override a PHP template

1. Create a greenhousewp folder in your theme, ideally a child theme: wp-content/themes/your-theme/greenhousewp/.
2. Copy the template you want from wp-content/plugins/greenhousewp/templates/ into that folder, keeping the file name.
3. Edit your copy.

The plugin looks in your theme first and falls back to its own copy, so updates leave your copies alone. The comment at the top of each template lists the variables it receives.

After a plugin update, compare your copies with the new originals. A template may gain a variable or a fix worth carrying over.

The 13 templates

Take over the whole page on classic themes

page-jobs.php and page-single-job.php build the whole page, including your theme’s header and footer, on classic themes. A block theme on WordPress older than 6.7 uses them too, with the theme’s header and footer template parts. With the block templates above, they are not used.

To replace the whole page, either:

• override greenhousewp/page-jobs.php or greenhousewp/page-single-job.php as above, or
• add a standard WordPress template for the ghjb_job post type to your theme: archive-ghjb_job.php for the list, single-ghjb_job.php for a job, taxonomy-ghjb_department.php and the like for job archives. The plugin uses them when your theme has them.

Restyle with CSS classes and custom properties

Every element has a class starting with ghjb-. Job lists, filter forms, single jobs and the apply area sit inside a .ghjb-root wrapper. The main classes:

Colours, spacing and corners are CSS custom properties on .ghjb-root. Override them in one rule in your theme’s stylesheet or in Appearance → Customize → Additional CSS. For example:

.ghjb-root {
	--ghjb-accent: #0a5cff;          /* buttons and links */
	--ghjb-accent-contrast: #ffffff; /* text on the accent colour */
	--ghjb-border: #e2e2e2;
	--ghjb-muted: #6b6b6b;           /* secondary text */
	--ghjb-surface: transparent;     /* card background */
	--ghjb-radius: 4px;
	--ghjb-gap: 1rem;
	--ghjb-gap-lg: 2rem;
}

By default the accent follows your block theme’s contrast colour and the text on it follows its base colour. Borders and secondary text are your theme’s text colour, faded, so they suit light and dark themes without any CSS.

Developer hooks

Jobs with a pay range in Greenhouse get baseSalary in their JobPosting markup automatically, from the first range. Greenhouse sends no pay period, so the plugin reads it from the range’s title or description (“hourly”, “per month”, “Annual Base Salary”). A range that names none is taken as a year only when its lowest amount is at least 15,000 in USD, CAD, AUD, NZD, GBP or EUR; otherwise the job gets no baseSalary.

Example: every pay range you publish is monthly, but the ranges don’t say so.

add_filter( 'ghjb_pay_range_unit', function ( $unit, $range ) {
	return '' === $unit ? 'MONTH' : $unit;
}, 10, 2 );

The period then shows on the job page too, as in “4,000 – 5,500 EUR per month”. Turning off Pay ranges under Greenhouse → Settings → Display removes the row and baseSalary together.

A job’s description is Greenhouse’s HTML, filtered with the rules WordPress applies to post content (wp_kses_post) on import and again when it is printed. HTML comments are removed, and the title is stored as plain text. A shortcode typed into a Greenhouse description is shown as text, never run, wherever the job’s content is printed: the block template, a theme template or the jobs feed.

Hooks for the application form are listed in Greenhouse application form.