Directus Basics Part 2 — Understanding Relationships (M2O, O2M, M2M) This is part two of our Dire...Directus Basics Part 2 — Understanding Relationships (M2O, O2M, M2M) This is part two of our Dire...
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Directus Basics Part 2 — Understanding Relationships (M2O, O2M, M2M)
This is part two of our Directus Basics series. In [part one](https://www.youtube.com/watch?v=tJGuxqhv2SY&t=11s), we set up a Directus instance and created our first collection. Today we're covering one of the most powerful features Directus offers: **relationships** between collections.
By the end of this article, you'll understand three core relationship types — Many to One (M2O), One to Many (O2M), and Many to Many (M2M). There's a fourth type, Many to Any (M2A), which we'll cover in a future post.
Relationships are always the part that trips people up when they're new to headless CMS work. What was the project that actually pushed you to map out M2O, O2M, and M2M properly instead of winging it?
It's not just one project in particular, but since I started using Directus (https://northernrangedigital.com ), of all the features, relationships, was a bit tricky for me especially when I wanted to share data across multiple collections. I thought to myself, someone who is...
Relationships are always the part that trips people up when they're new to headless CMS work. What was the project that actually pushed you to map out M2O, O2M, and M2M properly instead of winging it?
The bottle tags next to the meeting player are the part that sells it. You see how the pieces relate before anyone explains a feature. That is the hard part of a SaaS template: the cards still have to do that job after someone swaps in their own product.
BOSAK; Music App Exploration 🎵
Refining the home experience with a focus on content discovery, clean UI, and natural interactions.
What are your thought?
#figma #figmadesign #uiux
Goal: sell a Hosokawa Alpine industrial granulation line to buyers abroad.
What was built: a buyer database by segment (manufacturers, dealers, OEM); a separate email for each segment in local languages (EN, PL and others), no templates; a touch sequence: first email → reminder → final; stop list and bounce tracking; a log of all replies.
Result: 1,997 emails, 91% delivered, 68 replies from potential buyers.