A new store looks empty until it has products. Storefill fills it with the demo content your theme\nwas designed around, so you can see every section working and then swap the demo products for your\nown.<\/p>\n\n
Open Appearance \u2192 Import demo<\/strong>, check the requirements, and click Import demo content<\/strong>.\nStorefill adds:<\/p>\n\n Tick This is a public demo site<\/strong> (or use Demo packs are available for Twenty Twenty-Five (the default WordPress theme) and Unishop. Packs\nfor more themes are added to the demo library over time; Storefill finds them without an update.<\/p>\n\n A demo pack is a few JSON files (content, dashboard settings, Customizer settings and widgets)\nand a folder of photos in the public\ndemo-pack repository<\/a>. Its README documents the format.\nNothing in a pack is executed: Storefill only reads data and imports images through the WordPress\nmedia library. Pack text is treated as plain text (any HTML is stripped), and a pack can only change\na fixed list of store and site-identity settings, never accounts, roles, URLs or security settings.<\/p>\n\n Storefill downloads demo packs from the public demo-pack repository on GitHub, published with\nGitHub Pages at GitHub is operated by GitHub, Inc.:\nTerms of Service<\/a>,\nPrivacy Statement<\/a>.<\/p>\n\n To use another host, define No. Storefill only adds. When something with the same name already exists, it is used as it is and\nnever changed, and removal never deletes it.<\/p><\/dd>\n Appearance \u2192 Import demo, click Remove demo content<\/strong>, and confirm. Or run\n wp storefill remove .<\/p><\/dd>\n Yes, to match the demo. A block theme switches to the style variation its demo uses, if it names\none, and a classic theme gets the demo's Customizer settings and widgets. Storefill records your own\nstyles and settings first, and removing the demo puts them back exactly.<\/p><\/dd>\n Open Appearance \u2192 Import demo again and click Finish the import<\/strong>, or click Try again<\/strong> on the\nstep that stopped. Every step picks up where it left off without duplicating anything.<\/p><\/dd>\n It stays on your site. Storefill keeps its record of what it imported, so if you install it again\nyou can still remove the demo content. Remove the demo first if you want it gone.<\/p><\/dd>\n Packs that build a store need WooCommerce, and the import screen says so. Packs with only pages,\nposts and a menu work without it.<\/p><\/dd>\n\n<\/dl>\n\n\n\n
Safe on a store that already has content<\/h4>\n\n
\n
For theme demo sites<\/h4>\n\n
--demo-site<\/code> on the command line) to also set the site\ntitle and store address, switch store visibility to Live, turn on pretty permalinks, unpublish\nWordPress's sample post and page, and add a demo checkout: a payment method that takes no money and\ndelivery methods, so visitors can place a test order. Never use this option on a real store.<\/p>\n\nWP-CLI<\/h4>\n\n
wp storefill packs\nwp storefill import unishop --demo-site\nwp storefill status unishop\nwp storefill remove unishop --yes\n<\/code><\/pre>\n\nSupported themes<\/h4>\n\n
For theme developers<\/h4>\n\n
External services<\/h3>\n\n
som3669.github.io<\/code>.<\/p>\n\n\n
index.json<\/code>), the pack for your active theme\n(pack.json<\/code>) and that pack's photos.<\/li>\nSTOREFILL_SOURCE<\/code> in wp-config.php<\/code> with its base URL. To read packs\nfrom a folder on the server and make no requests at all, define STOREFILL_LOCAL_PACKS<\/code> with the\nfolder path.<\/p>\n\n\n\n
storefill-demo-content-importer<\/code> folder to \/wp-content\/plugins\/<\/code>\nand activate it on the Plugins<\/strong> screen.<\/li>\n\n
Will importing overwrite my products or pages?<\/h3><\/dt>\n
How do I remove the demo content?<\/h3><\/dt>\n
Will importing change my site's design?<\/h3><\/dt>\n
What happens if the import stops half way?<\/h3><\/dt>\n
What happens to the demo content if I uninstall Storefill?<\/h3><\/dt>\n
Does it work without WooCommerce?<\/h3><\/dt>\n
1.0.0<\/h4>\n\n
\n