You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Step 0, it is mentioned that you will be required to find problems with the steps, but users don't know the requirements for PRs and issues until much later on. It would be nice to have an explanation of these before the very end.
Steps to reproduce the problem
Go to 'The Steps' section in First Steps on pages/vi/vi-first-steps.md
Screenshots
Here is the specific section:
Proposed solution
Add a bulleted list or table describing the final requirements, while explaining that the requirements will be explained in detail in future steps. If using a table, I suggest making all the page's bulleted tables for consistency.
The text was updated successfully, but these errors were encountered:
In this I would suggest we could make the words as links starting from Mardown to Github PRs, so they can navigate as soon as the read it. It wouldn't require major changes as well
Kuljeet1998
pushed a commit
to Kuljeet1998/Kuljeet1998.github.io
that referenced
this issue
Jun 20, 2024
There is a small part at the end of Step 8 mentioning what should be completed by the end of the steps. I believe putting something similar at the beginning could be efficient and do the job. It won't take much time and keep it simple for now until a better method is done.
Problem
In Step 0, it is mentioned that you will be required to find problems with the steps, but users don't know the requirements for PRs and issues until much later on. It would be nice to have an explanation of these before the very end.
Steps to reproduce the problem
Screenshots
Here is the specific section:
Proposed solution
Add a bulleted list or table describing the final requirements, while explaining that the requirements will be explained in detail in future steps. If using a table, I suggest making all the page's bulleted tables for consistency.
The text was updated successfully, but these errors were encountered: