diff --git a/rfcs/084-shopify-integration-strategies/README.md b/rfcs/084-shopify-integration-strategies/README.md
new file mode 100644
index 00000000..db6c82eb
--- /dev/null
+++ b/rfcs/084-shopify-integration-strategies/README.md
@@ -0,0 +1,302 @@
+# Shopify Integration Approaches for Wellcome Collection
+
+**Research Focus:** Evaluating different approaches for integrating Shopify with wellcomecollection.org
+
+## Summary
+
+This research outlines five approaches for integrating Shopify with the Wellcome Collection website, ranging from simple embedded solutions to fully headless implementations.
+
+## Current Technical Context
+
+The Wellcome Collection website is built as a Next.js monorepo with:
+- React-based frontend (Next.js)
+- Styled-components for styling
+- Prismic CMS for content management
+- Yarn workspaces architecture
+- Strong emphasis on performance optimisation and accessibility
+
+## Initial Requirements
+At first the only things to be sold via the shop will be exclusive Wellcome Collection ranges (wellcome collection books, wellcome collection toys, and exhibition ranges). This may change in the future.
+
+## Integration Approaches
+
+### Option 1: Shopify Buy Button
+
+**Description:** Embeds Shopify products directly into existing pages using JavaScript widgets.
+
+**Implementation:**
+- Add Shopify-generated code snippets to relevant pages
+- Products display in pop-up or redirect to Shopify checkout
+- Minimal development effort required
+
+**Advantages:**
+- Quick implementation (hours to days)
+- Low cost
+- No complex integration required
+- Shopify handles all checkout and payment processing
+- Suitable for testing e-commerce viability
+
+**Disadvantages:**
+- Limited design customisation
+- Checkout redirects to Shopify domain breaking brand continuity
+- Inconsistent user experience
+- Limited control over customer journey
+- Not suitable for substantial product catalogues
+
+**Best For:** Testing e-commerce concept, limited product offerings, content-heavy sites with occasional sales
+
+**Sources:**
+- [Shopify Buy Button](https://www.shopify.com/buy-button)
+- [Buy Button FAQ](https://help.shopify.com/en/manual/online-sales-channels/buy-button/faq)
+
+---
+
+### Option 2: Embedded Shopify Storefront
+
+**Description:** Creates a separate Shopify store accessible via subdomain or integrated section whilst maintaining primary site navigation.
+
+**Implementation:**
+- Standard Shopify theme on `shop.wellcomecollection.org` or `/shop` path
+- Create custom Liquid theme to match brand
+- Link from main site to shop
+
+**Advantages:**
+- Full Shopify feature set available
+- Extensive app ecosystem
+- Proven reliability for e-commerce operations
+- Professional checkout experience
+- Comprehensive analytics and reporting
+- Easy to hand over management to a different team if needed
+- There's only one place to search (no confusion around whether you're searching the shop or the main site)
+
+
+**Disadvantages:**
+- Inconsistent user experience between main site and shop (although this is a common pattern in the sector and unlikely to cause significant issues)
+- Duplicate navigation/header/footer/component maintenance
+- Users perceive being taken away from main site
+- SEO considerations for separate domain/path
+- Theme customisation limited by Liquid templating
+
+**Best For:** Organisations prioritising speed to market, those without significant development resources, when complete feature parity with Shopify ecosystem is required
+
+
+
+There is a skeleton Liquid theme available [here](./skeleton-theme) showing how products and categories could be grouped and displayed, with a simple cart and checkout flow (video above). We would have to write seperate css to style a theme created in this way, but we should be able to import and use the [existing design system](https://github.com/wellcometrust/wellcome-design-system/tree/main) for spacing, typography, grid, and colour variables to help ensure consistency at least.
+
+Probably the biggest advantage of this approach is that it would be the easiest to hand over to a different team to manage in the future, as it would be a more standard standalone Shopify implementation and as such wouldn't need to be unpicked from our existing codebase.
+
+---
+
+### Option 3: Headless Commerce with Shopify Storefront API
+
+**Description:** Uses Shopify as backend commerce engine whilst building custom frontend using Storefront API (GraphQL).
+
+**Implementation:**
+- Shopify manages products, inventory, orders, customers
+- Custom React components in Next.js fetch data via the Storefront API
+- Checkout can be embedded or redirect to Shopify
+- Full control over frontend presentation
+
+**Technical Architecture:**
+```
+Next.js Frontend (wellcomecollection.org)
+ ↓
+ Storefront API (GraphQL)
+ ↓
+Shopify Backend (products, orders, inventory)
+ ↓
+ Shopify Checkout
+```
+
+**Key Implementation Details:**
+- GraphQL API with no request-count rate limits
+- Versioned API updated quarterly
+- Public and private access tokens via Headless channel
+
+**Advantages:**
+- Complete design control and brand consistency
+- Seamless user experience within existing site
+- Leverage existing Next.js expertise
+- Optimised performance (fetch only required data)
+- Scalable architecture
+- Aligns with existing strategies (composable, API-first)
+- Lends itself to iteration
+
+**Disadvantages:**
+- Higher development cost
+- Requires Next.js knowledge
+- Ongoing maintenance responsibility
+- Checkout still redirects to Shopify domain
+- More complex than out-of-box solutions
+- Potentially complicates site-search and user expectations
+
+Robert put forward a relatively major concern with this approach:
+
+> I'm concerned the recommended approach will add a maintenance overhead that won't be sustainable, and might cause issues in the future if we want to resource changes to the shop outside of the experience team. Adding the shop also adds a slew of product concerns that will come with requirements and requests for changes - if we couple these to our development process tightly I think we risk issues with delivery
+
+If we were to go with this approach, we should ensure:
+1. We have full control of product direction
+2. The experience team will be resourced indefinitely to take on the extra maintenance burden of the new product area
+3. We should consider whether it belongs as its own service rather than being built directly into the content app
+
+It is still unknown if we want to allow for user accounts, or always use guest checkout. Maintaining user accounts ourselves would add a significant amount of complexity and if they were required, we might want to consider using Shopify's customer accounts functionality, which might add some friction to the ux but would be a lot easier to implement and maintain than building our own.
+
+**Development Approach:**
+1. Set up Shopify Headless channel and generate API tokens
+2. Configure environment variables in Next.js
+3. Create GraphQL queries for products, collections, cart
+4. Build React components for product display, cart, checkout(?) flow
+5. Implement state management for cart functionality
+6. Integrate with existing design system/component library
+7. Add analytics and tracking
+
+**Best For:** Organisations with development resources, those requiring brand consistency, sites with existing sophisticated frontend, when user experience is paramount
+
+**Sources:**
+- [Shopify Headless Commerce](https://www.shopify.com/plus/solutions/headless-commerce)
+- [Building with the Storefront API](https://shopify.dev/docs/storefronts/headless/building-with-the-storefront-api)
+- [Storefront API Reference](https://shopify.dev/docs/api/storefront/latest)
+- [Building Ecommerce Sites with Next.js and Shopify](https://vercel.com/kb/guide/building-ecommerce-sites-with-next-js-and-shopify)
+- [Good and Bad of Headless Commerce with Shopify](https://www.plytix.com/blog/headless-commerce-with-shopify)
+- [Headless Commerce vs Traditional Commerce](https://www.shopify.com/enterprise/blog/headless-commerce-vs-traditional-commerce)
+
+---
+
+### Option 4: Hydrogen Framework (Shopify's React/Remix Framework)
+
+**Description:** Shopify's official React-based framework specifically built for headless commerce.
+
+**Implementation:**
+- Use Hydrogen as frontend framework instead of custom Next.js integration
+- Pre-built commerce components and hooks
+- Oxygen hosting for global deployment (free with Shopify)
+- Optimised for Shopify's commerce patterns
+
+**Advantages:**
+- Accelerated development with pre-built components
+- Built-in Shopify integrations and best practices
+- Optimised for performance at global scale
+- Regular updates from Shopify
+- Shopify-specific tooling and conventions
+- Free global hosting with Oxygen
+
+**Disadvantages:**
+- Introduces different framework from existing Next.js
+- Would require site migration or dual-framework approach
+- Less flexibility for non-commerce features
+- Smaller community compared to Next.js
+- Oxygen deployment limitations (one storefront per store, limited logging)
+- Learning curve for team familiar with Next.js
+- Not suitable if requiring extensive customisation beyond e-commerce
+
+**Best For:** New projects, shops with minimal non-commerce content, teams starting fresh without existing frontend constraints
+
+**Sources:**
+- [Hydrogen: Shopify's headless commerce framework](https://hydrogen.shopify.dev/)
+- [Shopify Headless Commerce: A Complete Guide](https://litextension.com/blog/shopify-headless/)
+
+---
+
+### Option 5: Shopify Plus with Custom Checkout Extensibility
+
+**Description:** Shopify Plus plan with extensive checkout customisation using Checkout UI Extensions.
+
+**Implementation:**
+- Shopify Plus subscription (£££)
+- Custom checkout steps using UI Extensions API
+- Full Shopify feature set with enhanced customisation
+- Can maintain brand experience through checkout
+
+**Technical Details:**
+- Checkout UI Extensions
+- Custom functionality for product offers, fields, loyalty programmes
+- Extensions available for information, shipping, payment, order summary steps
+
+**Advantages:**
+- Branded checkout experience on Shopify domain
+- Access to Plus-only features (scripts, automation, wholesale)
+- Dedicated support
+- Can customise checkout with UI extensions
+
+**Disadvantages:**
+- Significant ongoing cost
+- May be over-specification for smaller operations
+
+**Best For:** Large-scale operations, high-volume sales, organisations requiring extensive Shopify app ecosystem, wholesale capabilities
+
+**Sources:**
+- [Checkout UI Extensions](https://shopify.dev/docs/api/checkout-ui-extensions/latest)
+
+---
+
+## Key Decision Criteria
+
+### Technical Considerations
+- How easy is it to back out/hand over?
+ - Option 2 would be relatively easy to hand over, as it is a standalone Shopify implementation
+ - Option 3 would be harder to hand over, as it would be tightly integrated with our existing codebase and would require significant unpicking to hand over to a different team.
+
+**Existing Architecture:**
+- Current Next.js implementation/(and expertise) favours headless approach
+- Styled-components design system can extend to commerce components
+- TypeScript throughout supports type-safe API integration
+
+### User Experience Priorities
+
+**Brand Consistency:**
+- Requires cohesive UX/UI
+- Headless approaches provide seamless integration
+- Checkout on Shopify domain is probably acceptable – it is a familiar/trustworthy user flow. Fully customising checkout ourselves (including managing credit card information, shipping, and taxes etc.) feels like it would probably be building in a wealth of future pain
+
+**Customer Journey:**
+- Content-to-commerce flow should be natural
+- Integration with existing site navigation and search
+
+### Implementation Roadmap for option 3
+
+#### Phase 1: Foundation
+- Set up Shopify backend
+- Configure Headless channel and API access
+- Create product catalogue structure
+- Design commerce component architecture
+
+#### Phase 2: Core Features
+- Product listing pages
+- Product detail pages
+- Shopping cart functionality
+- Checkout flow (redirect to Shopify)
+- Basic search and filtering
+
+#### Phase 3: Enhanced Experience
+- Content-product associations in Prismic
+- Advanced search and recommendations
+- Analytics integration
+
+#### Phase 4: Optimisation
+- Performance tuning
+- A/B testing
+- User feedback incorporation
+- Additional features based on usage patterns
+
+
+## Technical Implementation Notes
+
+- It isn’t obvious how to redirect back to wc.org after checkout clicking the ‘Continue shopping’ page, with several unanswered questions from community boards [1](https://community.shopify.com/t/change-continue-shopping-url-on-thank-you-page-headless/403380), [2](https://community.shopify.com/t/change-continue-shopping-url-on-thank-you-page-headless/403380), [3](https://community.shopify.dev/t/headless-shopify-continue-shopping-button-redirects-to-wrong-domain-after-checkout/18950), [4](https://community.shopify.com/t/headless-redirect-after-checkout/397344/3), [5](https://www.reddit.com/r/shopify/comments/1iz2fa0/headless_redirect_after_checkout/), but I made a minimal Liquid theme that just redirects client-side and this seems to work fine.
+- I haven’t looked much into [integration with existing Prismic content](https://prismic.io/docs/fields/integration#sync-products-from-a-shopify-store) beyond knowing that it exists.
+- I think/presume additional cookies should be added to the functional/required list in order for cart/checkout functionality to work.
+- I haven't looked at any Shopify-specific analytics/tracking options.
+
+## Proof of Concept
+The [shopify branch](https://github.com/wellcomecollection/wellcomecollection.org/compare/shopify) of the wc.org monorepo contains a minimal proof of concept implementation of Option 3 (Headless Commerce with Storefront API). It demonstrates fetching products and variants from Shopify and displaying them on a Next.js page, with a cart and checkout flow.
+
+
+
+**Sources:**
+- [GraphQL Storefront API](https://shopify.dev/docs/api/storefront/latest)
+- [GraphiQL explorer](https://shopify.dev/docs/api/usage/api-exploration/admin-graphiql-explorer)
+- [Getting Started with GraphQL](https://www.shopify.com/partners/blog/getting-started-with-graphql)
+- [Working with Shopify Storefront API](https://medium.com/@sandeeppangeni17/working-with-shopify-storefront-api-graphql-javascript-e02fb89eb682)
+
+---
diff --git a/rfcs/084-shopify-integration-strategies/skeleton-theme/.shopifyignore b/rfcs/084-shopify-integration-strategies/skeleton-theme/.shopifyignore
new file mode 100644
index 00000000..59a11a13
--- /dev/null
+++ b/rfcs/084-shopify-integration-strategies/skeleton-theme/.shopifyignore
@@ -0,0 +1,13 @@
+# This file contains a list of files that will be excluded from Shopify CLI
+# operations such as push, pull, dev, etc.
+#
+# Examples:
+#
+# Ignore a specific file:
+# templates/product.json
+#
+# Ignore templates with a wildcard pattern:
+# templates/*.json
+#
+# Ignore templates and sections with a regular expression:
+# /(templates|sections)/.*\.json/
diff --git a/rfcs/084-shopify-integration-strategies/skeleton-theme/.theme-check.yml b/rfcs/084-shopify-integration-strategies/skeleton-theme/.theme-check.yml
new file mode 100644
index 00000000..f9576a6c
--- /dev/null
+++ b/rfcs/084-shopify-integration-strategies/skeleton-theme/.theme-check.yml
@@ -0,0 +1 @@
+extends: theme-check:recommended
diff --git a/rfcs/084-shopify-integration-strategies/skeleton-theme/LICENSE.md b/rfcs/084-shopify-integration-strategies/skeleton-theme/LICENSE.md
new file mode 100644
index 00000000..611b31d0
--- /dev/null
+++ b/rfcs/084-shopify-integration-strategies/skeleton-theme/LICENSE.md
@@ -0,0 +1,9 @@
+Copyright (c) 2018-present Shopify Inc.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, sell and/or create derivative works of the Software or any part thereof, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
+
+The rights granted above may only be exercised to develop themes that integrate or interoperate with Shopify software or services, and, if applicable, to distribute, offer for sale or otherwise make available any such themes via the Shopify Theme Store. All other uses of the Software are strictly prohibited.
+
+The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
diff --git a/rfcs/084-shopify-integration-strategies/skeleton-theme/README.md b/rfcs/084-shopify-integration-strategies/skeleton-theme/README.md
new file mode 100644
index 00000000..eaf59b2c
--- /dev/null
+++ b/rfcs/084-shopify-integration-strategies/skeleton-theme/README.md
@@ -0,0 +1,160 @@
+
+
+
+
+ Shopify Skeleton Theme
+
+
+A minimal, carefully structured Shopify theme designed to help you quickly get started. Designed with modularity, maintainability, and Shopify's best practices in mind.
+
+
+
+
+
+
+## Getting started
+
+### Prerequisites
+
+Before starting, ensure you have the latest Shopify CLI installed:
+
+- [Shopify CLI](https://shopify.dev/docs/api/shopify-cli) – helps you download, upload, preview themes, and streamline your workflows
+
+If you use VS Code:
+
+- [Shopify Liquid VS Code Extension](https://shopify.dev/docs/storefronts/themes/tools/shopify-liquid-vscode) – provides syntax highlighting, linting, inline documentation, and auto-completion specifically designed for Liquid templates
+
+### Clone
+
+Clone this repository using Git or Shopify CLI:
+
+```bash
+git clone git@github.com:Shopify/skeleton-theme.git
+# or
+shopify theme init
+```
+
+### Preview
+
+Preview this theme using Shopify CLI:
+
+```bash
+shopify theme dev
+```
+
+## Theme architecture
+
+```bash
+.
+├── assets # Stores static assets (CSS, JS, images, fonts, etc.)
+├── blocks # Reusable, nestable, customizable UI components
+├── config # Global theme settings and customization options
+├── layout # Top-level wrappers for pages (layout templates)
+├── locales # Translation files for theme internationalization
+├── sections # Modular full-width page components
+├── snippets # Reusable Liquid code or HTML fragments
+└── templates # Templates combining sections to define page structures
+```
+
+To learn more, refer to the [theme architecture documentation](https://shopify.dev/docs/storefronts/themes/architecture).
+
+### Templates
+
+[Templates](https://shopify.dev/docs/storefronts/themes/architecture/templates#template-types) control what's rendered on each type of page in a theme.
+
+The Skeleton Theme scaffolds [JSON templates](https://shopify.dev/docs/storefronts/themes/architecture/templates/json-templates) to make it easy for merchants to customize their store.
+
+None of the template types are required, and not all of them are included in the Skeleton Theme. Refer to the [template types reference](https://shopify.dev/docs/storefronts/themes/architecture/templates#template-types) for a full list.
+
+### Sections
+
+[Sections](https://shopify.dev/docs/storefronts/themes/architecture/sections) are Liquid files that allow you to create reusable modules of content that can be customized by merchants. They can also include blocks which allow merchants to add, remove, and reorder content within a section.
+
+Sections are made customizable by including a `{% schema %}` in the body. For more information, refer to the [section schema documentation](https://shopify.dev/docs/storefronts/themes/architecture/sections/section-schema).
+
+### Blocks
+
+[Blocks](https://shopify.dev/docs/storefronts/themes/architecture/blocks) let developers create flexible layouts by breaking down sections into smaller, reusable pieces of Liquid. Each block has its own set of settings, and can be added, removed, and reordered within a section.
+
+Blocks are made customizable by including a `{% schema %}` in the body. For more information, refer to the [block schema documentation](https://shopify.dev/docs/storefronts/themes/architecture/blocks/theme-blocks/schema).
+
+## Schemas
+
+When developing components defined by schema settings, we recommend these guidelines to simplify your code:
+
+- **Single property settings**: For settings that correspond to a single CSS property, use CSS variables:
+
+ ```liquid
+
+
+
+ {{ '404.back_to_shopping' | t }}
+
+
+{% schema %}
+{
+ "name": "t:general.404",
+ "settings": []
+}
+{% endschema %}
diff --git a/rfcs/084-shopify-integration-strategies/skeleton-theme/sections/article.liquid b/rfcs/084-shopify-integration-strategies/skeleton-theme/sections/article.liquid
new file mode 100644
index 00000000..146acd1e
--- /dev/null
+++ b/rfcs/084-shopify-integration-strategies/skeleton-theme/sections/article.liquid
@@ -0,0 +1,68 @@
+{% comment %}
+ This section is used in the article template to render the article page, which
+ displays the full content of the blog post and can optionally include a
+ comments section for customers (not shown in this example).
+
+ https://shopify.dev/docs/storefronts/themes/architecture/templates/article
+{% endcomment %}
+
+{% if article.image %}
+ {{ article.image | image_url: width: 1000 | image_tag }}
+{% endif %}
+
+
+
+
+
diff --git a/rfcs/084-shopify-integration-strategies/skeleton-theme/templates/index.json b/rfcs/084-shopify-integration-strategies/skeleton-theme/templates/index.json
new file mode 100644
index 00000000..b03e3a86
--- /dev/null
+++ b/rfcs/084-shopify-integration-strategies/skeleton-theme/templates/index.json
@@ -0,0 +1,22 @@
+/*
+ * ------------------------------------------------------------
+ * IMPORTANT: The contents of this file are auto-generated.
+ *
+ * This file may be updated by the Shopify admin theme editor
+ * or related systems. Please exercise caution as any changes
+ * made to this file may be overwritten.
+ * ------------------------------------------------------------
+ */
+{
+ "sections": {
+ "main": {
+ "type": "hello-world",
+ "settings": {
+ "featured_collection": "featured"
+ }
+ }
+ },
+ "order": [
+ "main"
+ ]
+}
diff --git a/rfcs/084-shopify-integration-strategies/skeleton-theme/templates/list-collections.json b/rfcs/084-shopify-integration-strategies/skeleton-theme/templates/list-collections.json
new file mode 100644
index 00000000..30984287
--- /dev/null
+++ b/rfcs/084-shopify-integration-strategies/skeleton-theme/templates/list-collections.json
@@ -0,0 +1,20 @@
+/*
+ * ------------------------------------------------------------
+ * IMPORTANT: The contents of this file are auto-generated.
+ *
+ * This file may be updated by the Shopify admin theme editor
+ * or related systems. Please exercise caution as any changes
+ * made to this file may be overwritten.
+ * ------------------------------------------------------------
+ */
+{
+ "sections": {
+ "main": {
+ "type": "collections",
+ "settings": {}
+ }
+ },
+ "order": [
+ "main"
+ ]
+}
diff --git a/rfcs/084-shopify-integration-strategies/skeleton-theme/templates/page.json b/rfcs/084-shopify-integration-strategies/skeleton-theme/templates/page.json
new file mode 100644
index 00000000..36d23000
--- /dev/null
+++ b/rfcs/084-shopify-integration-strategies/skeleton-theme/templates/page.json
@@ -0,0 +1,20 @@
+/*
+ * ------------------------------------------------------------
+ * IMPORTANT: The contents of this file are auto-generated.
+ *
+ * This file may be updated by the Shopify admin theme editor
+ * or related systems. Please exercise caution as any changes
+ * made to this file may be overwritten.
+ * ------------------------------------------------------------
+ */
+{
+ "sections": {
+ "main": {
+ "type": "page",
+ "settings": {}
+ }
+ },
+ "order": [
+ "main"
+ ]
+}
diff --git a/rfcs/084-shopify-integration-strategies/skeleton-theme/templates/password.json b/rfcs/084-shopify-integration-strategies/skeleton-theme/templates/password.json
new file mode 100644
index 00000000..030b7259
--- /dev/null
+++ b/rfcs/084-shopify-integration-strategies/skeleton-theme/templates/password.json
@@ -0,0 +1,21 @@
+/*
+ * ------------------------------------------------------------
+ * IMPORTANT: The contents of this file are auto-generated.
+ *
+ * This file may be updated by the Shopify admin theme editor
+ * or related systems. Please exercise caution as any changes
+ * made to this file may be overwritten.
+ * ------------------------------------------------------------
+ */
+{
+ "layout": "password",
+ "sections": {
+ "main": {
+ "type": "password",
+ "settings": {}
+ }
+ },
+ "order": [
+ "main"
+ ]
+}
diff --git a/rfcs/084-shopify-integration-strategies/skeleton-theme/templates/product.json b/rfcs/084-shopify-integration-strategies/skeleton-theme/templates/product.json
new file mode 100644
index 00000000..8329ddc6
--- /dev/null
+++ b/rfcs/084-shopify-integration-strategies/skeleton-theme/templates/product.json
@@ -0,0 +1,20 @@
+/*
+ * ------------------------------------------------------------
+ * IMPORTANT: The contents of this file are auto-generated.
+ *
+ * This file may be updated by the Shopify admin theme editor
+ * or related systems. Please exercise caution as any changes
+ * made to this file may be overwritten.
+ * ------------------------------------------------------------
+ */
+{
+ "sections": {
+ "main": {
+ "type": "product",
+ "settings": {}
+ }
+ },
+ "order": [
+ "main"
+ ]
+}
diff --git a/rfcs/084-shopify-integration-strategies/skeleton-theme/templates/search.json b/rfcs/084-shopify-integration-strategies/skeleton-theme/templates/search.json
new file mode 100644
index 00000000..8c540c54
--- /dev/null
+++ b/rfcs/084-shopify-integration-strategies/skeleton-theme/templates/search.json
@@ -0,0 +1,20 @@
+/*
+ * ------------------------------------------------------------
+ * IMPORTANT: The contents of this file are auto-generated.
+ *
+ * This file may be updated by the Shopify admin theme editor
+ * or related systems. Please exercise caution as any changes
+ * made to this file may be overwritten.
+ * ------------------------------------------------------------
+ */
+{
+ "sections": {
+ "main": {
+ "type": "search",
+ "settings": {}
+ }
+ },
+ "order": [
+ "main"
+ ]
+}
+ 
+
+ {% endif %}
+ 
+ {% endif %}
+
{{ comment.author }}
++ {{- comment.created_at | time_tag: format: 'date' -}} +
+{{ comment.content }}
+