# Famado Care Famado Care is a hybrid Gutenberg WordPress theme converted from the supplied Famado HTML site. It retains the source CSS, DOM classes, JavaScript libraries, imagery, videos, responsive behavior, and three visual header variants while moving editable content into Gutenberg, record collections into WordPress queries, record attributes into registered post meta, and global areas into WordPress settings and menus. ## Installation 1. In WordPress Admin, open **Appearance → Themes → Add New → Upload Theme**. 2. Upload `famado-files.zip`, install it, and activate **Famado Care**. 3. Open the top-level **Import** screen and run **Import Famado Demo** once. 4. Review **Settings → Permalinks** and save only when the host requires an explicit refresh. The archive contains one theme directory named `famado`. The minimum declared versions are WordPress 6.6 and PHP 7.4. ## Demo import The non-network importer reads only the bundled, checksummed demo manifest and local assets. It creates or updates content by stable demo keys and does not remove unrelated site content. The import reconstructs: - 15 editable Pages covering the three homepages, three About pages, three service landing pages, team, two blog views, FAQ, contact, and the source error-page preview. - Native Posts, including the source article-detail page and the assigned `Journal` posts page. - 57 structured records across Services, Team, Testimonials, and Care Plans. - The `Care Type` taxonomy with Baby Care, Senior Care, and Pet Care terms. - 63 local Media Library entries, featured images, the site icon, primary mega menu, three footer menus, sidebar widgets, homepage/posts-page assignments, and global theme settings. Re-running the import updates matching demo items instead of creating uncontrolled duplicates. The Import screen reports success and errors through standard WordPress admin notices. Only users with `manage_options` may run it, and the action is protected by a nonce and an import lock. ## Editing content - **Pages → Edit:** edit and reorder source sections as nested Famado Gutenberg blocks. Text, links, images, video, accordions, tabs, sliders, forms, title bars, and layout wrappers remain individually selectable. - **Posts:** edit journal content through Gutenberg and standard post fields. - **Services / Team / Testimonials / Care Plans:** edit query-backed records. Structured values use registered post meta and native meta boxes; no ACF dependency is required. - **Care Type:** edit the reusable Baby, Senior, and Pet classifications. - **Appearance → Menus:** edit the primary mega menu and footer link/legal menus. Menu-item settings preserve the source mega-menu structures. - **Appearance → Customize:** edit the logo, default header style, contact details, social links, footer copy, opening hours, and related global values. - **Appearance → Editor → Styles** where available: edit colors, typography, spacing presets, content widths, links, buttons, and other `theme.json` controls. - **Appearance → Widgets:** edit the fallback blog sidebar. Each page or record also stores the required Famado header variant. Imported content can therefore preserve the Baby, Senior, and Pet source designs without hardcoded page menus. ## Gutenberg blocks The theme registers structured blocks under the **Famado Care** category. They include semantic section/layout wrappers; slider, slide, and layer composition; editable text, inline text, links, lists, images, icons, video, embeds, accordions, tabs, blockquotes, and tables; secure form blocks; dynamic title bars; query-backed collections; and current-record field output. Custom blocks disable raw HTML editing and sanitize their attributes before output. No imported page uses `core/html`, a page-sized shortcode, an iframe wrapper, or a monolithic HTML attribute. ## Forms Contact, booking, service-request, newsletter, and search interfaces use WordPress handlers. Submission forms include nonces, honeypots, server-side validation, escaped feedback, rate limiting, and Post/Redirect/Get behavior. Mail destinations default to the WordPress administration email and can be filtered by code. Actual delivery depends on the site's configured `wp_mail()` transport. ## Dependencies and compatibility - Required plugins: none. - ACF/ACF Pro: not required and not bundled. - Page builders: not required. - SEO plugins: WordPress-native titles and semantic templates remain compatible with common SEO plugins. - Source libraries: Bootstrap, Revolution Slider, Slick, AOS, PrettyPhoto, icon fonts, source images, and source videos are packaged locally because they are required by the supplied design. The original Google Fonts imports remain in the source stylesheet. ## Source-fidelity and runtime notes The original source referenced remote placeholder-image services. Equivalent local image assets were generated at the requested dimensions, and copied CSS references were rewritten to those local files so the imported site does not depend on placeholder hosts. The original Google Fonts imports are the only intentional source-origin network references. WordPress necessarily supplies canonical URLs, menu IDs/classes, attachment URLs, nonce values, form actions, post dates, comment counts, and queried record data at runtime. Those are documented execution deltas; the source structural classes, cascade, assets, section ordering, and behavior-bearing scripts remain preserved. ## Internationalization and RTL Static theme-interface strings use the `famado` text domain. A translation template is included at `languages/famado.pot`. WordPress loads `rtl.css` automatically on RTL sites; it adds directional corrections without changing the supplied LTR stylesheet. ## Validation See `QA-REPORT.md` for the packaged validation scope and results. Package installation can also be verified with the separately supplied fail-closed `apply-and-verify-famado.sh` script.