Files
laraundfelix/docs/ux/verwaltung/generierung/cms-prompts.md
T
Lars 4c29ab2593
Deploy Test / test (push) Successful in 55s
Deploy Test / deploy (push) Successful in 24s
Führe den gemeinsamen Redaktionsarbeitsplatz ein.
Texte, Medienzuordnung und Einordnung teilen sich einen Arbeitsplatz. Fassungen, Rechte und das Datenmodell bleiben unverändert.
2026-11-19 14:43:15 +01:00

22 KiB
Raw Blame History

CMS-Seiteneditor – Generierung der Anordnungen

Datum: 19.11.2026. Integrierter Bildgenerator. Drei unabhängige CMS-Anordnungen innerhalb des bereits gewählten Verwaltungsrahmens. Reihenfolge entspricht der tatsächlichen Anzeige im Gespräch. Keine Anordnung ausgewählt und keine Umsetzung.

Referenzen aller Aufrufe

  1. B15: verschachtelter CMS-Editor, vorhandene Fähigkeiten und zu reduzierende Strukturmechanik.
  2. B16: Widgetdialog, Inhalts-, Medien- und Darstellungsaufgaben.
  3. B19: kompakte Struktur, positive strukturelle Referenz.
  4. B18: Seitenausgabe in Vorschau, vorhandener Ausgabe-/Vorschaurahmen.
  5. Gewählter Verwaltungsrahmen.

Die Quellen wurden direkt betrachtet und als lokale Bildreferenzen an jeden Aufruf übergeben. Sie sind frühere Auditbelege, kein neuer Live-Audit. Die bekannte Anmeldegrenze ist in Dokument 11 erhalten; die Fortführung der Entwurfsarbeit wurde danach vom Auftraggeber beauftragt.

Angezeigter Entwurf 1: Struktur und fester Bearbeitungsbereich

Ausgabe: cms-01-struktur-bearbeitung.png.

Exakter Prompt

