Contact persons best practice?

Using Neos & Flow
1

Hey,
i would like to have an option to edit contact persons in a central place, referencing them in other modules.

My idea is to create a document type for that, but is this the best practice to do it? Cause if i create a document type they get a url and document “status” what i dont want.

But best case they are selectable inside the document tree.

Any suggestions on how to implement cases like that?

2

Hi Finn.
for data records like a “contact person” it’s a good idea to create a new document NodeType. To avoid such pages being reachable in frontend you can use fusion to determine

  • @if.backend = ${node.context.inBackend}
  • and vice versa

In case of frontend render your local 404 page body in the Neos.Neos:Page inheriting NodeType of your package.

2 Likes
3

Thanks for the answere, sounds like we are on the right path, thank you!

4

I like this approach, as the editor shall be used to utilize the backend. Administration backend would also be a solution, but then the UX of the editor is broken.

5

My usual approach is:

Can something appear in someway in a url, be it simply a segment? → Document

If not → Content inside some kind of container page.

Important is always the number of items you have. If you have 200 contact people, that might be annoying to manage in the document tree except if you use folder type nodes to organise and some kind of auto organisation like some plugins provide.

Handling many items on a page, f.e. with pagination and make them mostly editable in the content area is the best. You might not even need a template for that case, as the structured content rendering might be enough, depending on the requirements of your editors.

If you think that one day this “Person” nodetype might turn into something more, f.e. you want to show related content of a person, a document is of course very helpful.

1 Like
6

I use the same solutions as Sebastian.

Settings-Sites with some Section Elements wich can be used to manage Contacts and similar data globally.
A big advantage of managing contacts in these content collections is, that we can build filters for the editors to handle huge amouts of contacts.

1 Like