Visual Studio
Build responsive pages from reusable components, edit content inline, and keep desktop and mobile presentation under control.
- Component library and inspector
- Responsive canvas and previews
- Draft-safe editing and undo history
Features
Website builder, commerce, AI, and publishing in one platform
Build responsive websites, organize media, prepare products, use reviewable AI workflows, and publish from one connected creator platform.
Overview
What this means in practice
Explore the systems, responsibilities, and workflows behind this part of Sklash.
Media Center
Upload, organize, search, reuse, replace, and retire assets across the Sites in a Workspace.
- Central asset library
- Metadata and usage visibility
- Responsive image variants
Publishing and revisions
Separate editing from the live Site, validate important changes, and preserve recoverable versions before and after publishing.
- Draft and published documents
- Revision history and restoration
- Release validation controls
Commerce foundation
Prepare catalogs, prices, customer records, orders, and checkout components without operating a disconnected storefront.
- Products and pricing
- Orders and customers
- Page-level commerce components
Reviewable AI workflows
Ask specialized AI agents to draft, inspect, and propose changes while keeping application approval with the creator.
- Specialized minions
- Proposal and approval workflow
- Verification and audit history
Domains, SEO, and health
Manage public addresses, page metadata, discovery files, release checks, and operational signals from the same platform.
- Custom-domain foundation
- Canonicals, robots, and sitemaps
- Site health and validation
One connected workflow
Move from the first page draft to a published Site without rebuilding your work between tools.
Sklash treats the website, media library, commerce catalog, publishing state, and AI assistance as parts of the same creator workspace. Content created in one area remains available to the systems that need it.
That connected model reduces duplicate setup and makes important actions—such as replacing an image, restoring a revision, or reviewing an AI proposal—easier to trace and control.
- Create and organize multiple Sites inside scoped Workspaces.
- Reuse assets and structured components instead of copying disconnected files.
- Keep drafts private until the creator explicitly publishes them.
- Review operational and release signals before sharing work publicly.
Creator control
Automation should accelerate decisions, not silently make them.
Sklash AI is designed around proposals, ownership boundaries, and verification. Specialized agents can inspect the current Site context and prepare structured work, but meaningful mutations remain visible and reviewable.
- AI-generated work is attached to the relevant Workspace, Site, or Page.
- Proposals can be approved, regenerated, rejected, or inspected before application.
- Verification records explain what was checked and what still needs attention.
- Publishing remains a separate creator-controlled action.
Questions
Clear answers before the next step
These answers describe the current pre-release service and may evolve as Sklash approaches production.
Can I build without using AI?
Yes. The Studio, media, publishing, SEO, and commerce foundations are designed to work directly. AI is an optional assistant layer, not a requirement for editing or publishing.
Does Sklash publish every change immediately?
No. Editing and publishing are separated so creators can review drafts, validate important changes, and decide when the public Site should update.
Can one account manage more than one website?
Yes. Sklash organizes work into Workspaces, Sites, and Pages so creators and future teams can keep separate projects scoped and manageable.
Is Commerce required?
No. A Site can be a portfolio, landing page, publication, or business website without Commerce. Catalog and checkout tools can be added only where they are useful.
Continue
Create your workspace
Build the Site first. Add the rest when it becomes useful.
Start with a blank canvas or a prepared structure and keep every part editable.