questpie-admin/blocks

Name: questpie-admin/blocks
Availability: InStock
Author: QUESTPIE

Define reusable server-side blocks with fields and admin metadata for QUESTPIE page builders.

5|3|Updated Dec 15, 2025

Search Tags:#content management #frontend development #blocks #reusable components #page builder #questpie

Ready to run

npx skills add https://github.com/questpie/questpie --skill questpie-admin-blocks

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: questpie-admin/blocks
Source: https://github.com/questpie/questpie/tree/main/packages/admin/skills/questpie-admin/blocks
Command: npx skills add https://github.com/questpie/questpie --skill questpie-admin-blocks

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill simplifies the creation of dynamic, reusable content components for web pages and applications, enabling faster development and consistent design.

Core Features & Use Cases

Reusable Content Blocks: Define content sections (like hero banners, feature lists, testimonials) once and reuse them across multiple pages.
Page Builder Integration: Provides the backend definition for a visual page builder interface.
Use Case: A marketing team can use this Skill to create a library of approved content blocks (e.g., a "Call to Action" block, a "Product Feature" block) that content editors can then assemble into new landing pages without needing developer intervention.

Quick Start

Define a new block named 'hero' with a 'title' and 'backgroundImage' field using the questpie-admin/blocks skill.

Frequently Asked Questions about questpie-admin/blocks

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

FAQPage Schema

How do I build dynamic pages with reusable content blocks?▼

You can build dynamic pages by defining reusable content blocks with specific fields and admin metadata, then assembling them via a page builder interface. This enables modular content creation without requiring developer intervention for each new page.

What is the best way to let non-developers assemble landing pages from approved components?▼

The best way is to define server-side content blocks with fields for elements like hero banners or calls to action. Content editors can then visually assemble these predefined blocks into new landing pages independently.

Can I define custom fields and admin metadata for reusable frontend components?▼

Yes, you can define custom fields and admin metadata for reusable frontend components. Server-side block definitions support structured fields like titles and background images, which integrate directly with client-side rendering components.

Does this page builder approach support declarative prefetching for related block data?▼

Yes, the page builder approach supports declarative prefetching for related data within content blocks. This ensures that client-side rendering components have the necessary related data available without manual fetching logic.

How do reusable content blocks work within a frontend development workflow?▼

Reusable content blocks work by separating server-side definitions containing fields and metadata from client-side rendering components. Developers define the block structure once, and content editors reuse it across multiple pages to maintain consistent design.

Are there limitations when creating modular content sections for a visual page builder?▼

Modular content sections are tied to the QUESTPIE framework's page builder integration, meaning blocks must be defined with compatible server-side definitions and admin metadata to function correctly within the supported visual editing interface.