Skip to content

Commit 62e2de7

Browse files
committed
Fix incorrect image IA
1 parent 85b205f commit 62e2de7

2 files changed

Lines changed: 9 additions & 9 deletions

File tree

src/pages/blog/2026-02-12-better-together-design-systems-graphql-part-1.mdx

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ featured: true
88

99
By Amanda Olsen, Sam Combs
1010

11-
# Part 1: The GraphQL Double-Edged Sword
11+
## The GraphQL Double-Edged Sword
1212

1313
_A deep dive into how coupling design system components with GraphQL schema through collaborative cross-functional workshops can reduce sprawl, ensure consistency, and enhance productivity at both the UI and API layers._
1414

@@ -186,7 +186,9 @@ If we collaborate on data requirements early, we avoid fighting similar issues i
186186

187187
Let’s now try to imagine what the schema storming workshop would look like for the icon with text atomic component.
188188

189-
### Icon Component![][image9]
189+
### Icon Component
190+
191+
![][image9]
190192

191193
**The basic premise of the workshop is really simple.** Using a whiteboard tool like Miro, the relevant stakeholders need to to discuss the data expectations of the icon component and record them as sticky notes placed on the design system screen cap:
192194

src/pages/blog/2026-02-12-better-together-design-systems-graphql-part-2.mdx

Lines changed: 5 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -5,9 +5,7 @@ date: 2026-02-12
55
byline: Amanda Olsen, Sam Combs
66
---
77

8-
# Better Together: Cross-Functional Collaboration at the Intersection of Design Systems and GraphQL APIs \- Part 2 of 2
9-
10-
## A deep dive into how coupling design system components with GraphQL schema through collaborative cross-functional workshops can reduce sprawl, ensure consistency, and enhance productivity at both the UI and API layers.
8+
_A deep dive into how coupling design system components with GraphQL schema through collaborative cross-functional workshops can reduce sprawl, ensure consistency, and enhance productivity at both the UI and API layers._
119

1210
In part 1, we discussed the relevance of design system thinking in GraphQL schema design. And in fact, we attached GraphQL fragments to our atomic components. These fragment shapes were created in cross-functional workshops, ensuring the result would be sufficient for practically any future use case.
1311

@@ -96,7 +94,9 @@ These groupings map 1:1 to GraphQL Type Definitions. Being able to link an on-sc
9694

9795
Let’s update our SDL and our client query to see how the groupings apply. Note the use of square brackets “\[ \]” to denote lists:
9896

99-
## ![][image23]Optionality, Nullability, and Error State Discussion
97+
![][image23]
98+
99+
## Optionality, Nullability, and Error State Discussion
100100

101101
Next up, we need to:
102102

@@ -240,9 +240,7 @@ Senior Full-Stack Engineer
240240

241241
Sam was exposed to computers at a very young age, sparking a passion that he can now proudly call his livelihood. He cut his teeth as a full stack developer building organic farm management solutions which gave him experience in working with large data sets and creating UIs for non-technical users. Introduced to GraphQL in 2018, Sam currently works at Xolvio, the official Apollo GraphQL professional services partner, working with large enterprises like Wayfair, Ford Credit, and more.
242242

243-
Unsure if this image should be used at all or where.
244-
245-
# ![][image36]
243+
![][image36]
246244

247245
[image17]: https://placehold.co/1200x700?text=image17
248246
[image18]: https://placehold.co/1200x700?text=image18

0 commit comments

Comments
 (0)