InvisionFree Magazine 2.0 — installation and date preservation

1. Extract the outer ZIP. Open START-HERE.html to browse the offline preview and original archive.
2. WordPress: Appearance > Themes > Add New > Upload Theme. Upload wordpress-theme/invisionfree-magazine.zip and activate it. Upload the nested theme ZIP, not the outer all-in-one package.
3. Settings > Reading: select "Your latest posts" to show the magazine homepage.
4. Tools > Import > WordPress: import blog-content/wordpress-posts-original-dates.xml. Map the author to your preferred account. The 212 posts have historical publication dates, original-date labels and source metadata.
5. Covers appear automatically from the theme. Optionally open Appearance > Magazine media setup and click "Attach included cover images" to copy the bundled covers into your Media Library and set featured images. Existing featured images are skipped. This action updates attachment/thumbnail metadata; it does not change post publication dates or article text. If interrupted, you can run it again.
6. Appearance > Menus: create your navigation. Existing categories appear automatically when no menu is assigned. Add technology, business, lifestyle, health, entertainment or any other categories for your new posts.
7. Appearance > Customize: set your logo, site title, introduction and homepage headlines. Set a featured image in the post editor to replace any included cover. Sidebar widgets are available under Appearance > Widgets.
8. Settings > General: use InvisionFree as the site title. SEO.txt contains the suggested homepage title and description for your chosen SEO settings.

POST DATES
212 imported posts have a recoverable publication day, month and year. WordPress post_date retains that historical date. It is not the adaptation or archive-capture date. Source times are preserved as local time; no original time zone is assumed. If only a day is known, 00:00 is the import-time placeholder. The theme displays the original source date label.

12 complete bodies have incomplete/absent publication dates. They are included in all-adapted-posts.json, date-review-required.json and the preview. They are excluded from automatic published import so that no historical date is invented. Review these records before publishing them yourself.

Original texts remain in archive-backup. Blog versions have clearer headings/paragraph formatting, three revised guide titles/introductions and minor typo fixes. Historical facts are retained. Adaptations carry a separate edit date of 27 October 2026.

PICTURES
All 224 preview articles have local covers: one recovered original article cover and 223 covers using four new editorial illustrations. See design-assets/cover-report.json for the per-post mapping. These illustrations are reused by subject. Article captions identify illustrations and recovered originals.

Nine recovered inline image files are bundled. The theme redirects matching image URLs to local files when displaying imported posts. Other original inline images could not be recovered; their historical URLs are retained in the unchanged import data. The offline preview uses an unavailable-image placeholder for those missing files. See design-assets/image-availability.json.

STATIC PREVIEW
Open magazine-preview/index.html. Navigation, pagination, categories, article covers, related stories, mobile menu, dark mode and local search are included. It contains no WordPress admin or database. Covers, CSS and JavaScript work from local files without external fonts/libraries. Source links and historical external article links require an internet connection.

VERIFICATION
The responsive preview was checked at 320, 390, 768 and 1440 pixel frame widths. Search, mobile menu, theme switch and article navigation passed. All 224 cover mappings and unchanged archive/blog data were verified. All 14 PHP files passed PHP 7.4 syntax parsing; both JavaScript files passed syntax checks.

Live WordPress activation, Media Library setup and import were not executed in this workspace because no WordPress/PHP server is installed. Run those steps on your WordPress installation. See verification.json for exact checks and recovery gaps.
