The primary intended users are individuals, like myself, who wish to keep a record of books, films, plays, gigs, exhibitions and similar events that they have experienced.
- xbBooks - as the name implies is for a catalogue of books of all sorts. Changelog
- xbFilms - not surprisingly is for movies, although it can also handle series, tv shows and box-sets. Changelog
- xbEvents - is for live performance; music, theatre, spoken word and comedy - IN DEVELOPMENT
- xbPeople - a support component bundled in the packages for the above, provides tools for managing a common database of people and characters as well common styles, language and code across the components. Changelog
- Recently added : mod_xbculture_recent
- Filtered lists : mod_xbculture_list
- Random images : mod_xbculture_randimg
A package containing all of the components and modules is available.
11th August 2023 J3
Possible new modules
- Search titles/names across xbCulture items
- Top/bottom rated
- Popular People
- Common Characters
Further components like xbEvents (theatrical performance, exhibitions, gigs and other live events) are in development,
xbFestivals (combining many separate events under one roof) may become a separate component. Likewise an xbSeries component to handle tv/video series which consist of multiple seasons and episodes might become a spn-off from xbFilms
It is not intended (at present) to develop an xbMusic component for recorded music (albums/CDs etc) as this is pretty well covered by the plethora of music players available.
Common to all these is xbPeople which provides a database of real people and fictional characters involved in the works - obviously one person may have many roles: film director, actor, author, musician, painter - so it makes sense not to duplicate records but share them between the components. Likewise a character might appear in a book, a film a play and inspire some music, so they are also shareable between the components.
The basic structure of the components is similar - the data structures and relationships and the views of the data have commonalities - although of course there are particular fields which are appropriate to each type of item.
Many items have common features - a Title and optional sub-Title, a summary (a short bit of text), a description (longer text, may be known as a synopsis for a book or film - intended to be factual rather than opinion), plus links to people involved and some specific fields (dates, formats, publishers/producers/promoters/venues)
Each core item type - a book, a film, an event - has its own data table. Each item may have one or more reviews (at its most basic a review just consists of a rating from 1-appalling to 7-the best-thing-ever) which may have its own title, summary and description together with dates and other notes.
At the simplest an item may have no review or or only one, but the components allow for multiple reviews of an item to be created so if you re-read an old favourite book, or watch a film with a partner you can express separate views and ratings.
When it comes to people, at the simplest a person just consists or an optional firstname and a lastname - but there is the facility for including more biographical information if required.
All components provide three basic core views on the front-end of the site - a list view, an individual item view which includes any ratings and reviews, and a blog view of reviews which have some content. In addition there are people lists with links to the items they are associated with, and person detail views where there is more than just a name to show.
The list views can all be customised by the admin regarding which fields are show, filtering and sorting - and also optionally further filtered and searched by the end user.
Standard Joomla Categorisation and Tagging facilities are provided - an item can only belong to a single category, so in practice I find these less useful than Tags, but categories are included in case you find a use for them (they can simply be hidden if not used)