One application with hub-specific identity and editorial purpose.
Verified implementation reference · August 2, 2026
What is actually built beneath this platform.
This page documents the current first-party technical evidence behind the platform: its custom PHP application, PDO data layer, MySQL/MariaDB schema, publishing administration, source records, searchable article body, moderated comments, and database-backed Life Timeline.
Different structures for articles, research, projects, tools, and milestones.
Publishing, evidence, Timeline, accounts, comments, operations, and projects.
Claim type is separated from content format and workflow status.
01
Verification scope
The page describes a dated implementation snapshot—not every future idea.
The verification basis is the current website archive, the accompanying SQL export, the public routes rendered by that code, and the administration modules contained in the build. The page summarizes what those materials support without publishing credentials, private records, session data, token values, or a downloadable copy of the source code.
Because this is Donald’s own implementation record, it is strongest as direct evidence of architecture and intended behavior. It should not be treated as an independent penetration test, performance benchmark, accessibility certification, or guarantee that every feature is free of defects.
Current means verified on August 2, 2026.
Later updates may change routes, fields, tables, safeguards, or feature status.
Application architecture
A direct request flow built for understandable maintenance.
The platform intentionally uses traditional PHP entry points, shared initialization, reusable application functions, PDO, and shared templates instead of hiding a small-site workflow behind unnecessary framework complexity.
-
01
Request entry point
A root PHP route receives the public or administrative request and loads the shared initialization layer.
index.php · post.php · search.php · timeline.php · admin/* -
02
Shared initialization
Configuration, sessions, database access, helper functions, CSRF protection, security controls, authentication, content queries, and comments are initialized once.
includes/_init.php -
03
Application services
Purpose-specific functions load posts, hubs, sources, comments, users, settings, Timeline records, and related publishing data.
includes/content.php · auth.php · comments.php · security.php -
04
PDO data access
The application uses PDO with exceptions, associative results, UTF-8, and native prepared statements rather than emulated prepares.
includes/db.php -
05
MySQL/MariaDB storage
The database snapshot contains 26 related tables covering publishing, sources, Timeline data, comments, identity, operations, and project features.
donald_faulknor.sql · verified August 2, 2026 -
06
Shared presentation
Public pages use common header, footer, metadata, responsive navigation, accessibility helpers, and page-specific styles when a custom composition is needed.
templates/header.php · templates/footer.php · assets/css/*
Verified system components
The public experience and the administration system use the same underlying records.
Each component below is represented in the current PHP files, database schema, or both. The evidence labels identify representative files, fields, or tables rather than exposing the complete private implementation.
CMS-managed publishing
The post editor stores the title, subtitle, hub, content type, slug, summary, rich body, workflow status, evidence label, discussion setting, dates, SEO fields, social fields, index status, and featured state.
admin/posts/edit.phppostshubscontent_types Revision-aware editing
Each successful save can add a revision record containing the current title, summary, rich body, editor, timestamp, and revision note, creating a dated publication history.
post_revisionsrevision_noteaudit_logs Research source system
Reusable source records store publication details, source type, URL, reliability notes, and last-checked date. Post attachments add citation order, access date, claim notes, and public-display control.
sourcespost_sourcesadmin/sources/index.php Article Design Blocks
The editor provides reusable HTML patterns for opening leads, editorial callouts, pull quotes, key points, evidence notes, and wide feature blocks while keeping the text inside the searchable post body.
admin/posts/edit.phpbody_htmlbody_text Hub-specific presentation
Ten hubs share one application but retain their own promises, descriptions, palettes, default discussion settings, ordering, and public landing-page presentation.
hubshub.phphub_style() Full-text search
Published post titles, summaries, and plain-text bodies are queried through a database FULLTEXT index. Search terms and result counts can be recorded for later editorial analysis.
search.phpFULLTEXT ft_postssearch_queries Moderated comments
The discussion system supports members and guests, approval states, replies, optional websites, link detection, signed cooldown cookies, rate limits, duplicate checks, reports, and role-aware moderation.
commentscomment_actionscomment_reportsrate_limits Database-backed Life Timeline
Timeline Entry posts store structured start and end dates, visible date wording, milestone type, optional location, major-milestone status, and same-date ordering. Every public event links to its complete post.
timeline.phptimeline_entriesincludes/content.php Administration workflow
A post moves through classification, writing, evidence, discovery, and review.
The editor is designed to preserve the context around a page rather than treating publishing as a title field plus an HTML box.
-
01
Classify
Choose one of ten hubs, twelve content types, an evidence label, a discussion state, and the appropriate workflow status.
-
02
Write
Draft the summary and TinyMCE body, including reusable design blocks when they improve rhythm, hierarchy, or comprehension.
-
03
Document
Attach source records, identify the claim each supports, set citation order and access date, and decide whether it appears publicly.
-
04
Prepare discovery
Set the slug, SEO title, meta description, index status, social title, social description, and featured state.
-
05
Publish and review
Publish immediately or schedule a date, preserve revisions, assign a future review date where facts can change, and confirm public output.
Database evidence
The schema separates concerns instead of storing the entire platform in one oversized table.
The August 2 export contains 26 tables. They are grouped below by public purpose. Raw SQL, private rows, credentials, password hashes, session files, and active token values are intentionally not published.
Publishing and knowledge
Core editorial records, organization, history, relationships, media, and reader continuity.
postshubscontent_typespost_revisionspost_relationsmediasaved_posts Research and documentation
Reusable evidence records, claim-level post attachments, and public trust or policy pages.
sourcespost_sourcespolicy_pages Timeline and participation
Chronological milestones, public discussion, moderation history, reports, and contact submissions.
timeline_entriescommentscomment_actionscomment_reportscontact_messages Identity and access
Member identity, profiles, role assignments, account recovery, verification, and persistent administrator sessions.
usersuser_profilesrolesuser_rolesemail_verificationspassword_resetsadmin_persistent_logins Operations and project features
Configuration, accountability, abuse controls, search signals, redirects, and interactive project voting.
settingsaudit_logsrate_limitssearch_queriesredirectswebsite_demo_votes Security and reliability controls
The build includes safeguards at the request, session, form, database, upload, and participation layers.
These controls reduce common risks, but their presence is not a claim that the platform has completed an independent security assessment.
Review the public trust standardsDatabase access
PDO exceptions, associative fetches, UTF-8, prepared statements, and disabled emulated prepares.
Form protection
CSRF tokens are tied to authenticated users, signed with the application key, age-limited, and regenerated when expired.
Administrator continuity
Database-backed selector and validator tokens can reconstruct authorized admin sessions when shared hosting removes PHP session data.
Output and rich text
Escaping helpers protect ordinary output, while rich HTML is limited to an approved tag set and stripped of event-handler and JavaScript URL patterns.
Uploads and abuse controls
MIME checks, size limits, randomized stored names, rate-limit records, comment cooldowns, link review, and moderation states add defensive layers.
Operational accountability
Audit records, post revisions, review dates, source-check dates, redirects, and release backups support maintenance and recovery.
Publicly observable examples
Several implementation claims can be checked directly through the live site.
Source boundary
What this page supports—and what still requires separate proof.
Supported by this reference
The August 2 build uses a custom PHP/PDO/MySQL-compatible application with CMS-managed posts, hub-specific presentation, structured publishing metadata, reusable source records, Article Design Blocks, moderated comments, full-text search, and Timeline functionality.
Not independently established
This first-party reference does not independently certify security, accessibility, legal compliance, scalability, uptime, code quality, commercial value, or whether every path behaves correctly under every hosting and user condition.
Planned features remain separate
Automatic tables of contents, one-click block insertion, advanced source maintenance, curated reading paths, reusable tool infrastructure, project showcases, and expanded community functions remain conditional roadmap items unless separately verified as deployed.