Closed agitator closed 8 years ago
I would love to see an Event tile inside the package, but we need to have a mockup of it first.
if you're only trying to add and register a tile for collective.cover in another package, it's easy: just take one of the standard tiles as an example (the Banner tile coud be a good one) and register yours in the configure.zcml of your package (see src/collective/cover/tiles/tiles.zcml).
also, help on creating documentation is welcome: take a look at the files inside docs (refs. #164).
if we would use the approach of the "All content"/full_folder_view wouldn't need a separate tile for each new content type.
but in this case I think an Event tile will still be needed.
i'm talking about reusing content that already exists in a plone site. you wanna do a tile for each type seperatly and only allow that type to be added to that tile? maybe i didn't get the concept of c.cover to the full extend?
The main goal of colective.cover is create front-pages for a website or sections. Thinking in a front-page, its not a regular issue insert the full content of an object inside a front-page. You usually create a highlight showing important informations like title and description, linking for the content. The event tile should do that, showing relevant informations for the event, like Title, start and end date, local.
Is it not easier to just add another tile in another product (and just disable the other tile in the control panel) ?
you can see a couple of examples here:
i got a custom dx ct based on p.a.event that i wanna display within the contentbody tile.
how would one extend a tile from another package? i don't think an extra tile just for events reasonable or the way tiles should work.