The problem
Contact details and designer credits were hard-coded across templates. A business change could mean several code edits and another deployment.
WordPress plugin · Active project
Configuration123
One place for your site’s identity.
Keep business details, contact information, and designer credits editable in WordPress—and independent of your theme.
- Platform
- WordPress · PHP
- Focus
- Reusable site identity
- Interface languages
- English & French
01 / Overview
Update the information.
Keep the theme out of it.
The approach
Move those details into a shared WordPress settings screen. Administrators manage the values and choose which fields can appear publicly.
The benefit
Site information stays editable when the theme changes. The same plugin can serve different client sites, each with its own saved data.
02 / Workflow
Configure once.
Choose what appears.
For example: update a business email in settings, then display the approved value wherever it is needed.
Add the site details
Manage the site name, tagline, owner, organisation, location, hours, contact methods, services, and social profiles.
Set public visibility
Choose which fields may be shown. The frontend display layer uses the fields approved for public output.
Display through WordPress
Use a dynamic Gutenberg block or shortcode in a page or template. The output reads the current saved values.
03 / Capabilities
Practical tools for reusable builds.
Flexible presentation
- A dynamic Gutenberg block with theme-independent output.
- Shortcodes for fields, profiles, contacts, services, social links, attribution, and copyright.
Localised interfaces
- Maintained English and French interfaces follow the WordPress locale.
- Optional cached machine-generated language packs support additional locales.
Connected to WordPress
- Site name and tagline synchronisation.
- Administrator dashboard summary and toolbar access.
- Optional Person or Organization structured data uses public fields.
04 / Architecture
Site data and plugin code have different homes.
Git deploys the plugin code. Each site’s saved identity stays in its own WordPress database.
- Settings API
- Administrator controls for identity fields and visibility.
- Options API
- Site-specific values stored in WordPress.
- Dynamic blocks & shortcodes
- Current values displayed in content or templates.
Implementation safeguards
The codebase uses capability checks, nonces, field-specific sanitisation, contextual escaping, and WordPress translation APIs. Public output is limited to approved fields.
05 / Project status
Working software.
Room to keep improving.
The current release is used across custom WordPress builds. Next priorities include smoother onboarding, reviewed language coverage, and portable presentation patterns.
Requirements
PHP 8.1+ · WordPress 6.4+
