Closed sheepyhollow closed 3 years ago
The final behaviour is yet under discussion, there are several ideas but no final decision. But the first sub-task is basically the same: make messages available on the landing page. This can be done anytime.
@anhnguyen-98 If you start working on the 2nd sub task, you should check out the message.state.ts
and message.actions.ts
. Some of the work is already prepared since all messages are already loaded into the local store and obviously displayed from there. It seems a little unfinished, there is no routine to mark messages as read, but the basics are there.
As mentioned above: concentrate on the 1st sub-task - part 2 and 3 are not needed for the release.
I noticed that the "Neuigkeiten"-Area is always displayed, even if no valid messages exist. I updated the task list above. It's okay for now - we are going to make sure that we have valid messages.
We will have to edit the css on landing page messages, the effective line-height or line spacing is far too high and messages look "stretched".
And there is a double space character between the message title and the |
separator. I think it's the linebreak after the {{ message.title }}
variable and the <span>
element.
SOLID has a built-in "messaging service" to inform users about new content, updates etc. Messages are already displayed on the "info" page, separately as "News" and "Changelog" - this implementation can be used as a reference for the task.
Messages should be displayed on the main page (skeleton landing component) and look something like here: https://app.geomat.uni-frankfurt.de/