search

PalisadoesFoundation / talawa-docs

Documentation for Talawa and Talawa-API
https://docs.talawa.io/
GNU General Public License v3.0
44 stars 146 forks source link

1. Using Text Instead of Email JPEGs for Better Usability 2. Scroll Navbar for Enhanced Space Management in Smaller Devices #586

Closed Nitya-Pasrija closed 1 year ago

Nitya-Pasrija commented 1 year ago

Describe the bug I suggest converting the mails imgs to text format to make it easier for viewers to copy the emails. Currently, they have to switch back to see the email, which can be inconvenient. Additionally, I propose hiding the navbar on down scroll and making it reappear on scrolling up, to improve the user experience.

Screenshots image

Potential internship candidates Please read this if you are planning to apply for a Palisadoes Foundation internship https://github.com/PalisadoesFoundation/talawa/issues/359

palisadoes commented 1 year ago

Duplicate.

Please search the closed issues to see whether your issue has already been addressed.

Closing

Nitya-Pasrija commented 1 year ago

I apologize for any inconvenience caused by not checking the closed issues before submitting my query. Going forward, I will make sure to check the existing issues before posting to avoid such oversights.

Nitya-Pasrija commented 1 year ago

@palisadoes Should we proceed with the implementation of a scrollable navbar to provide mobile application users with more screen space though?

palisadoes commented 1 year ago

We are now focusing on three types of issues as priority areas:

  1. The improvement in the reliability of our code base. There are many issues created to test existing code. It is a good place to start if you want to understand the operation of various apps. When you submit PRs, we automatically check to see whether the code you submitted has been covered by testing and that each file meets the minimum standard level of the repository as a whole. You won’t be able to avoid understanding testing regimes to contribute to Talawa.
  2. The fixing of bugs and features that seriously hamper the user from using the application. The apps have various shortcomings. The most obvious ones are where the apps do not work as expected. For example buttons that don’t work, errors or messages that are not displayed to make the user understand what to do and many more. Think of any difficulty you have had in getting things working, there could be a bug there waiting for you.
  3. The creation of additional our updated documentation that helps with improving both the experience of the end user and the various GitHub contributors who support the development of our software. This would include user guides.

We will only be accepting feature issues for deficiencies that are obviously lacking in the apps. These are things that make it very difficult to operate the apps. Even so, the PRs will still require you to understand testing as stated before.

Closing

palisadoes commented 1 year ago

Also we need to one issue per problem discovered. It makes tracking easier.

Nitya-Pasrija commented 1 year ago

Alright, I will keep this in mind. Should I create a separate issue for the navbar issue thou?