This section is now wired into the database-driven public site and ready for expanded content.

DOCUMENTATION

Documentation

Open standalone
Documentation art

Documentation

This page exists to prove the public site is rendering real database content through view.php. The menu is generated from the pages table, ordered by position, and nested by owner.

Real routing

Menu items now link to ?slug=... pages instead of being fake placeholders.

Child support

Documentation has seeded child pages so you can test drop downs and flyout menus immediately.

Prism ready

Code blocks use language-python and are highlighted by Prism on both page load and modal preview.

Getting Started

Open page

Getting Started

The quickest way to validate the front end is to install the SQL, hit the home page, and open the seeded pages from the dynamic menu. This page is a child of Documentation and proves the rollout stays open long enough to use.

from qtpy.QtWidgets import QApplication, QLabel

app = QApplication([])
label = QLabel("Hello from CutiePy")
label.resize(320, 60)
label.show()
app.exec()

Dynamic Menu

Open page

Dynamic Menu

The top navigation is built from the pages table. Parent-child relationships are determined by the owner column, and nested flyouts are rendered recursively.

  • Top-level pages have owner = 0.
  • Child pages store the parent page ID in owner.
  • Ordering comes from position.

Python Sample

Open page

Python Sample

This page is seeded specifically so you can verify Prism is wired up correctly on a real installed page.

class CutieWindow:
    def __init__(self, title: str) -> None:
        self.title = title
        self.widgets = []

    def addWidget(self, widget: str) -> None:
        self.widgets.append(widget)

    def describe(self) -> str:
        return f"{self.title} with {len(self.widgets)} widgets"

window = CutieWindow("CutiePy Demo")
window.addWidget("NavigationBar")
window.addWidget("CodePanel")
print(window.describe())

EXAMPLES

Examples

Open standalone
Examples art

Examples

These sample pages exist to test database-backed navigation, child items, media blocks, and highlighted code.

CutiePy interface mockup
Sample visual content seeded directly into the install SQL.

Startup Window

Open page

Startup Window

A product page can show a startup view, hero explanation, and implementation notes without leaving the main site shell.

Window frame source image
Seeded media block for layout testing.

Theme XML

Open page

Theme XML

Use this sample child page to document export formats, theme tokens, or settings serialization.

<theme name="CutiePy Default">
  <color name="brand" value="#2A368F" />
  <color name="accent" value="#FFD456" />
  <image name="hero" path="/img/fusion-bg.png" />
</theme>

Embedded Assets

Open page

Embedded Assets

This sample page gives you a place to document icons, screenshots, audio cues, and other application-facing front end assets.

Badges

Provider and framework badges can sit in CMS content blocks.

Images

Cache-broken image URLs still render through dynamic content.

Audio

The public page keeps the click/open cues while using real page routing.

WITH FLATLINE DEBUGGER

With FlatLine Debugger

Open standalone
With FlatLine Debugger art

With FlatLine Debugger

FlatLine gives the product a technical edge: parent-child process monitoring, crash visibility, and watchdog behavior without hiding broken state.

FlatLine debugger graphic
FlatLine branding integrated as a secondary product badge.

ABOUT

About art

About

CutiePy is a cute but technical Qt/Python application shell presented through a CMS-driven front end. This seed set is designed to test the menu, nested pages, routing, and code display with real data.

The red bleed-through header issue is fixed by scoping the public header styles separately from the CMS admin header.