Search the Community
Showing results for tags 'page table fieldtypes'.
Found 1 result
-
Hi guys, I'm currently designing the backend fields of a new intranet publishing platform and I think that there's still some improvement possible. Like I know you, you probably have some great ideas for my issue To explain the structure in the frontend: The starting page is divided in three horizontal sections with each section having cards in them (the first section having 8 cards, sections 2 and 3 each having 3 cards). Normally the first section should display the latest news, the second section should display social media postings and the third section should display news from a specific category. My current approach: I've created a "page-sections" template for my starting page, which has three "section" templates as children. For each section I've defined a field "Standard selectors" with content like template=news, sort=-date Now the tricky part: It should be easily possible to define some "sticky" cards in each section. For example in the first section the third card should be an important news, the fifth card likewise and the seventh card should be a promotion card. So what I was trying to do is adding a "page" field to my section template like the following: As you can see I've added 8 pages (resembling the 8 cards for the first section) where pages 3, 5 and 7 are specifically selected items and the others are just an empty page named "Standard-Kachel" (meaning "standard card"). This standard card field should be filled out with the fields from the "standard selectors". With this I would be totally happy! The problem is that the page field does not accept the same page selected multiple times. Is this possible anyway? Another idea was to use the ProField Table instead. But there one would need another approach to add the page field as a column. Maybe you've got another idea? ;-) Thanks a lot!
