Limina by Runs Like New

Limina documentation

Set up with confidence.

Start with your products, connect their details, then check the purchase path on an unpublished draft.

This guide covers Limina 0.10.32–0.10.36. Earlier versions may have different controls; include your theme version when contacting support.

Start with an unpublished theme

  1. Keep a backup of the current theme and its saved settings.
  2. Choose a preset. All presets share the same product, search and cart behavior. Choose the visual direction that fits your store.
  3. Add your branding, navigation and collection links in the theme editor.
  4. Preview with your own products, variants and apps. Check a small screen, keyboard navigation and the full path from search to checkout before publishing.

Use real product information and approved policy text. Demo copy and sample guides are starting points, not evidence about your products.

Connect useful product information

Start with one product and one useful fact. Product facts are optional: shoppers can browse and buy before you configure them. A shared list is enough for products that use the same attributes.

Show your first fact without creating a field

  1. Open Theme settings → Product understanding. Set Product facts to Use shared mappings.
  2. For the first fact, enter label Brand, namespace product and key vendor. This reads the product's existing Shopify Vendor. Clear the labels and keys of unused rows.
  3. On the collection template, enable Show product details. Home-page Product collection sections have their own setting; enable it there too if you want facts on those cards. On the product template, include the Decision details block.
  4. Save the draft. Open the same product from its collection and confirm the brand matches Shopify. If Vendor is empty or unhelpful, use a verified specification instead.

Add a measurement or specification

Create or reuse a compatible product metafield in Settings → Metafields and metaobjects → Products, enable storefront access and enter its verified value on the product. A definition alone supplies no value. For example, an Overall height fact can use a Dimension field with namespace custom and key overall_height. Enter the same label, namespace and key in the next shared mapping, then save and preview.

When an option changes the fact, use a variant metafield with the same namespace/key and compatible type. Selected product details and comparison follow that override; collection cards retain the product-wide value. Cards show at most two populated product facts, so put the most useful ones first.

In the editor, expand Product facts setup beside the full product facts to check the active source, mapping problems and variant overrides. This guidance is hidden from shoppers. Check the exact path, field type, storefront access and saved value when a row is missing. Leave unknown values blank; comparison uses Not specified.

If the product or variant says No metafields pinned, use Metafields → View all before creating another definition. Existing values may simply be unpinned. Open the field name and View definition to check its type and access. Enter variant overrides on the variant itself. Shopify's Packed product size describes the shipping package, not the object's overall height or seat height.

Optional: use different facts for different product categories

Use product profiles only when categories need different attribute lists. Create these merchant-owned definitions in Settings → Metafields and metaobjects:

  1. A Product fact metaobject with two single-line text fields: label for the customer-facing name and source for an existing fact path, such as custom.overall_height.
  2. A Product fact profile metaobject with name (single-line text) and fact_fields (a list of metaobject references restricted to Product fact).
  3. A product metafield custom.fact_profile containing one metaobject reference restricted to Product fact profile.

Enable storefront access on both metaobject definitions and the product reference. If a definition uses Active/Draft publishing, its referenced entries must be Active. Enable translations when the store needs translated profile labels.

In Content → Metaobjects, create the fact entries and an ordered profile for each category. Assign the profile and verified fact values on each product. In Product understanding choose Use product profiles and set Profile metafield to custom.fact_profile. Up to 12 unique facts are supported; cards show the first two populated product facts. A missing profile falls back to shared mappings.

Preview one product from each category and a variant with a known override before expanding the catalog. Keep different meanings separate: overall height and seat height should not share a key. These fields remain in Shopify if you change themes; no companion app is required.

For guides, connect the appropriate guide page and check it with the selected product and option. Replace illustrative charts with verified measurements before relying on them for fit advice.

Put answers beside the purchase controls

Enable Show tax, shipping and returns information in Purchase controls. Add your actual shipping and refund policies in Shopify Settings → Policies, then open the resulting links from a product page. Non-shipping variants intentionally omit delivery information.

Use a product detail block for care, materials or other useful information. Add its Detail body or connect the appropriate rich-text field. Empty content stays hidden; a populated block with no heading uses Product details.

Shipping and gift thresholds are display messages. They do not create shipping rates or reward rules. Configure and verify the corresponding Shopify or app rule before enabling those messages.

Check apps on the actual product path

Add the app block to its intended template and test required selections, variant changes, cart updates and checkout. Compatibility depends on the app, its configuration and the task.

If an app requires the full product page, use the per-product Require the product page setting (custom.disable_quick_view). Confirm that the app preserves and enforces required values. An app appearing in the editor does not establish that it works throughout checkout.

Availability requests are contact messages, not automatic restock subscriptions. Use genuine, approved review content. Contact support with the app name and the exact failing task when you need help.

Update with a way back

  1. Record the current version and keep a backup of the theme, settings and custom code.
  2. Apply the update to an unpublished copy. Reconcile custom code and app changes before publishing.
  3. Check product facts, guides, variant selection, app fields, cart totals and checkout with representative products.
  4. Publish only after reviewing the draft. Retain the previous theme until the new version has passed your checks.

If something changes unexpectedly, record the previous and current versions, the affected draft and the first failing step. Contact support before repeatedly changing a draft whose save state is uncertain.

Common questions

Why is a product fact or care panel missing?

Check the saved value, field type, namespace/key and storefront access. For variant-specific information, check the selected variant. A detail block needs a nonempty body; an empty panel is intentionally hidden.

Does “Available” promise immediate shipping?

No. In 0.10.34 and later, the general availability label means the selected item can be purchased. Check the store’s delivery terms for dispatch timing. Tracked low-stock, backorder and sold-out notices remain separate.

Where should a shopper enter a discount code?

In Limina 0.10.30 and later, codes are entered and managed in Shopify checkout. Read Shopify’s eligibility message there. Cart item discounts appear beside products, and order deductions appear between subtotal and estimate.

What if search suggestions do not load?

Use the Search button for full results. Try a shorter product name or SKU, and check that the expected product is available to the Online Store and intended market.

What should I do about a gift recipient error?

Correct the field Shopify identifies and confirm the recipient and optional send date before resubmitting. When reporting a problem, include the theme version and redacted error text. Leave out private recipient details and redemption codes.

What if a required app field disappears?

Use the full product page and check the Require the product page setting for that product. Include the app, product URL, required field and the steps that lose its value in your support request.

How do I report a keyboard or accessibility problem?

Include the task, page, browser and input method. Note where focus moves, whether a control has a usable label and whether you can finish the task. Include an assistive technology name if relevant.

Still need help? Prepare a support request with the page, steps and visible result.