search

culturecreates / footlight-app

Footlight CMS Front-end
https://cms.footlight.io
3 stars 0 forks source link

Style and functionality changes of input component to include support for additional content languages #1189

Closed SyamBabu-M closed 3 weeks ago

SyamBabu-M commented 3 months ago 
### Tasks
- [x] Handiling language literal functionality in newly update input components
- [x] Design Changes of tabs.
- [x] New Language tabs in input component.
- [x] Add more content languages
- [x] Integrate new content language type to existing components. Change static content language handling and adapt dynamic handling
- [x] Replace old input form item component with new dynamic component
- [ ] Peer review of enitre form pages
SyamBabu-M commented 3 months ago

@SuhailAliyar @dev-aravind The list of languages need to be added in Calender details get API. Currrently we are handling this with contentLanguage field that can only take values of FRENCH, ENGLISH or BILINGUAL. It need to be converted to an array of languages.

dev-aravind commented 2 months ago

@SyamBabu-M If the languages are passed as empty strings, i.e. "" then the language fallbacks are not working in the people and organization forms. Please take a look into this.

troughc commented 1 month ago

Notes from meeting with @SyamBabu-M and @troughc Syam: will take the 'spreadsheet' approach (not tabs) for the concept list Syam: remove semi-colons from the language labels at the top Syam: when there are only 2 languages, do not have scroll bar, otherwise do have one.

To discuss with Stephanie next Tuesday Caitlin/Design: when 3 or more languages to display, do we need some kind of indicator for user to scroll to see other languages? both ways? Caitlin/Design: what design changes are needed to improve the spreadsheet concept approach? It's the best of the current options available but how can we make a better user experience? Caitlin/Design: what design changes if any are needed for the language labels in the spreadsheet concept approach? Also in other multi-language fields? For example, what can we do with the warning symbol - it causes the tabs to overflow the space (get 3 dots), should we use a colour instead, have a popup. What is the best approach?

QUESTIONS What if a concept does not have korean language but the listing site includes a korean page, do we use the fallback language: YES What fallback language should be used? Should this be done in frontend or backend?

do we show the language literal tag when a concept is replaced by a fallback language? Where would this appear - in tree or in edit popup dialog box

troughc commented 4 weeks ago

@SyamBabu-M I think this should be deployed too although we have NOT updated the concept list yet (with the new design). Do you agree?

troughc commented 4 weeks ago

Note for @SyamBabu-M I have added a new 'enhancement' issue for implementing the 'spreadsheet' approach in taxonomies. Please find it here