Use case: ui-mockup. Create realistic production-quality German desktop CMS administration UI for Lara & Felix. ONE independent focused design, not a collage, no browser or device frame. Target 1487 x 1058. Current date anchor 19 November 2026; no dates need be shown.
Reference images: image 1 current CMS expanded editor demonstrates excessive nested frames to improve, image 2 current widget dialog provides real field/content patterns, image 3 current compact CMS outline is a positive reference, image 4 existing real rendered page preview grounds CMS output and brand, image 5 is the selected new admin frame to MATCH for administration. Preserve the approved quiet white admin surfaces, navy typography, green primary action, restrained blue selection and sensible spacing. Existing public widget styling is its own rendered content, never turn admin into a promotional landing page.
Context: owner-operated platform, modest catalog, usually one editor. Keep Laravel/Filament/Livewire-compatible existing CMS model Page -> Sections -> Slots -> Widget. Existing widget registry, section grids, central media and program references, revisions and renderers remain. Do not invent another CMS, freeform absolute-position canvas, AI composer, dashboards or seven-stage release process.
Global left nav exactly "Lara & Felix", "Verwaltung"; Arbeitsplatz, Medien, Inhalte, Angebote, Website SELECTED, Kunden. Approx 210px wide like reference 5. Breadcrumb "Website / Seiten / Prävention im Alltag". Page title "Prävention im Alltag". Header status "Entwurf · Änderungen nicht gespeichert" with amber indicator. Separate quiet fact "Öffentlich: Revision 12". This is illustrative data, not claims about actual content of reference screenshots.
Header right: ONE primary green "Entwurf speichern", secondary outlined eye "Seitenvorschau", subdued supporting "Veröffentlichen…" (not a green competing button). This CMS action may save and publish the current page draft through the existing explicit flow, no new business-release process. Shared page tabs "Seiteninhalt" active, "Seiteneinstellungen", "Verlauf". Address and SEO belong to Seiteneinstellungen rather than a permanent giant form above the content.
Same example page composition in all designs:
- Abschnitt 1 "Einstieg", grid 4 full width, widget Einstieg (Hero).
- Abschnitt 2 "Training im Alltag", grid 2 + 2: first slot Bild und Text; second slot Programmkarte "Programm Abstand", SELECTED.
- Abschnitt 3 "Häufige Fragen", grid 4, widget FAQ.
Use natural training/park thumbnails, not placeholder posters or giant decorative background art. Page output may show headline "Stark im Alltag", a concise text about personal boundaries, a small program card, and FAQ; no price, purchase CTA or invented shop.
Current editing target is the ONE program-card widget in Abschnitt 2, second slot. Do not mix page settings, section layout and all widget controls into one panel.
Selected widget content editor:
heading "Programmkarte"; path "Abschnitt 2 · Training im Alltag". Tabs "Inhalt" active, "Medien", "Darstellung".
Source line "Quelle: Programm Abstand (Programm)" and link "Redaktion öffnen" for shared source editorial manager, with context/return handled later. Source is a reference, not copied data.
"Überschrift": effective value "Programm Abstand", subtle label "Aus Programm übernommen"; supporting link "Hier anpassen".
"Kurztext": own local override textarea "Übungen für mehr Sicherheit im Alltag." and label "Eigene Angabe für diese Karte"; small "Wieder übernehmen" action.
Small scope note "Lokale Änderungen gelten nur für diese Karte." It must not say source editing has only local effect.
Media tab would use the shared media picker and show website permission, not a text radio list. Do not put all media and display settings permanently into active Inhalt tab.
Reordering sections and widgets uses targeted handles and keyboard alternatives, and only valid destinations. No drag handles on every nested frame. Selected-widget menu can expose duplicate/remove-assignment; never present global source deletion as removing a widget.
Any widget preview is identified "Bausteinvorschau"; it should include its section surface where relevant. Page preview is distinct, names draft/revision and device width, never claims an unapproved source asset publicly available. Current page editor in images is NOT proof of functional rendering.
Keep at most two main content areas after global navigation. Use whitespace and simple dividers instead of nested cards. Natural readable type 14-16px body, page title max36, stable control placements. Source fields should be truly readable, and UI fit viewport with no overlapping/clipped controls. No huge full-page explanatory banners, no field inventory, no extra template/global-section functionality.
Direction name: Struktur und fester Bearbeitungsbereich.
Under the page tabs create a 33%-wide compact structural outline on the left and a 67%-wide selected-widget editor on the right. The positive outline reference 3 and selected program workspace frame reference 5 guide grouping.
Outline header "Seitenstruktur", quiet "+ Abschnitt" action. Three compact section groups with ordinal 1/2/3 and small grid summary "4" or "2 + 2". First/third collapsed enough to read names. Second expanded shows its two slots as indented thumbnail rows: "Bild und Text", and SELECTED "Programmkarte · Programm Abstand" with thin blue outline. The grouping visibly distinguishes section and contained widget, without repeated raster panels. Place movement alternatives only for selected meaningful target, not every row.
Main right pane contains the selected widget editor as specified, with spacious form for inherited heading and the ONE local short-text override. Section layout controls appear only if the section itself is selected; do not show all raster choices now.
A modest lower "Bausteinvorschau" can show the program card on its section surface, but do not let it dominate the active editing pane or add another full webpage. It is okay to show a collapsed preview link if that keeps the active form legible.
User model: always see where the widget sits while editing at a stable place; navigate by structure, not by scrolling through many giant sections. Main source/display tools are accessible in respective tabs. No modal overlay.

Angezeigter Entwurf 2: Visuelle Seitenfläche mit Kontextinspektor

Ausgabe: cms-02-seitenflaeche-inspektor.png.

Exakter Prompt

