Overview
Activity Diary is an android application that can be used to record series of events in details in the right sequence to which they occurred.
This application also allows for easy referncing of a particular recorded event or activity with the time duration with which it occurred.
The contribution I made to this application is a detailed FAQ and proper answer which might be giving new users issues over the usage of the application.
Components
The questions included in the FAQ includes the following:
What is activity diary?
What’s Activity diary license?
What’s a diary?
Who is building this application?
How does Activity diary works?
How do I add new activity on Activity Diary?
How do I edit or delete an activity among the activity list?
How do I add notes to a particular activity?
I have provided detailed answers to each of the questions, thereby assisting new and existing users to have a smooth experience of the application.
This has been added to the Github file of the project, and is accessible to all users via the About page section of the application.
Frequently Asked Question section (FAQs) is a very vital tool of self service, it allows users find quick answers to possible questions they might want to ask concerning the use of the application, this relieves them the stress of having to contact the project owners before having answers to their several questions.
Additional information
Detailed link to write up here
Detailed link to texts here
Links
MERGED PULL REQUEST
Proof Of Work Done
Link To My GitHub Profile
Thank you for your contribution. Some issues should be addressed in order to improve further copywriting efforts. Some of them are:
Always proofread your work. You have some minor details in your text, as using capital letters after a comma, misusing some quotation marks and or letters floating with no meaning behind them. It's totally readable but still the devil is in the details.
As you may see in the comments from your Pull Request, the Project Owner would actually need to go over your work to successfully implement Markdown over your text as plain text is not aesthetical enough for customer service. Failing at providing such changes after you got the comment can be seen as performing below the expectations of the Project Owner.
The sole purpose of a FAQ file is to be robust enough to cover all the doubts a user may have over the use and details of the application. Therefore, consider packing up more data before providing such a file. If the questions and the relevant information are not enough to be isolated in a different file, adding the (properly detailed and formated) information to the README file could fit it better.
From the comments you received in your Pull Request it is obvious to me that your efforts were made prior contacting the Project Owner. Please remember that your work can be more detailed and useful if you always involve with the team that is developing the application.
Link to the Answers of the Questionnaire -
Click here
Need help? Write a ticket on https://support.utopian.io/.
Chat with us on Discord.
[utopian-moderator]
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
Hey @mayowa-eu
Thanks for contributing on Utopian.
We’re already looking forward to your next contribution!
Contributing on Utopian
Learn how to contribute on our website or by watching this tutorial on Youtube.
Want to chat? Join us on Discord https://discord.gg/h52nFrV.
Vote for Utopian Witness!
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit