This is the third and final part of the My first content app tutorial. The content type allows you to define the actual content model. Magnolia then creates an editing interface automatically, but you have the ability to tune every aspect of the interface to its final form as required by a specific use case.

On this page you fine-tune the app to the requirements ask for by the use case defined for this tutorial. You also add and polish the i18n labels and descriptions for the elements of the app's UI.

Fine-tune the app descriptor

First you change the bookshelf-app.yaml app descriptor, to:

  • Add an app icon
  • Tailor the properties

Open the file, located in the bookshelf light module apps folder, and edit it as follows and save it:

bookshelf-app.yaml (app descriptor)
!content-type-m5:bookshelf-app
name: bookshelf-app
icon: icon-content-app
subApps:
  detail:
    editor:
      form:
        tabs:
          default:
            name: bookDetailsTab
            fields:
              ed:
                fieldType: checkbox
              title:
                rows: 2
              description:
                rows: 5
                maxLength: 5000
              publish_date:
                fieldType: date
              isbn13:
                maxLength: 13
                validators:  
                  - name: isbn13
                    class: info.magnolia.ui.form.validator.definition.RegexpValidatorDefinition
                    pattern: '97(8|9)[0-9]{9}(\d|X)'

Changing the app icon

On line 3 above, you assign the Bookshelf app a new icon called icon-content-app, which symbolizes a bookshelf.

The icon-content-app is one of the icons we provide as part of the UI framework and you can see them all here: https://dev.magnolia-cms.com/svg-app-icons-gallery/. 

Tailoring the properties in the detail subapp

  • Line 10: Give the default tab a new name.
    The app generator creates the default tab in the Book detail subapp. You assign the tab (node) a more meaningful name, bookDetailsTab, which makes it easier to address the app components and i18n labels.
  • Lines 12 and 13: Change the ed property.
    You change the field type of this property from the default text to the checkbox field type.
  • Lines 14 and 15: Set the height of the field for the title property.
    You set the rows field property of the title content type property to 2. Some book titles are longer and in most cases a two-row text field allows the user to read the whole title compared to just a one-row field.
  • Lines 16-18: Define the height and maximum length of the field for the  description property.
    Similarly, you set the number of rows for the description property to 5.
    You also limit the maximum length of a description to 5 000 characters to comply with data import restrictions of the libib.com cloud service, in case the user decides to transfer data between the Bookshelf app and libib.com.
  • Lines 19-20: Change the publish_date property.
    Set the field type to date to help the user find a book publication date with a pull-down calendar.
  • Lines 21-26: Length setting and a validator related to the isbn13 property.
    We set the maxLength property to 13 characters to provide the user with a digit counter for entering the ISBN-13 number.
    On lines 23-26 we add a regex-based field validator for the ISBN-13 field. This validation makes sure that the number entered complies with the basic syntax of ISBN-13 numbers.

Adding an i18n message bundle

Now add and polish the i18n labels and descriptions for the elements of the UI in the Bookshelf app.

What is a message bundle?

A message bundle (resource bundle in Java) is a collection of .properties files. Each file contains key-value pairs of translated user interface text such as labels and messages. The keys in all files of the same bundle are identical but the values are language specific translations.

A message bundle must contain at least one .properties file. The files are named after the language (locale): <bundle-name>_<locale>.properties, for example app-pages-messages_en.properties. Every Magnolia module should provide its own message bundle. If a module installs several apps, each app should have its own message bundle.

Since you've assigned a new name ( bookDetailsTab) to the default tab in the detail subapp, you have to create new labels even for the message keys that supply label values from the magnolia-ui-framework module.

In the i18n subfolder, open the bookshelf-messages_en.properties file and save it with the following content (click the filename link to see the content):

# App label
bookshelf-app=Bookshelf

# Book browser subapp labels.
bookshelf-app.browser.label=Book Browser
bookshelf-app.browser.actionbar.sections.root.label=Actions
bookshelf-app.browser.actionbar.sections.item.label=Actions
bookshelf-app.browser.actionbar.sections.folder.label=Actions
bookshelf-app.browser.actionbar.sections.deletedItem.label=Actions
bookshelf-app.browser.actionbar.sections.deletedFolder.label=Actions
bookshelf-app.browser.actions.addItem.label=Add book
bookshelf-app.browser.actions.confirmDeletion.label=Delete book
bookshelf-app.browser.actions.editItem.label=Edit book data
bookshelf-app.browser.actions.rename.label=Rename book
bookshelf-app.browser.actions.addFolder.label=Add shelf
bookshelf-app.browser.actions.confirmDeleteFolder.label=Delete shelf
bookshelf-app.browser.actions.editFolder.label=Rename shelf
bookshelf-app.browser.actions.moveFolder=Move shelf
bookshelf-app.browser.actions.confirmDeleteFolder.confirmationHeader=Delete {0,choice,1#this shelf|1< these {1} shelves}?
bookshelf-app.browser.actions.confirmDeleteFolder.confirmationMessage={0,choice,1# This shelf|1< These {1} shelves} and all {1,choice,1#its|1< their} sub-items will be marked for deletion.
bookshelf-app.browser.views.treeview.name.label=Shelf name or book cataloging name
bookshelf-app.browser.views.listview.name.label=Cataloging name
bookshelf-app.browser.views.listview.path.label=Bookshelf location

# Book detail subapp labels and descriptions.
bookshelf-app.bookDetailsTab.label=Book Details
bookshelf-app.bookDetailsTab.name.label=Cataloging name
bookshelf-app.bookDetailsTab.name.description=This field is required. Its value is used to create a unique, hyphenated book cataloging name which is visible in the BOOK BROWSER subapp and under which the book is stored in the <i>books</i> workspace.
bookshelf-app.bookDetailsTab.authors.label=Author(s)
bookshelf-app.bookDetailsTab.ed.label=Author(s) in editorial role
bookshelf-app.bookDetailsTab.ed.buttonLabel=
bookshelf-app.bookDetailsTab.ed.description=Check off the box if the primary role of the "Author(s)" is editorial. 
bookshelf-app.bookDetailsTab.title.label=Full title
bookshelf-app.bookDetailsTab.description.label=Description
bookshelf-app.bookDetailsTab.publisher.label=Publisher
bookshelf-app.bookDetailsTab.publish_date.label=Publication date
bookshelf-app.bookDetailsTab.publish_date.description=If you know just the year of publication, enter the date as YYYY-01-01.
bookshelf-app.bookDetailsTab.isbn13.label=ISBN-13
bookshelf-app.bookDetailsTab.isbn13.description=If an ISBN-13 is available for the book, enter it without hyphens or spaces.
bookshelf-app.bookDetailsTab.isbn13.validation.errorMessage=The ISBN-13 number has 13 characters. The first 12 characters can only be numerals, the last character can be either a numeral or "X". The number has to begin with either 978 or 979.
bookshelf-app.detail.actions.cancel=Cancel
bookshelf-app.detail.actions.commit=Save Book Data

To apply the new labels and descriptions, close and reopen the Bookshelf app in Magnolia.

(thumbs up) Congratulations! The Bookshelf is now ready for use.

You can tweak the app's configuration further to expand its capabilities:

  • Sample book data

    If you would like to see some book data in the app, you may either add it yourself or download it as a sample file called books.My-Good-Reads.xml from the _sampleContent folder in the bookshelf repository. Import the sample data to the Bookshelf app using the Import action in the Book browser subapp.

  • Compatibility with online library management services

    Except for the ed and name content properties, all the other properties make the design of the Bookshelf app compatible with the data nomenclature used by the libib.com service. This makes a file-based or a REST-based exchange of book data between the Bookshelf app and the Libib cloud service possible.  


#trackbackRdf ($trackbackUtils.getContentIdentifier($page) $page.title $trackbackUtils.getPingUrl($page))
  • No labels