Kilnfold is a ten-page static HTML template for pottery studios, ceramics schools, shared workshops, independent teachers, and community kiln spaces. It combines class discovery, weekly schedules, memberships, studio access, firing services, instructor profiles, gallery content, journal stories, and inquiry guidance in one original editorial system.

Included pages

• Home and studio overview
• Classes and weekly schedule
• Class detail
• Memberships and comparison
• Studio, facilities, and first visit
• Firing services
• Filterable gallery
• Instructors
• Journal
• Contact and safe demo inquiry

Product boundary

Kilnfold is a static front-end template. It does not include booking, payments, memberships, accounts, email delivery, a CMS, analytics, hosting, or a backend. All studio details are fictional demonstrations and must be replaced and verified by the buyer. The included form sends no data until the buyer connects a secure endpoint.

Support

Support covers the supplied file structure, documented customization, and reproducible defects in the unmodified source. Custom development, backend services, integrations, hosting, framework conversion, and third-party configuration are not included.

• Ten purposeful, connected HTML pages
• Original warm editorial pottery-studio visual system
• Responsive at 360, 768, 1440, and 1920 pixels
• Semantic HTML5, modern CSS, and Vanilla JavaScript
• No framework, build step, package manager, CDN, remote font, or runtime network dependency
• Filterable class catalog and keyboard-accessible weekly schedule
• Detailed class outcomes, levels, materials, timing, and instructor content
• Membership tiers and keyboard-focusable comparison table
• Studio facilities, access notes, first-visit guidance, and process
• Firing services, kiln options, turnaround, sample rates, and FAQ
• Filterable pottery gallery and editorial journal system
• Local-only inquiry-form validation that sends no data
• Skip link, landmarks, visible focus, reduced-motion behavior, and meaningful image alternatives
• Five product-specific generated images with recorded provenance
• Complete English documentation, credits, licenses, changelog, version, customization guidance, and support scope

• A modern browser for preview and editing
• A text or code editor
• Any trusted static web server or host selected by the buyer
• Buyer-supplied services for real forms, booking, payments, accounts, email, content management, or data persistence

1. Extract the buyer ZIP and keep the folder structure unchanged.
2. Read README.md and documentation/index.html for setup, page structure, design tokens, and customization guidance.
3. Edit the HTML content and the CSS variables in assets/css/styles.css.
4. Replace every fictional studio detail, biography, price, schedule, policy, access statement, address, and contact value.
5. Connect the demonstration form only to a secure endpoint you control, then validate consent, privacy, spam protection, and error handling.
6. Preview every page through a local static server and test the final site before publishing.