seed-packs_skill

Overview

This skill creates and manages seed packs for PropertyWebBuilder, enabling fast setup of scenario-based seed data bundles for tenant websites. It provisions website settings, agency info, users, localized page content, property listings, taxonomy (field keys), navigation, and images. Use it to preview, apply, or reset realistic demo data for testing and demos.

How this skill works

The skill reads pack directories under db/seeds/packs and parses required pack.yml plus optional properties/, content/, translations/, images/, and field_keys.yml. Packs can inherit from a base pack; inheritance applies parent data first and lets child packs override values. Use the Pwb::SeedPack API or provided rake tasks to preview, apply with options (skip sections, dry run, verbose), list available packs, or reset and apply.

When to use it

• When provisioning a new tenant website with pre-configured demo data
• During demos or user acceptance testing to spin up realistic property scenarios
• When building or validating themes and page part templates with localized content
• To seed staging environments with repeatable, scenario-based datasets
• When creating reusable seed bundles for different markets or regions

Best practices

• Start packs by inheriting from base to reuse field_keys and navigation
• Keep one YAML file per property and include localized titles/descriptions for supported_locales
• Store images in the pack images/ folder and reference by filename only; fallback to db/seeds/images/
• Use price fields in cents (price_cents / monthly_price_cents) to avoid floating point issues
• Preview packs (dry run) before applying to production or shared databases

Example use cases

• Create a spain_luxury pack to demo multi-language listings, gallery images, and agency branding
• Build a small starter pack for a new client with agency contact, default theme, and a handful of properties
• Run rake pwb:seed_packs:preview[pack_name] during development to validate content and page parts
• Use apply_with_options to skip users when reusing properties across multiple websites
• Reset and apply a pack to clear test data and repopulate a clean scenario