docs: add Vendure custom fields blog by sauraww · Pull Request #1090 · juspay/superposition

sauraww · 2026-07-09T14:01:12Z

Vendure Blog

Added a Vendure custom fields blog post and a supporting animation that shows Vendure as the stored fallback source and Superposition as the condition + override layer used to produce the resolved storefront value.

Environment variable changes

None.

Pre-deployment activity

None.

Post-deployment activity

Verify the published docs page renders correctly.

API changes

None.

Possible Issues in the future

The animation is documentation-only, but layout may need minor tuning if the blog theme, typography, or embedded animation container dimensions change later.

semanticdiff-com · 2026-07-09T14:01:15Z

Review changes with

Changed Files

File	Status
docs/blog/2026-07-07-context-aware-vendure-custom-fields.md	Unsupported file format
docs/src/components/animations/VendureOwnershipFlow/index.tsx	0% smaller
docs/src/components/animations/VendureOwnershipFlow/styles.module.css	0% smaller

Copilot

Pull request overview

Adds a new documentation blog post explaining how to use Superposition to resolve context-aware Vendure custom fields, including a new animated diagram component to visually communicate the “Vendure stores fallback / Superposition resolves effective value” concept.

Changes:

Added a new blog post: “Context-aware Vendure custom fields with Superposition”.
Added a new VendureOwnershipFlow animation component (Anime.js-driven) used by the blog post.
Added a dedicated CSS module to style the new animation.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 4 comments.

File	Description
docs/src/components/animations/VendureOwnershipFlow/index.tsx	New animation component rendering and animating the Vendure→Superposition→storefront value flow.
docs/src/components/animations/VendureOwnershipFlow/styles.module.css	Styling for the new `VendureOwnershipFlow` animation layout and theme variants.
docs/blog/2026-07-07-context-aware-vendure-custom-fields.md	New blog post content embedding the animation via `AnimationSlide`.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Datron · 2026-07-16T07:31:35Z

+import AnimationSlide from '@site/src/components/AnimationSlide';
+import { VendureOwnershipFlow } from '@site/src/components/animations';
+


@sauraww you have to add an export in superposition/docs/src/components/animations/index.ts for VendureOwnershipFlow

+---
+slug: context-aware-vendure-custom-fields
+title: Context-aware Vendure custom fields with Superposition
+description: How Superposition adds channel aware resolved values to Vendure custom fields.


+
+## Why Superposition fits this problem
+
+Superposition starts from a simple idea: configuration should be resolved in context. Instead of spreading rules across environment variables, hardcoded conditionals , or one-off feature flags, it lets teams define typed defaults and resolve the right value for each context in a cascading way.


+        <div
+            ref={diagramRef}
+            className={styles.figure}
+            aria-label="Vendure catalog value, Superposition condition and override, and storefront result"
+        >


coderabbitai · 2026-07-09T14:05:36Z

Caution

Review failed

An error occurred during the review process. Please try again later.

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests
Commit unit tests in branch blog/vendure

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands.}

Datron

Can we include some sections about how the plugin was built with superposition and how others can do the same. It should include setup instructions with superposition_provider and code examples as well.

Datron · 2026-07-16T07:28:45Z

@@ -0,0 +1,150 @@
+---


@sauraww this file needs to be mdx for the animations to render

Datron · 2026-07-16T07:29:56Z

@@ -0,0 +1,150 @@
+---
+slug: context-aware-vendure-custom-fields
+title: Context-aware Vendure custom fields with Superposition


Suggested change

title: Context-aware Vendure custom fields with Superposition

title: Context Aware Custom Form Fields in Vendure

With superposition is implied, or it can be added to the URL slug for SEO

Datron · 2026-07-16T07:31:35Z

+import AnimationSlide from '@site/src/components/AnimationSlide';
+import { VendureOwnershipFlow } from '@site/src/components/animations';
+


@sauraww you have to add an export in superposition/docs/src/components/animations/index.ts for VendureOwnershipFlow

Datron · 2026-07-16T07:32:38Z

+Commerce data is rarely as global as it first appears.
+
+An online store often needs extra product information: a price band, a fulfilment promise, a merchandising label, or a marketplace-specific badge.
+In Vendure, custom fields are a natural place to store this data because they let teams extend products and product variants directly.


Vendure can link to Vendure's website. One thing that would be helpful would be to add a few lines about what Vendure is

Suggested change

In Vendure, custom fields are a natural place to store this data because they let teams extend products and product variants directly.

