Feat: dynamic 'unstable' body blocks #94
Open
+594
−15
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…new way of adding storyblock to spark.
lastHokage
changed the title
lastHokage
changed the title
…unstableBodyBloks and move it's location in the readme
…the --validationKeywords flag to add a sparkGenerateStoryblock to the gallery
adgad
reviewed
Sep 1, 2025
…of the build scripts
lastHokage
commented
Sep 9, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
First step:
Schema Driven Componentfor SparkThis PR is the first step toward using Content Tree as the source of truth for body block configuration in Spark.
You can read more background in our Reusable Components doc.
As our first example, we’ve added an
Galleryblock.It’s a simple, dynamic block with a few primitive fields (string, boolean) and one image node/type. More fields can be added later as needed — this is just a starting point to validate the pipeline end-to-end
Key changes
Add
--validationKeywordsflag in the build state to add thesparkGenerateStoryblock:truekey-value pair to the Gallery to be utilised in spark.Gallery→ first dynamic block wired into the Spark.