Sci-Fi Lore Wiki — WordPress Integration
Budget: $10 – $500 USD
Project Brief: WordPress Sci-Fi Wiki Integration (YadaWiki Preference)
Project Title: Akhentaten System Lore Bible Development
Objective:
To establish a dedicated "Lore Bible" or "Wiki" section on an existing WordPress website. The YadaWiki plugin is the preferred method for managing the core wiki articles. Each wiki article requires a structured "Infobox" (similar to Wikipedia) to display key data points. The final implementation must be fully integrated and functional within a Full Site Editing (FSE) theme environment.
Current Setup & Environment:
Platform: WordPress
Hosting: Bluehost
Theme: Anastasi (Full Site Editing Theme)
Child Theme: An active child theme is in use for custom code and modifications.
Core WordPress Version: Latest stable release.
PHP Version: Latest recommended by WordPress (developer to confirm specific version if critical).
Key Plugins & Their Roles:
Advanced Custom Fields PRO (ACF Pro):
Role: Essential for defining and managing the custom fields that comprise the "Infobox" for each wiki article.
Status: Installed, active, and an "Infobox Field Group" has been created and correctly assigned to the existing custom post type (akhentaten_system).
Custom Post Type UI (CPT UI):
Role: Used to create the custom post type and custom taxonomy. Their continued use will depend on YadaWiki's internal structure for its articles.
Status: Installed, active.
YadaWiki:
Role: Preferred plugin for managing and displaying the actual wiki articles/pages themselves. This plugin provides wiki-specific features like internal linking, tables of contents, and a dedicated wiki structure.
Status: To be installed (or existing if already present).
BetterDocs:
Note: This plugin was previously considered, but the custom post type's REST API base slug (/as/) is currently in use. Developer should be aware of potential permalink conflicts or if BetterDocs serves other purposes on the site.
Existing Custom Post Type (CPT) & Taxonomy Details:
Custom Post Type Slug: akhentaten_system
Display Labels: "Akhentaten System Articles" (Plural), "Akhentaten System Article" (Singular)
Has Archive: True; REST API Base Slug: as
Custom Taxonomy Slug: wiki_category
Display Labels: "Wiki Categories" (Plural), "Wiki Category" (Singular)
Attached To: akhentaten_system; Hierarchical: True
Note: The developer should assess whether to adapt the existing akhentaten_system CPT and wiki_category taxonomy to work with YadaWiki, or if YadaWiki's inherent content structure should be exclusively used for the wiki articles. The "Infobox" must integrate with the chosen wiki article content type.
Specific Deliverables & Developer Tasks:
YadaWiki Installation & Configuration:
Properly install and configure YadaWiki as the foundation for the wiki articles.
Address any initial permalink or general settings.
ACF Infobox Integration with Wiki Articles:
Ensure the "Infobox Field Group" (defined via ACF) can be attached to YadaWiki articles (or whichever content type is chosen for the wiki).
The custom ACF Block, named "Wiki Infobox" (name: 'wiki-infobox'), must be correctly registered and appear as an insertable block within the Gutenberg editor when editing YadaWiki articles (or the chosen wiki content type).
Confirm the block correctly renders the ACF field data using its template file (wp-content/themes/anastasi-child/blocks/infobox.php).
Full Site Editing (FSE) Template Design:
Configure or create a dedicated Full Site Editing (FSE) template to ensure YadaWiki articles display correctly and align with the site's design.
This template should correctly display:
The article's title.
The article's content (from YadaWiki).
The "Wiki Infobox" ACF Block, ideally positioned to the right or left of the main content, or above it as desired.
Permalink Structure: Ensure permalinks for the wiki articles work correctly, ideally following YadaWiki's typical structure (e.g., yourwebsite.com/wiki/article-slug/), and resolving any conflicts with the existing /as/ slug if necessary.
Current Challenges & Troubleshooting Information (for the Infobox Block):
The primary challenge encountered during initial development is that the custom "Wiki Infobox" ACF Block does not currently appear in the Gutenberg editor when editing akhentaten_system articles (this will need to be re-tested for YadaWiki articles). Extensive troubleshooting has been performed, and the following has been confirmed for the block registration code:
Child Theme functions.php:
Contains the my_acf_blocks_init() function, which calls acf_register_block_type().
The function is correctly wrapped in if ( !function_exists( 'my_acf_blocks_init' ) ) { ... } to prevent redeclaration errors.
The function is hooked to add_action('init', 'my_acf_blocks_init'); (changed from acf/init to resolve previous timing issues).
The functions.php file itself is confirmed to be loading.
Block Template File: The infobox.php file is confirmed to exist at wp-content/themes/anastasi-child/blocks/infobox.php and its content is syntactically correct for rendering ACF fields.
PHP Errors: No recent PHP Fatal Errors related to my_acf_blocks_init() or acf_register_block_type() are appearing in the PHP error logs after the latest code adjustments.
Caching: All forms of caching (browser, WordPress plugins, server-side via Bluehost) have been repeatedly and thoroughly cleared.
ACF Field Group: The "Infobox Field Group" is correctly set to display on the akhentaten_system post type. ACF fields save correctly on the backend.
Developer should investigate:
YadaWiki & ACF Block Compatibility: Determine the best strategy for integrating ACF Field Groups and the custom block with YadaWiki's content type/structure.
Browser Developer Console: Check for any JavaScript errors or warnings that might be preventing the block inserter or custom blocks from loading.
Plugin Conflicts: Systematically test for conflicts by temporarily deactivating other non-essential plugins (beyond ACF Pro, CPT UI, YadaWiki) to see if the block appears.
WordPress Block Transients: Investigate if WordPress's internal block cache (transients) might be stale and require manual flushing (though often covered by general cache clears).
Anastasi Theme Specifics: Assess if the Anastasi FSE theme has any unique behaviors or overrides that might affect custom block registration/display, especially in conjunction with YadaWiki.
Desired Outcome: A fully functional, YadaWiki-powered sci-fi lore bible where articles can be created, their "Infobox" data entered via ACF fields, and the "Wiki Infobox" block can be easily added and displayed correctly within the article content on the frontend, all seamlessly integrated with the Anastasi FSE theme.
Project Title: Akhentaten System Lore Bible Development
Objective:
To establish a dedicated "Lore Bible" or "Wiki" section on an existing WordPress website. The YadaWiki plugin is the preferred method for managing the core wiki articles. Each wiki article requires a structured "Infobox" (similar to Wikipedia) to display key data points. The final implementation must be fully integrated and functional within a Full Site Editing (FSE) theme environment.
Current Setup & Environment:
Platform: WordPress
Hosting: Bluehost
Theme: Anastasi (Full Site Editing Theme)
Child Theme: An active child theme is in use for custom code and modifications.
Core WordPress Version: Latest stable release.
PHP Version: Latest recommended by WordPress (developer to confirm specific version if critical).
Key Plugins & Their Roles:
Advanced Custom Fields PRO (ACF Pro):
Role: Essential for defining and managing the custom fields that comprise the "Infobox" for each wiki article.
Status: Installed, active, and an "Infobox Field Group" has been created and correctly assigned to the existing custom post type (akhentaten_system).
Custom Post Type UI (CPT UI):
Role: Used to create the custom post type and custom taxonomy. Their continued use will depend on YadaWiki's internal structure for its articles.
Status: Installed, active.
YadaWiki:
Role: Preferred plugin for managing and displaying the actual wiki articles/pages themselves. This plugin provides wiki-specific features like internal linking, tables of contents, and a dedicated wiki structure.
Status: To be installed (or existing if already present).
BetterDocs:
Note: This plugin was previously considered, but the custom post type's REST API base slug (/as/) is currently in use. Developer should be aware of potential permalink conflicts or if BetterDocs serves other purposes on the site.
Existing Custom Post Type (CPT) & Taxonomy Details:
Custom Post Type Slug: akhentaten_system
Display Labels: "Akhentaten System Articles" (Plural), "Akhentaten System Article" (Singular)
Has Archive: True; REST API Base Slug: as
Custom Taxonomy Slug: wiki_category
Display Labels: "Wiki Categories" (Plural), "Wiki Category" (Singular)
Attached To: akhentaten_system; Hierarchical: True
Note: The developer should assess whether to adapt the existing akhentaten_system CPT and wiki_category taxonomy to work with YadaWiki, or if YadaWiki's inherent content structure should be exclusively used for the wiki articles. The "Infobox" must integrate with the chosen wiki article content type.
Specific Deliverables & Developer Tasks:
YadaWiki Installation & Configuration:
Properly install and configure YadaWiki as the foundation for the wiki articles.
Address any initial permalink or general settings.
ACF Infobox Integration with Wiki Articles:
Ensure the "Infobox Field Group" (defined via ACF) can be attached to YadaWiki articles (or whichever content type is chosen for the wiki).
The custom ACF Block, named "Wiki Infobox" (name: 'wiki-infobox'), must be correctly registered and appear as an insertable block within the Gutenberg editor when editing YadaWiki articles (or the chosen wiki content type).
Confirm the block correctly renders the ACF field data using its template file (wp-content/themes/anastasi-child/blocks/infobox.php).
Full Site Editing (FSE) Template Design:
Configure or create a dedicated Full Site Editing (FSE) template to ensure YadaWiki articles display correctly and align with the site's design.
This template should correctly display:
The article's title.
The article's content (from YadaWiki).
The "Wiki Infobox" ACF Block, ideally positioned to the right or left of the main content, or above it as desired.
Permalink Structure: Ensure permalinks for the wiki articles work correctly, ideally following YadaWiki's typical structure (e.g., yourwebsite.com/wiki/article-slug/), and resolving any conflicts with the existing /as/ slug if necessary.
Current Challenges & Troubleshooting Information (for the Infobox Block):
The primary challenge encountered during initial development is that the custom "Wiki Infobox" ACF Block does not currently appear in the Gutenberg editor when editing akhentaten_system articles (this will need to be re-tested for YadaWiki articles). Extensive troubleshooting has been performed, and the following has been confirmed for the block registration code:
Child Theme functions.php:
Contains the my_acf_blocks_init() function, which calls acf_register_block_type().
The function is correctly wrapped in if ( !function_exists( 'my_acf_blocks_init' ) ) { ... } to prevent redeclaration errors.
The function is hooked to add_action('init', 'my_acf_blocks_init'); (changed from acf/init to resolve previous timing issues).
The functions.php file itself is confirmed to be loading.
Block Template File: The infobox.php file is confirmed to exist at wp-content/themes/anastasi-child/blocks/infobox.php and its content is syntactically correct for rendering ACF fields.
PHP Errors: No recent PHP Fatal Errors related to my_acf_blocks_init() or acf_register_block_type() are appearing in the PHP error logs after the latest code adjustments.
Caching: All forms of caching (browser, WordPress plugins, server-side via Bluehost) have been repeatedly and thoroughly cleared.
ACF Field Group: The "Infobox Field Group" is correctly set to display on the akhentaten_system post type. ACF fields save correctly on the backend.
Developer should investigate:
YadaWiki & ACF Block Compatibility: Determine the best strategy for integrating ACF Field Groups and the custom block with YadaWiki's content type/structure.
Browser Developer Console: Check for any JavaScript errors or warnings that might be preventing the block inserter or custom blocks from loading.
Plugin Conflicts: Systematically test for conflicts by temporarily deactivating other non-essential plugins (beyond ACF Pro, CPT UI, YadaWiki) to see if the block appears.
WordPress Block Transients: Investigate if WordPress's internal block cache (transients) might be stale and require manual flushing (though often covered by general cache clears).
Anastasi Theme Specifics: Assess if the Anastasi FSE theme has any unique behaviors or overrides that might affect custom block registration/display, especially in conjunction with YadaWiki.
Desired Outcome: A fully functional, YadaWiki-powered sci-fi lore bible where articles can be created, their "Infobox" data entered via ACF fields, and the "Wiki Infobox" block can be easily added and displayed correctly within the article content on the frontend, all seamlessly integrated with the Anastasi FSE theme.