Directus as headless CMS: some questions to experienced users
Hi Cloudron+Directus community,
I am currently planning a web project with a JAMStack setup. Basically: Directus → React → Gatsby → Nginx hosting of the static site.
But I am not entirely sure what Directus is capable of as a hCMS:
- Is it possible to set up a collection which is defining different sections (components) which can be used in a repeater within other collections such as pages, articles, products, etc. – each with independently filled fields. I am aiming for a structure where components are defined once and not redundant for each page article or product collection.
- Is there a solution for relational links within a WYSIWYG/RTE field? What I mean: Editors should be able to link from the RTE to another page, best case with relation to find a page by title, keeping the language relation and keeping the correct URL even though the target page changes the slug.
There might be some extensions I guess. But for now I am very grateful for anyone who can tell me if this is possible in general and with which efforts.
Knowing that the alternatives are hCMS like Contentful or Storyblok we prefer Directus by far.
If anyone having experiences with setting up such deployment pipelines for the Directus/React/Gatsby Stack it would be great if we could talk.
I am looking for someone who is an experienced DevOps engineer working on freelance basis or a company to support us setting up the entire architecture and who is willing to also further maintain it.
Thanks for any help here!
@dev-cb I know you've already swapped, but wish I had seen this a few days ago.
I run a slightly older version of Directus locally, but at least in it...
(1) Repeaters can't reference collections. If you want to reference other collections, you have to create a relationship (like Many-to-Many). Which is not quite as convenient, but a bit more powerful.
(2) As far as I know, nope. For this, you have to manipulate it in Gatsby. I do my manipulation in Elder.JS.