Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UI for notifications inbox link #94

Closed
rhiaro opened this issue Jan 14, 2016 · 4 comments
Closed

UI for notifications inbox link #94

rhiaro opened this issue Jan 14, 2016 · 4 comments

Comments

@rhiaro
Copy link
Collaborator

rhiaro commented Jan 14, 2016

Find a nice way to display the notifications inbox that will look good for most types of article, or have some options the user can set (eg. I could see wanting to hide the link altogether in Read mode, and it only actually needs to be in there machine-readably anyway)

@csarven csarven added the UI label Jan 17, 2016
@csarven
Copy link
Member

csarven commented Jan 17, 2016

Currently, we pile up brief definition-list like stuff (or metadata, depending on how you look at it) near the header region - above the main content of the document. I think we should stick to that for now - keep it visible. When the UI is a bit more advanced, it'll should be possible to move it around in the document e.g., to the footer, or hide completely from view. This whole thing depends on another dokieli feature which is not yet defined.

@rhiaro
Copy link
Collaborator Author

rhiaro commented Jan 20, 2016

We also need UI for adding an inbox link to a document, and creating the inbox if it doesn't already exist.

@csarven
Copy link
Member

csarven commented Dec 26, 2016

There is #110 which is intended to cover the feature on adding an inbox to the article.

@csarven
Copy link
Member

csarven commented Apr 22, 2024

#396 covers user inputting the inbox URL. What remains of this issue is perhaps the UI part where while an inbox may be associated with the article, the user should have the option to hide the inbox text/URL as a whole. To that end, that will be follow up / considered as part of #401 .

@csarven csarven closed this as completed Apr 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants