Introduction
Kupu Tabs enables end user editable plone.org like front page tabs in WYSIWYG editors.
This is a generic Javascript/CSS library and can be pluggd in to any WYSIWYG editor. Currently Kupu is supported.
Benefits and use cases
Where there is plenty of content on the page, but splitting it up is unsuitable and we do not want the user navigate away from the page
Suitable for content where the reading order is not critical
No page loads - better user experience
Fact pages (http://plone.org front page)
Data sheets
Accessibility - if Javascript is not supported renders as a normal page
Printability - prints as a normal page
Installation
Install via buildout
- eggs =
collective.kuputabs
- zcml =
collective.kuputabs
Usage - Plone
Open any Kupu editable content.
Write a tab name and choose “Tab” as its style from Kupu style drop down.
All text after Tab until the next Tab section or the end will be placed inside a tab container. Tab’ed text will be placed inside a tab container.
You can choose which tab is open by default with Tab (open by default) style.
There is two example style files: kuputabs.css.dtml for any Plone theme (variable colors) and kuputabs2.css which is more generic one.
Usage - Generic HTML
Create a container DIV for your content. Usually this is #content or similar and already provided your CMS/blog/whatever.
Add class “kuputab-tab-definer” for <h2> elements you want to be tabs. Add class “kuputab-tab-definer-default” for the tab which is open by default.
Include kuputabs.js on your page. Include kuputabs-alternative.css stylesheet or create your own.
Voila.
Under the hood
When the page is loaded in the view mode, Javascript parses all kuputabs-tab sections and builds a tab container from them. If Javascript is disabled the content will appear under normal Subheading styles.
There is an important distinction with two kind of CSS classes
kuputab-tab-definer is h2 element which marks the beginning of the tab
all content until the end of kuputab-tab-definer parent element or next kuputab-tab-definer goes to this tab
kuputab-tab-definer content is mutated to kuputab-tab-container which is placed at the bottom of kuputab-tab-definer container element
document.designMode attribute is used to determine whether the visitor views the page or is it under WYSIWYG editor.
Sponsorship
Thanks to our fabulous sponsors.
Metadata
Release files for collective.kuputabs 0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| collective.kuputabs-0.1.tar.gz | 9.3 kB | Without provenance | Details for collective.kuputabs-0.1.tar.gz |
Release files / collective.kuputabs-0.1.tar.gz
| Download URL | collective.kuputabs-0.1.tar.gz |
|---|---|
| Size | 9.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d4efe220ff6b4768aab984c924c2b6b9fcc0f8c048d56ee1ae7e9da4ba123b88
|
|
BLAKE2b-256 checksum How to use checksums |
6bbd71be2f2d2f5d9f2b3ec6b7c9e9c3f71e54828b40b6bbbc5cac8a6187f6fa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for collective.kuputabs 0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.