Overview

Theme Paperdesk

What this theme gives you

A tactile craft-studio presentation built around a browsable desk, physical paper objects, and direct commission paths.

How to use it

Open the theme-management entry for Theme Paperdesk, note the site’s current theme, and select only the site you intend to review.
Choose Preview Theme Paperdesk to view this theme privately on that site’s existing content without changing its selected theme. Check available page areas, sections and the mobile layout; create a page first if there is nothing to preview.
When ready, choose Apply Theme Paperdesk for that site. This changes its public design immediately, including already-published pages.
Pick a preset in Theme Studio and adjust the shared visual controls.
Add Paperdesk widgets in Layout Builder and supply portable copy, links, and media.
Preview desktop and mobile before publishing.

To recover the previous design, reopen the previous theme’s management entry, select the same site and choose its Apply button. This restores the theme selection; it does not undo content or shared Theme Studio settings. Saving those settings can affect public pages using that theme, so do not treat settings edits as private preview changes.

What it adds

A desk scatter and its accessible list equivalent.
Three presets and three section variants.
Craft-focused hero, materials, process, proof, event, gallery, CTA, and recovery sections.

Good to know

Install Foundation Theme and Layout Builder first.
Optional packages improve specific sections, but every path has a safe fallback.
The desk interaction is decorative; visitors can always use ordinary links and lists.

Try fictional demo content safely

Use private theme Preview for existing content. Ask a developer to follow safe demo setup in a disposable local site when you want fictional sample pages instead.

A scoped demo run writes sample pages, widgets and demo layouts, including on repeats, and can adopt the site recovery page. An unscoped run refuses existing sites; a scoped run preserves site configuration unless the developer deliberately chooses the documented overwrite option. Review the target, languages and domains together before setup.

For developers: see the README.