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

DRAFT - Go to top button in Notes #74

Open
Julien-Dubois-eXo opened this issue Aug 3, 2023 · 8 comments
Open

DRAFT - Go to top button in Notes #74

Julien-Dubois-eXo opened this issue Aug 3, 2023 · 8 comments

Comments

@Julien-Dubois-eXo
Copy link

Julien-Dubois-eXo commented Aug 3, 2023

Rationale
Details of the GAP ( problem(s) to address ) expressed by few words using some screenshots.
Note: avoid describing the solution here.

Currently, when we have a very long note we have to scroll a lot to go to the top of the page.
Moreover, with the addition of the anchor feature, we will be able to create a table of content at the top of the note to facilitate navigation inside. Usually, it's located at the top so we should be able to quickly go up.

Functional requirements

  • a button is added on the side of the note page
  • the button is following the screen when we scroll
  • clicking on it scroll automatically to the top of the page

Image

Non Functional Requirements
Expected volume & Performance requirements

Security requirements (Authentication, Authorizations, Audit track / traceability, data retention…)

Extensibility requirements (Identified extension points, plugables implementations...)

Configurability requirements (properties introduced, default settings, jobs, etc...)

Requirements related to existing users data

Requirements related to existing features (ex: Add a button to existing modules...)

Feature Flag (property name, default status, target audience, functional behaviour)

Other NFR (ex: Use of VueX, Vue, Vuetify)

Impacts
Requirements (Squash)

Documentation to update?

Training level / Change management needs

Software Architecture
Security
Access (GUI, API…)
Rest API design (Entry points, domain objects)
Portlet Vue & Vuetify, simple portlet, extension WAR ...
Services & processing
Ex: Scheduled Jobs
Data and persistence
Macro data model
Persistence layer (RDBMS, elasticsearch...)
Use of caches
Support for clustering
Support for multitenancy
Integrations
Migration strategy
Annexes
Reasoning that explain the technical choices
Impacts (ex: impact on public REST/Java API)
References (links...)

@Julien-Dubois-eXo Julien-Dubois-eXo converted this from a draft issue Aug 3, 2023
@Julien-Dubois-eXo
Copy link
Author

The specific location and size are open to discussion.

@srenault-meeds
Copy link
Member

Hi,
I suggest you to take a look at what we have done on meeds.io using the scroll to top option from vuetify.
In addition, I have two suggestions:

  • when a drawer opens, then it opens on this option and not the contrary (to avoid problem with actions to do in the drawer)
  • why not providing this option in other pages? Notes seems natural. Yet, it can be interesting to have such option when browsing the stream, the spaces, the people page, etc.

WDYT?

@Julien-Dubois-eXo
Copy link
Author

Definitely interested if you already have work on it. It seems you did but I can't find where. Could you show me where you implemented it, please?

We are doing one step by one step. We will implement it for Notes and News first. It may be interesting to do it also for other pages, you are right. We could discuss it.

@rdenarie
Copy link
Member

rdenarie commented Sep 4, 2023

@Julien-Dubois-eXo We implemented this option for a customer few times ago.
It is present on all pages.
If you plan to generalize it, it will easier to put it on all page at first step, than adding it on notes, then news, then generalize it.

@Julien-Dubois-eXo
Copy link
Author

For the moment, it's only requested to add it on notes and news. I did not have the time to discuss it with @margondicco.

But if it's not very complicated and takes not much time to implement on all pages, it might be interesting.

It should just be validated with @margondicco and @srenault-meeds.

@srenault-meeds
Copy link
Member

+1 to generalize it now

@srenault-meeds
Copy link
Member

Is that still something you plan to do?

@Julien-Dubois-eXo
Copy link
Author

Not for 6.5. For later I have not the visibility.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

No branches or pull requests

3 participants