Personal tools
Skip to content. | Skip to navigation
raptus.header provides a folderish content type called Header which may contain multiple images. The first image contained in the header folder will be displayed by the header viewlet. If no header folder is found in the current context the viewlet tries to find one in the acquisition chain.
raptus.inlinelightbox provides a inline lightbox jQuery plugin which is highly customizable.
raptus.multilanguagefields provides Archetypes fields and catalog indexes which are able to store multiple languages.
raptus.multilanguageplone provides a simple way to have internationalization on content objects. raptus.multilanguageplone isn't meant to be a fully fledged multilanguage tool, like LinguaPlone. Translation is done directly in the edit view of a content type and provides a widget to use google's translation api to translate the different fields. Unlike LinguaPlone raptus.multilanguageplone doesn't create an object for each translation, it stores the translation on the object itself and therefor doesn't support translation workflows and language aware object paths.
raptus.supersized provides the supersized jQuery plugin written by Sam Dunn http://buildinternet.com/project/supersized/ integrated into plone and slightly adjusted.
Provides the jQuery TouchSwipe plugin as Plone JS resource
The ``redomino.advancedkeyword`` plugin aims to improve the keyword mechanism provided by Plone introducing *hierarchy* among keywords. All the customizations introduced by redomino.advancedkeyword are made with backward compatibility in mind. You can also use this plugin without pain when you need to migrate your contents: redomino.advancedkeyword still uses the standard ``subject`` field and the main work was made at frontend level using javascript. Note: having your javascript enabled is not required to use redomino.advancedkeyword. What are the main problems of the old keyword management? --------------------------------------------------------- Here is a list of problems: * all the keywords are listed as a long, long plain list * keywords are not semantically grouped Here you can see the standard keyword widget how it is prompted to : .. figure:: https://github.com/redomino/redomino.advancedkeyword/raw/master/docs/resources/keywordold.png :align: center Old keywords widgets. As you can imagine the above edit widget is hard to use and difficult to manage. How can AdvancedKeyword help you -------------------------------- And now the advanced keyword widget with hierarchical management: .. figure:: https://github.com/redomino/redomino.advancedkeyword/raw/master/docs/resources/keywordtree.png :align: center Keywords widget powered by redomino.advancedkeyword The above image lets the keyword editor collapse/expand semantic groups of keywords, which makes it more suitable to manage large sets of keywords as you can find in a large intranet. You can also search for existing keywords through the existing tags. How does it work? ================= Hierarchy is introduced using the ``.`` (dot) character: it will be used as a keyword separator. Why are we using the dot character and not another one? Because it is little used in keywords and it is easy to type. Edit view --------- If you use correctly the . separator, you will be able to create a keyword tree similar to the following one: :: [+] what [v] [+] what.doors [v] [+] what.doors.flat [+] what.doors.profiled [+] what.furniture [-] technology [v] ... Clicking on the collapse or expand controls you can open or close keyword nodes. If you click on a keyword that is a leaf, all its parents will be selected automatically; if you unselect a node, all the sub-keywords selected are automatically deselected. So by the keyword editor you will be able to select single leafs or internal nodes. You can add new keywords using the standard Plone control: nothing has changed. If you want to add one or more keywords then type something similar to the following example: * what.furniture.outdoor * etc How keywords are shown on tagged contents ----------------------------------------- If you choose the following keywords on a particular object: * what.doors.flat * technology.combined systems the customized keywords viewlet will prompt the following links: * what (clicking on this item you will be able to see all the products) * what.doors (clicking on this item you will be able to see all the door related products) * what.doors.flat (clicking on this item you will be able all the flat doors related products) * technology * technology.combined systems This works because we provide a customized catalog indexer for keywords. In the next release a new mechanism will be provided for changing the displayed keywords. For instance, if you don't like how "technology.combinened systems" looks like, you'll be able to edit it. How to use AdvancedKeyword on an existing site ---------------------------------------------- At first you will see the javascript plugin with a plain keywords list, you should add the hierarchy level grouping keywords separated by dots characters: the Plone plugin named KeywordManager is your friend! Other features ============== Keyword map ----------- Thanks to the keywords map you 're able to see the website's arguments structure. How to see the arguments map of the site: * portal_url/@@keywordsmap Keywords portlet ---------------- This product also adds a new portlet: Keyword Portlet. In order to assign a new instance of this portlet you will have to choose a "supertag" (or a namespace tag). This supertag will be used to browse a list of all tags that are "first child" of this tag. For ex. if your portal has these two contents:: >>> doc1.Subjects() ['supertag','supertag1','supertag.subtag1','supertag1.subtag2'] >>> doc2.Subjects() ['supertag','supertag1','supertag.subtag3','supertag1.subtag4'] and if you choose 'supertag1' as parent tag, the results list will show this: * subtag2 * subtag4 These are links to the search page with a search parameter set to 'supertag.subtagX'. Here you can see the keyword portlet: .. figure:: https://github.com/redomino/redomino.advancedkeyword/raw/master/docs/resources/keywordportlet.png :align: center Keywords portlet powered by redomino.advancedkeyword (it shows a subset of existing keywords)
%redomino.breadcrumbsbrain is a new plugin for Plone CMS that will make it much easier to search for specific objects in a Plone-based portal or intranet by showing the breadcrumbs paths along with Titles and Descriptions in the search results. We all know that common users do not provide objects with proper titles and descriptions (sometimes they just do not provide them at all), which makes it hard to figure out if what you found is actually what you were looking for. Then you open every link in the search results to find it out, which may take you quite a time. What you actually need in a situation like this is CONTEXT. And context is what you get! redomino.breadcrumbsbrain displays the breadcrumbs of each object in the search results, helping you in figuring out what those objects are about: are they from 2010 or 2011? are they in the 'Notices' archive or in the 'News' archive? and so on. BE CAREFUL! This is not a standalone package. If you want you can call the breadcrumbs_renderer view provided by this package (for example you can insert this code into the search.pt template):: <tal:block tal:replace="structure result/@@breadcrumbs_renderer|nothing" /> This way you will be able to display where your search results items are placed.
Redomino Flowsearch is a new plugin for Plone CMS that provides an advanced search view optimized for Plone accoding to its features, replacing Plone's default search tool. Thanks to its tab-divided layout, it's much easier to set your search parameters compared to common, long 'Advanced search' pages. In Redomino Flowsearch the search activity is contextual, that is it always considers and notifies which is your current position in the website, therefore the position you're searching in. Furthermore, redomino.flowsearch features search parameters that have been capitalized according on Plone's characteristics and provided information. Search parameters are: - Search text - Path - Content types - Date range - Review state - Contributors - Sort results by...
A collection of useful views and portlets ========================================= The main purpose of this product is to provide series of useful views and portlets. Each of these can be applied to a folder or a collection. Views -------------- - **Gallery**: A scrollable carousel. - **Tabs**: Show the contents inside a tab. - **Accordion**: Show the contents inside an accordion. - **Gallery with preview (image top)**: A scrollable carousel that shows a preview of each content. - **Gallery with preview (image bottom)**: A scrollable carousel that shows a preview of each content. - **Slideshow**: Shows elements inside a folder (or collection) as a slideshow. Portlets ------------ This product provides three portlets. For each portlet you can choose among many different views: - **Gallery** - **Tabs** - **Accordion** - **Slideshow** - **Gallery with preview (image top)** - **Gallery with preview (image bottom)** - **List of items** - **All items** The portlets are: - **TabsAndSlides Collection portlet**: Show the items of a collection. - **TabsAndSlides Content portlet**: Show items with a certain ID inside a certain context (usually a folderish object). If the item is a Folder or a collection it returns the contained items. - **TabsAndSlides Tal portlet**: Show the items using a TAL expression. This expression can return a list of brain of a list of objects. This is a good reference: http://www.owlfish.com/software/simpleTAL/tal-guide.html For each of that portlet you can limit the elements to be shown, randomize the order of the items, show or not the border of the portlet.