Use case: ui-mockup. Create realistic production-quality German desktop CMS administration UI for Lara & Felix. ONE independent focused design, not a collage, no browser or device frame. Target 1487 x 1058. Current date anchor 19 November 2026; no dates need be shown.
Reference images: image 1 current CMS expanded editor demonstrates excessive nested frames to improve, image 2 current widget dialog provides real field/content patterns, image 3 current compact CMS outline is a positive reference, image 4 existing real rendered page preview grounds CMS output and brand, image 5 is the selected new admin frame to MATCH for administration. Preserve the approved quiet white admin surfaces, navy typography, green primary action, restrained blue selection and sensible spacing. Existing public widget styling is its own rendered content, never turn admin into a promotional landing page.
Context: owner-operated platform, modest catalog, usually one editor. Keep Laravel/Filament/Livewire-compatible existing CMS model Page -> Sections -> Slots -> Widget. Existing widget registry, section grids, central media and program references, revisions and renderers remain. Do not invent another CMS, freeform absolute-position canvas, AI composer, dashboards or seven-stage release process.
Global left nav exactly "Lara & Felix", "Verwaltung"; Arbeitsplatz, Medien, Inhalte, Angebote, Website SELECTED, Kunden. Approx 210px wide like reference 5. Breadcrumb "Website / Seiten / Prävention im Alltag". Page title "Prävention im Alltag". Header status "Entwurf · Änderungen nicht gespeichert" with amber indicator. Separate quiet fact "Öffentlich: Revision 12". This is illustrative data, not claims about actual content of reference screenshots.
Header right: ONE primary green "Entwurf speichern", secondary outlined eye "Seitenvorschau", subdued supporting "Veröffentlichen…" (not a green competing button). This CMS action may save and publish the current page draft through the existing explicit flow, no new business-release process. Shared page tabs "Seiteninhalt" active, "Seiteneinstellungen", "Verlauf". Address and SEO belong to Seiteneinstellungen rather than a permanent giant form above the content.
Same example page composition in all designs:
- Abschnitt 1 "Einstieg", grid 4 full width, widget Einstieg (Hero).
- Abschnitt 2 "Training im Alltag", grid 2 + 2: first slot Bild und Text; second slot Programmkarte "Programm Abstand", SELECTED.
- Abschnitt 3 "Häufige Fragen", grid 4, widget FAQ.
Use natural training/park thumbnails, not placeholder posters or giant decorative background art. Page output may show headline "Stark im Alltag", a concise text about personal boundaries, a small program card, and FAQ; no price, purchase CTA or invented shop.
Current editing target is the ONE program-card widget in Abschnitt 2, second slot. Do not mix page settings, section layout and all widget controls into one panel.
Selected widget content editor:
heading "Programmkarte"; path "Abschnitt 2 · Training im Alltag". Tabs "Inhalt" active, "Medien", "Darstellung".
Source line "Quelle: Programm Abstand (Programm)" and link "Redaktion öffnen" for shared source editorial manager, with context/return handled later. Source is a reference, not copied data.
"Überschrift": effective value "Programm Abstand", subtle label "Aus Programm übernommen"; supporting link "Hier anpassen".
"Kurztext": own local override textarea "Übungen für mehr Sicherheit im Alltag." and label "Eigene Angabe für diese Karte"; small "Wieder übernehmen" action.
Small scope note "Lokale Änderungen gelten nur für diese Karte." It must not say source editing has only local effect.
Media tab would use the shared media picker and show website permission, not a text radio list. Do not put all media and display settings permanently into active Inhalt tab.
Reordering sections and widgets uses targeted handles and keyboard alternatives, and only valid destinations. No drag handles on every nested frame. Selected-widget menu can expose duplicate/remove-assignment; never present global source deletion as removing a widget.
Any widget preview is identified "Bausteinvorschau"; it should include its section surface where relevant. Page preview is distinct, names draft/revision and device width, never claims an unapproved source asset publicly available. Current page editor in images is NOT proof of functional rendering.
Keep at most two main content areas after global navigation. Use whitespace and simple dividers instead of nested cards. Natural readable type 14-16px body, page title max36, stable control placements. Source fields should be truly readable, and UI fit viewport with no overlapping/clipped controls. No huge full-page explanatory banners, no field inventory, no extra template/global-section functionality.
Direction name: Visuelle Seitenfläche mit Kontextinspektor.
Under the common page tabs show a large VISUAL page-editing surface about 68% of the available workspace width on left and a fixed context inspector about 32% on right. Do not add a persistent second structural sidebar; a quiet "Struktur" button can open the outline on demand. The difference from structural editing is choosing the element on its visible page representation.
Left heading "Arbeitsansicht" with small note "Ausgewählt: Abschnitt 2 · Programmkarte". The canvas shows the same example page's three sections compactly:
Einstieg: a restrained crop of a photo-with-text widget with navy heading "Stark im Alltag" and a small authentic park photograph; not a huge marketing hero.
Training im Alltag: two equal columns, "Bild und Text" content on left and the program card on right. The right card has title "Programm Abstand", current local summary "Übungen für mehr Sicherheit im Alltag.", real thumbnail, and a clear thin BLUE editing-selection outline. Selection controls visually belong to the editor, not a public purchase CTA. Section 2 context label at its top and a small section-action menu, not every grid option. This render is a working canvas; do not label this narrow area Desktop 1440px or promise full-size page fidelity.
Häufige Fragen: small visible FAQ heading and one collapsed question, below selected section. If room include quiet "+ Abschnitt hinzufügen" at bottom. Avoid nested heavy containers around every grid slot.
Right inspector: heading "Programmkarte", path "Abschnitt 2 · Training im Alltag", tabs "Inhalt", "Medien", "Darstellung", and precisely the common source/heading/local-shorttext fields. The own local override textarea must be actually readable, the source line and "Redaktion öffnen" access clear. A compact overflow menu may expose movement, duplicate and remove from page, without duplicating a whole toolbar on every canvas block.
The page-wide preview is still the top "Seitenvorschau" button; do not add a second redundant full-page preview or lower card preview in inspector, since the canvas already shows it.
User model: see roughly the result on the left and select a widget to change its content beside it. Section layout settings appear only when selecting the section. Public and admin framing remain distinct. Use realistic spacing and complete visible controls rather than an overstuffed three-column dashboard.

