-
Notifications
You must be signed in to change notification settings - Fork 67
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
Documentation📄: Table for short forms. #202
Comments
If this issue looks fine, please assign this issue to me. |
I can help with with issue |
@meenaljain0303 what do you think we can do here, I tried searching if we can link these short form (anywhere in the doc) to the full forms in the document itself but there is no such syntax available in sphinx. |
We can hyperlink the short forms to their respective long forms, which will be provided at the end of the document!? |
Ohk then, I'll unassign myself now, go ahead with this issue, and maybe we can discuss it in the community_meeting tomorrow. |
Kindly assign it to me so that I can contribute |
What is the current documentation state?
The Full Lands Integration Tool (FLINT) is moja global’s flagship software. FLINT is a modular and highly flexible open-source software technology designed to meet the needs of governments, the private sector and other users in measuring, reporting and verifying (MRV) – or forecasting – greenhouse gas emissions and removals from forestry, agriculture and other land uses (AFOLU).
Where is this stated?
documentation
Why do you want to improve the statement?
While I was going through the documentation, I felt that there were many short forms and I had to constantly jump to that particular page where I found that short form for the first time. This can be helpful for those who are just starting to contribute.
Proposed Statement
What we can do here is make a table for short form with what they represent and show it on every page or at least link it somewhere in documentation .
Additional context.
No response
The text was updated successfully, but these errors were encountered: