Twitter
by @marcin_warno
·
R to @marcin_warno: Full prompt:
Add a complete Events section to the website.
1. CMS Collection "Events" with fields: event name (text), event description (rich text), date (date/time), event photo (image), speakers (reference to Team Members), location (text), event type (option: online/in-person/hybrid), registration URL (link), status (option: upcoming/past). Deploy/publish the schema so it's live.
2. Sample event — Create it programmatically using available CMS tools (MCP, API, CLI). Name: "AI Design Hackathon". Date: May 15, 2026. Location: Warsaw. Type: in-person. Status: upcoming. Speakers: Marcin Warno, Tomasz Szlachcikowski. Use images/grafit-team.png as the event photo — upload it to the CMS and assign it to the event document. Do NOT leave sample data as a manual step.
3. Events listing page (/events) — Modeled on the existing blog listing page. Separate upcoming and past events. Reuse existing components and design patterns.
Full prompt: Add a complete Events section to the website. 1. CMS Collection "Events" with fields: event name (text), event description (rich text), date (date/time), event photo (image), speakers (reference to Team Members), location (text), event type (option: online/in-person/hybrid), registration URL (link), status (option: upcoming/past). Deploy/publish the schema so it's live. 2. Sample event — Create it programmatically using available CMS tools (MCP, API, CLI). Name: "AI Design Hackathon". Date: May 15, 2026. Location: Warsaw. Type: in-person. Status: upcoming. Speakers: Marcin Warno, Tomasz Szlachcikowski. Use images/grafit-team.png as the event photo — upload it to the CMS and assign it to the event document. Do NOT leave sample data as a manual step. 3. Events listing page (/events) — Modeled on the existing blog listing page. Separate upcoming and past events. Reuse existing components and design patterns.