Create and publish an event page

01

Quick start

1. Get the latest master project. Work from the approved shared ZIP or folder—not from an old local copy.
2. Copy example-event/. Rename it using lowercase letters, numbers and hyphens, for example partner-2026.
3. Create the page. Edit the copy yourself or give the prompt below to an AI agent together with the event content.
4. Review locally. Check copy, links, layout, privacy and the technical checklist.
5. Upload the full project as Preview. Verify the Cloudflare preview URL.
6. Upload the exact same files to Production. Verify both / and the new event URL.
7. Save the new master. Replace the shared master ZIP/folder so the next editor starts from this version.

02

Environment rules

The platform serves static HTML, CSS, JavaScript and assets. Central security headers deliberately restrict what pages can execute or contact.

Path rules

Keep every event self-contained. From /partner-2026/index.html, prefer ./styles.css, ./script.js and ./assets/photo.webp. Do not reference assets inside another event folder.

03

You are creating a self-contained static event website that will be published at:
https://events.prowise.com/<event-slug>/

Create a folder named <event-slug> containing at least:
- index.html
- styles.css
- script.js only if interaction is genuinely needed
- assets/ for all images, icons and fonts

Technical constraints:
1. Use plain, standards-based HTML, CSS and JavaScript. Do not require a build step, package manager, framework, server or Cloudflare Function.
2. Put CSS in local .css files. Do not use inline style attributes or <style> blocks.
3. Put JavaScript in local .js files referenced with a relative src. Do not use inline scripts, inline event handlers, eval(), new Function(), dynamically generated executable code, WebAssembly or service workers.
4. Do not load any remote script, stylesheet, font, image, iframe, embed or other dependency. Store every required asset inside the event folder.
5. Do not use fetch, XMLHttpRequest, WebSocket, EventSource, remote APIs or form submission. Use normal links for calls to action.
6. Use relative paths such as ./styles.css and ./assets/image.webp so the page works below /<event-slug>/ and does not depend on other event folders.
7. Do not include secrets, credentials, analytics, tracking pixels, cookies, localStorage or personal data.
8. Make the result responsive and accessible: semantic landmarks, logical headings, keyboard access, visible focus, sufficient contrast, meaningful alt text and reduced-motion support.
9. Include appropriate title, description and social sharing metadata, but reference only local assets.
10. Keep the implementation compact and readable. Add comments only where they help a future non-specialist editor.

Content and design brief:
[PASTE THE APPROVED EVENT BRIEF, COPY AND VISUAL DIRECTION HERE]

Before finishing, verify every path and list all generated files. Explicitly report any requested feature that cannot work within these constraints instead of bypassing a constraint.

The prompt creates compatible output; it does not replace human review of facts, branding, rights, privacy or security.

04

Review before uploading

05

Upload to Cloudflare Pages

1. Prepare the complete project root. If using a ZIP, index.html, how-to.html, _headers and the event folders must be at the ZIP root—not inside an extra wrapper folder.
2. Open Cloudflare Dashboard → Workers & Pages → the events Pages project.
3. Select Create a new deployment and choose a Preview deployment.
4. Drag in the complete folder or ZIP, then deploy. Do not upload only the changed event directory.
5. Open the preview URL. Check the home page, the new event path, assets, links, console and mobile layout.
6. Create a second deployment, choose Production, and upload the exact same unchanged folder or ZIP.
7. Verify https://events.prowise.com/ and https://events.prowise.com/<event-slug>/. Keep the previous deployment available for rollback.
8. Store this deployed version as the new approved master project.

06

Expected folder structure

project-root/
├── index.html
├── how-to.html
├── 404.html
├── _headers
├── robots.txt
├── assets/
│   ├── site.css
│   └── how-to.js
├── example-event/
│   ├── index.html
│   ├── styles.css
│   ├── script.js
│   └── assets/
└── partner-2026/
    ├── index.html
    ├── styles.css
    ├── script.js
    └── assets/

Delete script.js when an event needs no interaction. Empty asset folders are not required in the upload.