The dashboard applications are modular web systems developed primarily by Hilgartner Software to serve the distinct operational domains across the Hilgartner Companies network and related personal projects.

Architecture and Design of the Dashboard Applications

Built on a procedural PHP and MySQL foundation, each dashboard operates as an autonomous workspace designed to integrate with organizational tools such as Google Workspace, Moodle LMS, Slack, Trello, and Wave Accounting. Rather than operating as standalone software islands, these dashboards share a common architectural pattern to allow consistent database operations, synchronized updates, and cohesive maintenance across diverse project domains.

At the foundation of each dashboard is a framework built around a clean separation of form, data, and function. Within this triad, individual PHP pages serve as the form layer, establishing the layout shell, routing parameters, and operational modes. Backend business logic is offloaded into reusable include files stored within an inc directory: a data block handles database queries and record transactions through a $mode switch statement, while a main block delivers form inputs and presentation layouts using an equivalent $mode switch. System logic is organized around organizational units acting as containers and entities acting as objects with properties, allowing the folder topology to mirror business functions directly.

Application access and security are managed through a physical three-tier directory hierarchy comprising Guest, Member, and Team permission levels. Unauthenticated visitors land in the site root (Guest tier), registered users access the members/ directory, and administrative operators manage workflows inside the team/ directory. Each tier functions as an autonomous environment equipped with its own asset folders, organizational unit subdirectories, database credentials in inc/config.php, and gatekeeper logic in inc/setup_role.php. These gatekeepers validate session tokens, prevent unauthorized access across boundaries, define dynamic asset paths, and route authenticating users straight to the landing page of their highest authorized role.

Within any organizational unit or entity folder, interactions follow a standardized six-page CRUD matrix. This predictable structure includes index.php for list views, [orgunit]_add.php for inserts, [orgunit]_view.php for single-record views, [orgunit]_update.php for edits, [orgunit]_remove.php for soft-deletions via status flags, and [orgunit]_delete.php for permanent database record removals. For complex datasets requiring parent-child synchronization, this structure expands into multi-stage launch wizards that preserve state across steps, complemented by dynamic interface widgets like interactive banners with expandable information panels.

Deployment and ongoing maintenance across multiple domains rely on automated installer scripts that recursively deploy directory structures, resolve file collisions by timestamping existing pages into an _archive/ folder, and dynamically inject environment tokens via XML configuration files. The architecture readily integrates specialized domain capabilities, ranging from procedural e-commerce suites with product catalogs, shopping carts, inventory tracking, and net profit analytics, to gamified event badging and point reward systems.