Angezeigter Entwurf 3: Großzügige Einzelbearbeitung mit Rückweg

Ausgabe: cms-03-einzelbearbeitung.png.

Exakter Prompt

Use case: ui-mockup. Create realistic production-quality German desktop CMS administration UI for Lara & Felix. ONE independent focused design, not a collage, no browser or device frame. Target 1487 x 1058. Current date anchor 19 November 2026; no dates need be shown.
Reference images: image 1 current CMS expanded editor demonstrates excessive nested frames to improve, image 2 current widget dialog provides real field/content patterns, image 3 current compact CMS outline is a positive reference, image 4 existing real rendered page preview grounds CMS output and brand, image 5 is the selected new admin frame to MATCH for administration. Preserve the approved quiet white admin surfaces, navy typography, green primary action, restrained blue selection and sensible spacing. Existing public widget styling is its own rendered content, never turn admin into a promotional landing page.
Context: owner-operated platform, modest catalog, usually one editor. Keep Laravel/Filament/Livewire-compatible existing CMS model Page -> Sections -> Slots -> Widget. Existing widget registry, section grids, central media and program references, revisions and renderers remain. Do not invent another CMS, freeform absolute-position canvas, AI composer, dashboards or seven-stage release process.
Global left nav exactly "Lara & Felix", "Verwaltung"; Arbeitsplatz, Medien, Inhalte, Angebote, Website SELECTED, Kunden. Approx 210px wide like reference 5. Breadcrumb "Website / Seiten / Prävention im Alltag". Page title "Prävention im Alltag". Header status "Entwurf · Änderungen nicht gespeichert" with amber indicator. Separate quiet fact "Öffentlich: Revision 12". This is illustrative data, not claims about actual content of reference screenshots.
Header right: ONE primary green "Entwurf speichern", secondary outlined eye "Seitenvorschau", subdued supporting "Veröffentlichen…" (not a green competing button). This CMS action may save and publish the current page draft through the existing explicit flow, no new business-release process. Shared page tabs "Seiteninhalt" active, "Seiteneinstellungen", "Verlauf". Address and SEO belong to Seiteneinstellungen rather than a permanent giant form above the content.
Same example page composition in all designs:
- Abschnitt 1 "Einstieg", grid 4 full width, widget Einstieg (Hero).
- Abschnitt 2 "Training im Alltag", grid 2 + 2: first slot Bild und Text; second slot Programmkarte "Programm Abstand", SELECTED.
- Abschnitt 3 "Häufige Fragen", grid 4, widget FAQ.
Use natural training/park thumbnails, not placeholder posters or giant decorative background art. Page output may show headline "Stark im Alltag", a concise text about personal boundaries, a small program card, and FAQ; no price, purchase CTA or invented shop.
Current editing target is the ONE program-card widget in Abschnitt 2, second slot. Do not mix page settings, section layout and all widget controls into one panel.
Selected widget content editor:
heading "Programmkarte"; path "Abschnitt 2 · Training im Alltag". Tabs "Inhalt" active, "Medien", "Darstellung".
Source line "Quelle: Programm Abstand (Programm)" and link "Redaktion öffnen" for shared source editorial manager, with context/return handled later. Source is a reference, not copied data.
"Überschrift": effective value "Programm Abstand", subtle label "Aus Programm übernommen"; supporting link "Hier anpassen".
"Kurztext": own local override textarea "Übungen für mehr Sicherheit im Alltag." and label "Eigene Angabe für diese Karte"; small "Wieder übernehmen" action.
Small scope note "Lokale Änderungen gelten nur für diese Karte." It must not say source editing has only local effect.
Media tab would use the shared media picker and show website permission, not a text radio list. Do not put all media and display settings permanently into active Inhalt tab.
Reordering sections and widgets uses targeted handles and keyboard alternatives, and only valid destinations. No drag handles on every nested frame. Selected-widget menu can expose duplicate/remove-assignment; never present global source deletion as removing a widget.
Any widget preview is identified "Bausteinvorschau"; it should include its section surface where relevant. Page preview is distinct, names draft/revision and device width, never claims an unapproved source asset publicly available. Current page editor in images is NOT proof of functional rendering.
Keep at most two main content areas after global navigation. Use whitespace and simple dividers instead of nested cards. Natural readable type 14-16px body, page title max36, stable control placements. Source fields should be truly readable, and UI fit viewport with no overlapping/clipped controls. No huge full-page explanatory banners, no field inventory, no extra template/global-section functionality.
Direction name: Großzügige Einzelbearbeitung mit Rückweg.
Keep exactly the common page header, global navigation, page tabs, illustrative current/public state and page-level actions. This is a focused MODE of the same page editor, not an independent widget administration or modal blocking the page actions.
Under page tabs show a prominent but quiet left-arrow text link "Zur Seitenstruktur", then heading "Programmkarte bearbeiten", breadcrumb/path "Abschnitt 2 · Training im Alltag · Platz 2". A short note "Änderungen bleiben im Seitenentwurf erhalten." The normal page outline is off screen in this focus mode and returns through that link with selection, open edits and scroll position retained.
Use the broad workspace for TWO areas: about 55% content editor on left, 45% isolated Bausteinvorschau on right. Do not insert another nested sidebar or all-page canvas. This differs from direction with permanent outline: here the editor gains room and the source context is explicit.
Left editor tabs Inhalt active, Medien, Darstellung. Content pane contains the shared source and inheritance controls, inherited heading with "Hier anpassen", own local Kurztext textarea with the exact shared sentence and "Wieder übernehmen", plus the exact local scope note. No other field inventory and no new asset/version/release settings.
Right area heading "Bausteinvorschau", sublabel "Im Kontext von Abschnitt 2". A well-proportioned single program card on a quiet light section surface shows natural training image, title Programm Abstand and summary matching own edited text. It is not a big shop page or the full page preview. Do not label this preview public/approved or Desktop1440. Small link "Ganze Seite prüfen" may refer to the same page preview but avoid duplicating actions if it creates clutter.
Below the editor/preview pair a quiet full-width context strip can state "Diese Karte verwendet Angaben aus Programm Abstand. Eigene Angaben überschreiben nur diese Verwendung." If it duplicates existing note omit it.
There is NO per-widget Save or Übernehmen button. Changes in this focused editing mode remain in the in-memory page working draft; top "Entwurf speichern" is the one explicit persistence action. Return does not silently discard or publish. Keep the top supporting Veröffentlichen… visible as page action, not a third widget release button.
User model: focus on one content unit with adequate room, inspect its actual card next to fields, then return one step to the page outline. Strong typographic hierarchy and ordinary product UI, not a wizard or dashboard.