What problem does it solve? Deploying a static website to Weegloo WebHosting involves several error-prone steps: choosing a unique subdomain, respecting file-count limits, packaging the build correctly, and wiring uploads to WebHosting resources through MCP tools. This Skill guides the AI through that entire flow and also covers editing a deployed page's SEO and share metadata without rebuilding or re-uploading. ## Core Features & Use Cases - Guided static deployment: Enforces static-export builds, the 300-file production cap (100 by default), and a ZIP with index.html at the root, uploaded via the CreateUpload MCP tool. - Autonomous subdomain selection: Picks a distinctive subdomain, verifies availability with CheckSubdomain, retries on collision, and reports the live *.weegloo.app URL. - Head metadata editing: Rewrites title, description, canonical, share image, favicon, and theme color through the pageMetas field of cma_UpdateOneWebHosting on MarketApp-installed hostings. - Use Case: After building a Next.js static export that integrates Weegloo content, deploy it end-to-end and later update the live site's SEO tags without a rebuild. ## Quick Start Deploy my static site build to Weegloo WebHosting and give me the live URL.
