collective.fullcalendar
Plone calendar
Integrates FullCalendar into Plone to create calendar-based content
Python 3 and Plone 5 Integration for fullcalender
2 stars
4 watching
1 forks
Language: Python
last commit: over 1 year ago
Linked from 1 awesome list
Related projects:
Repository | Description | Stars |
---|---|---|
collective/collective.documentviewer | Integrates DocumentCloud viewer and PDF processing with Plone. | 21 |
fullcalendar/fullcalendar-angular | A wrapper around FullCalendar for use in Angular applications | 1,081 |
collective/collective.catalogcleanup | Removes outdated catalog brains from the Plone Site's content repository | 4 |
collective/collective.jsonify | Converts Plone content to a JSON format | 12 |
collective/collective.contentsections | A product offering a block-based content approach for Plone 6 Classic using Dexterity content types. | 9 |
collective/collective.solr | A Solr search engine integration for the Plone content management system | 22 |
collective/collective.mailchimp | Provides integration with MailChimp email newsletter service for Plone websites. | 5 |
collective/collective.sidebar | A component for consolidating toolbar and navigation in Plone sites | 6 |
collective/collective.elastic.plone | Provides integration between Plone's content search and Open/ElasticSearch | 3 |
collective/collective.workspace | Provides restricted workspaces in Plone by granting access based on membership groups | 7 |
collective/collective.tiles.carousel | A reusable UI component for creating carousels in Plone.mosaic tile layouts. | 0 |
collective/collective.bbcodesnippets | Provides a way to integrate and manage BBCode markup in a Plone content management system | 1 |
nekken/ng2-fullcalendar | An Angular component wrapper around the FullCalendar library | 95 |
collective/collective.bookmarks | Provides a bookmarking system for Plone Classic, storing and managing bookmarks in user properties or through REST-API | 2 |
collective/collective.lineage | Enables multiple subfolders of a Plone site to be treated as separate sites with their own content and management | 12 |