Tomevexa Book Catalog di Francesco La Mancusa provides tools for creating and maintaining a book catalogue in WordPress.
Main features include:
wp-content/uploads/tomevexa-book-covers/.Imported books are saved as drafts so an editor can review them before publication. New cover files downloaded or generated by Tomevexa are stored in the plugin-specific tomevexa-book-covers uploads directory.
Tomevexa is designed so that the public catalogue can be navigated with a keyboard and understood with assistive technologies. Book-cover images in catalogue cards are links to the corresponding book page. These cover links are keyboard-focusable and expose an explicit accessible name identifying the image as the book cover and stating that the link opens the book page. Cover images also include meaningful alternative text based on the book title.
Published books use the public tomevexa_book permalink. On a single-book page, Tomevexa adds a semantic book-details section containing the cover and available bibliographic metadata before the editor-managed book content. Search and result areas use labelled regions and live status messages, interactive controls have visible focus indicators, and the stylesheet includes reduced-motion and forced-colors accommodations.
Accessibility also depends on the active WordPress theme and on content entered by site editors. Site owners should therefore test their complete front end with keyboard navigation and their preferred assistive technologies.
Tomevexa Book Catalog may communicate with the following external services when the related feature is used or enabled:
Used to search for and retrieve bibliographic data and cover information. Search terms, ISBNs, and book titles may be sent to Google. Google Books API terms: https://developers.google.com/books/terms — Google privacy policy: https://policies.google.com/privacy
Used as a selectable source for bibliographic data and cover images. Search terms, ISBNs, and book titles may be sent to Open Library. The service is operated by the Internet Archive. Terms: https://archive.org/about/terms.php — Privacy policy: https://archive.org/about/terms.php#privacy
Used only after the administrator configures valid credentials. ASINs, ISBNs, titles, and product requests may be sent to Amazon to retrieve product information and create supported affiliate links. Use is subject to Amazon’s applicable programme terms and privacy policy: https://affiliate-program.amazon.com/help/operating/agreement — https://www.amazon.com/gp/help/customer/display.html?nodeId=GX7NJQ4ZB8MHFRNJ
Wikidata, Wikipedia, and Wikimedia Commons may be queried to enrich author profiles with biographical information and properly attributed images. These requests occur only when an administrator explicitly chooses the author enrichment action from the author edit screen. The author name is then sent as a search term; no Wikimedia request is made automatically when an author term is created. Wikimedia services are operated by the Wikimedia Foundation. Terms: https://foundation.wikimedia.org/wiki/Policy:Terms_of_Use — Privacy policy: https://foundation.wikimedia.org/wiki/Policy:Privacy_policy
On WordPress 7.0 or later, administrators may optionally generate an original catalogue cover for a book by using the built-in WordPress AI Client. The plugin does not store AI provider credentials itself: the site owner chooses and configures a compatible provider through WordPress Connectors. When the administrator explicitly runs the AI cover action, the book title, author names, publisher and a short excerpt of the book description may be sent to the configured AI provider to generate an original illustrative cover placeholder. Provider-specific terms and privacy policies depend on the provider selected by the site owner.
Bibliographic and author-enrichment requests are initiated by administrators or configured background jobs. Imported cover images are downloaded into the WordPress Media Library under uploads/tomevexa-book-covers/ and are served locally on the public catalogue; external cover URLs are retained only as source metadata. AI cover generation is administrator-initiated and sends the bibliographic context described above to the AI provider configured by the site owner. Administrators should review the external-service terms and privacy policies and disclose enabled integrations as required for their site and jurisdiction.