Starter Templates – Website Templates & Demo Import for Block Editor

Install any required premium plugins from your PressMaximum account before importing. The importer cannot download those plugins from WordPress.org. If a dependency is unavailable, the import can continue with a warning; features may be missing, and content for an unavailable plugin can be skipped.

Use a new or staging site for your first import. Importing can replace settings and menu items, and re-importing can replace previously imported content. Back up an existing site before proceeding.

Free starter templates and premium designs

The plugin is free. Templates marked Free do not require a premium template license. Check each template’s plugin requirements as well: a template’s license and the licenses for its required plugins are separate.

A Press Studio license key is required to import premium templates. A standalone Customify Pro or Blocksify Pro license does not include premium template access. Use the license filter to browse Free or Press Studio templates.

You can still view a premium demo without access to import it. When a package is required, the setup sidebar names that package and links to PressMaximum pricing . A configured license is checked when you open a premium preview and again when you start an import.

Customify compatibility

These starter sites are intended for the Customify theme . The plugin integrates with its Starter Templates dashboard and applies Customify’s settings, palettes and typography. Activate Customify, or a child theme based on Customify, to use this integration.

Each design may require additional plugins for its blocks, shop or other content. Keep those plugins active after importing so the features used by your site remain available.

External services

PressMaximum / PM Templates

The plugin uses the public PM Templates catalog at https://pressmaximum.com/wp-json/pm-templates/v1/public/ to list templates, retrieve details and download their files. Public catalog browsing does not require an account or API key.

Requests happen at these points:

• Library loading: your WordPress server requests the template list and category filters. Search, category selection and license filtering in the current library run in your browser on the downloaded list; typing in the search field does not send each search to PressMaximum. Requests may be served from the site’s cache.
• Preview setup: your server requests the selected template’s details and may download its options.json file to load style choices. These requests identify the template or asset being requested.
• Live preview: your browser loads the public demo URL supplied by the catalog in an iframe, including a timestamp query parameter used to refresh the preview. The demo receives your browser’s normal request information, such as IP address and user agent, and may receive a referrer subject to browser policy. Palette and typography selections are sent to the embedded demo as CSS so compatible demos can display them.
• Import: your server retrieves template details and downloads content data in JSON format, options.json, and uploads.zip when supplied. The archive contains the template’s media files. These are inbound downloads; the importer does not upload your site’s content to the catalog.
• Premium access: when a premium preview opens, when you retry a license check, or when you start a premium import, your server may send configured license keys, read from the Customify Pro or Blocksify Pro settings, to the PressMaximum license service. Each check includes the license key, product ID, site home URL and the check_license action. No license request is sent if there is no configured key to check.

Server requests expose the server’s IP address. WordPress’s default HTTP user agent includes the WordPress version and site URL. If an advanced configuration supplies a Studio API key, the remote client sends it in the X-PMBD-Api-Key header with catalog requests and import asset downloads. This optional key is separate from premium license verification.

PressMaximum provides the catalog and license service. See its Terms and Conditions and Privacy Policy . The CUSTOMIFY_STARTER_SITES_STUDIO_URL constant can override the catalog host; license-service configuration is separate.

WordPress.org and Google Fonts

During import, WordPress requests plugin information and downloads selected free plugin packages from WordPress.org. These requests identify the plugins being installed and include normal HTTP request information. See the WordPress.org Privacy Policy .

When the style panel opens, your browser requests font CSS from fonts.googleapis.com for the displayed font pairs, plus their font files, to render the typography samples. Applying a font pair in the live preview can trigger the same requests from the embedded demo. These requests identify font families and variants and include the browser’s normal HTTP information.

During font installation, your server may fetch WordPress’s Google Fonts collection from s.w.org, request font CSS from fonts.googleapis.com as a fallback, and download the font files referenced by the collection or CSS, typically from fonts.gstatic.com. Requests identify the collection or requested font resources and include normal HTTP information. Successfully installed fonts are stored locally through the WordPress Font Library. See Google’s Terms of Service and Privacy Policy .

Development

Source code and build tools are available on GitHub .