Open Julien-Dubois-eXo opened 1 year ago
The specific location and size are open to discussion.
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:
WDYT?
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.
@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.
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.
+1 to generalize it now
Is that still something you plan to do?
Not for 6.5. For later I have not the visibility.
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
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...)