In [Vendure](https://vendure.io), custom fields are a natural place to store this data because they let teams extend products and product variants directly.

Datron · 2026-07-16T07:34:07Z

+An online store often needs extra product information: a price band, a fulfilment promise, a merchandising label, or a marketplace-specific badge.
+In Vendure, custom fields are a natural place to store this data because they let teams extend products and product variants directly.
+
+But some values are "default" values.


This seems out of place

Datron · 2026-07-16T07:35:30Z

+
+Vendure remains the system of record for the catalog. Superposition adds a runtime configuration layer that can resolve the right value for the current business context.
+
+<!-- truncate -->


truncate removes everything below this

Datron · 2026-07-16T07:36:38Z

+
+## Why Superposition fits this problem
+
+Superposition starts from a simple idea: configuration should be resolved in context. Instead of spreading rules across environment variables, hardcoded conditionals , or one-off feature flags, it lets teams define typed defaults and resolve the right value for each context in a cascading way.


Suggested change

Superposition starts from a simple idea: configuration should be resolved in context. Instead of spreading rules across environment variables, hardcoded conditionals , or one-off feature flags, it lets teams define typed defaults and resolve the right value for each context in a cascading way.

Superposition starts from a simple idea: configuration should be resolved with context. Instead of spreading rules across environment variables, hardcoded conditionals , or one-off feature flags, it lets teams define typed defaults and resolve the right value for each context in a cascading way.

Datron · 2026-07-16T07:37:12Z

+
+Superposition starts from a simple idea: configuration should be resolved in context. Instead of spreading rules across environment variables, hardcoded conditionals , or one-off feature flags, it lets teams define typed defaults and resolve the right value for each context in a cascading way.
+
+The important part is that the catalog does not need to become more complex just because the business rules become more specific. Vendure keeps the base product data understandable, and Superposition resolves the effective value at read time.


Suggested change

The important part is that the catalog does not need to become more complex just because the business rules become more specific. Vendure keeps the base product data understandable, and Superposition resolves the effective value at read time.

The important part is that the catalog does not need to become more complex just because the business rules become more specific. Vendure keeps the base product data understandable, and Superposition resolves the effective value at when required.

Is this better?

Datron · 2026-07-16T07:44:09Z

+
+Now suppose the same merchant wants a different bulk price for the B2B channel in INR. That value does not need to become another Vendure custom field. It can be stored as a contextual override in Superposition:
+
+```text


We should write this like cac toml, just to keep the format uniform across docs and blog

docs: add Vendure custom fields blog

a1010ca

Copilot AI review requested due to automatic review settings July 9, 2026 14:01

sauraww requested a review from a team as a code owner July 9, 2026 14:01

Copilot started reviewing on behalf of sauraww July 9, 2026 14:01 View session

Copilot AI reviewed Jul 9, 2026

View reviewed changes

Datron requested changes Jul 16, 2026

View reviewed changes

		import AnimationSlide from '@site/src/components/AnimationSlide';
		import { VendureOwnershipFlow } from '@site/src/components/animations';


		## Why Superposition fits this problem

		Superposition starts from a simple idea: configuration should be resolved in context. Instead of spreading rules across environment variables, hardcoded conditionals , or one-off feature flags, it lets teams define typed defaults and resolve the right value for each context in a cascading way.

	title: Context-aware Vendure custom fields with Superposition
	title: Context Aware Custom Form Fields in Vendure

	In Vendure, custom fields are a natural place to store this data because they let teams extend products and product variants directly.
	In [Vendure](https://vendure.io), custom fields are a natural place to store this data because they let teams extend products and product variants directly.


		Vendure remains the system of record for the catalog. Superposition adds a runtime configuration layer that can resolve the right value for the current business context.

		<!-- truncate -->


		Superposition starts from a simple idea: configuration should be resolved in context. Instead of spreading rules across environment variables, hardcoded conditionals , or one-off feature flags, it lets teams define typed defaults and resolve the right value for each context in a cascading way.

		The important part is that the catalog does not need to become more complex just because the business rules become more specific. Vendure keeps the base product data understandable, and Superposition resolves the effective value at read time.


		Now suppose the same merchant wants a different bulk price for the B2B channel in INR. That value does not need to become another Vendure custom field. It can be stored as a contextual override in Superposition:

		```text

Uh oh!

Conversation

sauraww commented Jul 9, 2026

Vendure Blog

Environment variable changes

Pre-deployment activity

Post-deployment activity

API changes

Possible Issues in the future

Uh oh!

semanticdiff-com Bot commented Jul 9, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Choose a reason for hiding this comment

Uh oh!

coderabbitai Bot commented Jul 9, 2026

Review failed

Uh oh!

Datron left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

semanticdiff-com Bot commented Jul 9, 2026 •

edited

Loading