Once #49 gets in, what stopping us from using entity translation instead of content translation
Pros: unified way of handling translation (nodes, taxonomy, ...) no need of i18n
Cons: still hard to manage translations of menu, block and other things
Related - https://github.com/backdrop/backdrop-issues/issues/4198 Content translation improvements
As people weigh in here with reasons they prefer (or were forced) to use entity translation, I would love if it we could add those reasons to that issue too -- since many of those improvements will be able to be included before 2025 :)
GitHub Issue #:
52
Recent comments
To add a summary of event details to the list below the title and customize the way the time is displayed. If this is part of the library then I guess the easiest way is to create a list...
FullCalendar Views - way to modify list view?
AFAIK, this is part of the FullCalendar library and it doesn't create a separate View Display. If you want to customise the look and feel, you will need to target the elements with CSS....
FullCalendar Views - way to modify list view?
CSS - font-weight: bold. If in the future you want to remove the bold for that field on all pages of the site, changing the formatting of all pages is very difficult, unlike changing the CSS...
Use text editors in Summary Field