You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Imported from Trac ticket #19 reported by jboggs on 2009-07-23:
As reported by Jen Anderson on the dev list, we should figure out a way to use shorter titles for exhibit navigation element, if needed. Having long exhibit, section, and page titles can make the design of exhibit navigation unruly.
This could either be an additional field, like "Short Title," or the system could automatically take the first 3-5 words of a title to make the navigation. The latter would be simple to implement as-is, while the former would require adding fields to the exhibit tables, and creating a migration for the changes to the DB.
The text was updated successfully, but these errors were encountered:
An exhibit that we're working on right now could use this. For example, we want the link in the navigation to say "Other Reformers" and the page title to be "Other Reformers: The Diversity of the Protestant Movement".
This is a pretty old issue - would a new field to hold the short title still be a helpful addition to the exhibit builder plugin?
I'm not opposed to this feature, but it's also not exactly a priority.
It's a pretty natural case for a pull request: add a column for the short title, add the input to the form, and modify the exhibit navigation helpers to use the short titles if they're specified.
Imported from Trac ticket #19 reported by jboggs on 2009-07-23:
As reported by Jen Anderson on the dev list, we should figure out a way to use shorter titles for exhibit navigation element, if needed. Having long exhibit, section, and page titles can make the design of exhibit navigation unruly.
This could either be an additional field, like "Short Title," or the system could automatically take the first 3-5 words of a title to make the navigation. The latter would be simple to implement as-is, while the former would require adding fields to the exhibit tables, and creating a migration for the changes to the DB.
The text was updated successfully, but these errors were encountered: