collective.glossary 1.0b1

Installation

To enable this package in a buildout-based installation:

1. Edit your buildout.cfg and add add the following to it:

   [buildout]
   ...
   eggs =
       collective.glossary

After updating the configuration you need to run ‘’bin/buildout’’, which will take care of updating your system.

Go to the ‘Site Setup’ page in a Plone site and click on the ‘Add-ons’ link.

Check the box next to collective.glossary and click the ‘Activate’ button.

Usage

TBD.

Screenshots

Developer Notes

The terms are loaded in a page using an AJAX call to a browser view that returns them as a JSON object.

The tooltips will only be available in the default view of a content type instance.

1.0b1 (2016-12-19)

• Term template was refactored to avoid duplicated definitions (closes #26) [hvelarde]

• Glossary terms now use tile scales (closes #5). [hvelarde]

• Remove dependency on five.grok. [hvelarde]

• Fix ReferenceError on JavaScript code (Plone 5 does not include global variables anymore). [hvelarde, rodfersou]

• Remove dependency on Products.CMFQuickInstallerTool. [hvelarde]

• Change glossary to always call JSON view from the portal URL (closes #22). [rodfersou]

• A new rich text field was added to the Glossary content type. [hvelarde]

• Normalize glossary index (closes #18). [rodfersou]

• Add option to select content types that will display glossary terms (closes #14). [rodfersou]

• Apply Glossary just to #content-core. (closes #12). [rodfersou]

• Review method is_view_action to work with Virtual Host configuration. [rodfersou]

• Terms should only be added inside a Glossary (closes #8). [hvelarde]

1.0a1 (2015-05-18)

• Initial release.