webhome-homepage-builder

Package single-file HTML homepages with ES5 bootstrap for legacy Android WebViews.

1.1k|342|Updated May 22, 2026
One-click install
npx skills add https://github.com/fish2018/webhtv --skill webhome-homepage-builder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: webhome-homepage-builder
Source: https://github.com/fish2018/webhtv/tree/main/webhome-devkit/skills/webhome-homepage-builder
Command: npx skills add https://github.com/fish2018/webhtv --skill webhome-homepage-builder

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

WebHome Homepage Builder reduces the friction of creating WebHome homepages that work reliably in legacy Android WebViews by ensuring ES5 compatibility and providing a packaged, single-file HTML deliverable.

Core Features & Use Cases

  • ES5-compatible bootstrap with inline polyfills to render on older WebViews.
  • SDK integration patterns for App WebHome, including fm.req/fm.res and chrome management.
  • WAF/extension guidance to determine whether to fetch data directly or via a WebHome extension, with safe fallbacks.
  • Use Case: Create a Nostr/TMDB-friendly homepage that runs inside WebView and can be extended for TV remote UX.

Quick Start

Provide a target WebHome configuration and let the builder generate a compliant single-file HTML homepage.

Frequently Asked Questions about webhome-homepage-builder

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a single-file HTML homepage that works in legacy Android WebView?

To build a single-file HTML homepage for legacy Android WebView, you need an ES5-compatible bootstrap with inline polyfills. This ensures your WebHome page renders reliably on older WebViews by enforcing ES2017-or-lower JavaScript constraints.

Why does my WebHome homepage fail to load inside an older Android WebView?

Your WebHome homepage likely fails in older Android WebView due to unsupported modern JavaScript syntax. You must use an ES5 bootstrap with inline polyfills and restrict your code to ES2017-or-lower JavaScript to ensure legacy WebView compatibility.

How do I integrate the WebHome SDK for app configurations and chrome management?

WebHome SDK integration for app configurations involves implementing specific patterns like fm.req and fm.res alongside chrome management. These SDK integration patterns allow your single-file HTML homepage to communicate effectively within the App WebHome environment.

Do I need a WebHome extension when fetching data for a Nostr or TMDB homepage?

Whether you need a WebHome extension for fetching Nostr or TMDB data depends on WAF compatibility analysis. If direct data fetching is blocked, you should use a WebHome extension with safe fallbacks to ensure your homepage loads properly.

Can I create a TV remote-friendly homepage using WebHome?

Yes, you can create a TV remote-friendly homepage using WebHome by building a Nostr or TMDB-style single-file HTML page. This homepage runs inside WebView and can be specifically extended to support TV remote UX navigation.

What are the limitations of using ES5 bootstrap for WebHome homepage development?

The main limitation of using an ES5 bootstrap for WebHome homepage development is the strict ES2017-or-lower JavaScript requirement. This constraint prevents using modern ECMAScript features, requiring inline polyfills to maintain functionality in legacy Android WebViews.