"Tekst" page - design and functionality

[sarahwoodhouse]

Functional architect/designer: @-mention Technical architect: @-mention

Description As a service developer I need to be able to access functionality related to texts. the service developer needs to be able to see and edit all texts and text keys available for the service. It should be possible to search on texts and text keys functionality is described in #492, #490, #489, #488

In the user test done in april 2019 a number of interaction problems where identified:

• The user is unsure if things are autosaved or not
• The interaction on the two buttons don't follow the states of other buttons
• No feedback is given when pressing the buttons
• Handling a large number of texts is challenging

Sketch (if relevant) //Sketches needed

Navigation from/to (if relevant) This page is available in the left side menu undr the "Språk" area

Technical considerations Input (beyond tasks) on how the user story should be solved can be put here.

Acceptance criterea

• Possible to search for text and text keys
• Text key ids required by the platform should not be possible to edit in Studio.

Tasks

• [ ] Analysis into text functionality
• [ ] Sketches
• [ ] Auto save according to #404

[sarahwoodhouse]

For MVP 1 there will not be a need for a specific text page. The work done so far i saved and parked and will be re-visited at a later stage.

[FinnurO]

#4963

[nkylstad]

Closing this issue as outdated.