Greenstand / Greenstand/greenstand-documentation
Clean Typo3 Website
- Dominant language
- No language data
- Stars
- 3
- Forks
- 12
- Avg merge
- 3m
- Merged PRs (30d)
- 1
Description
**All this should be confirmed to be located in other places and deleted.**
For example...
Contributor Documentation
An annotated index of links to how-to's, guides, references, and tutorials to help those contributing to Treetracker software.
To contribute, comment, or question the documentation, please submit an issue or pull request at the github repository
Libraries:
Repositories: Greenstand organizes and publishes its open-source Treetracker software platform in multiple github repositories, most of them public.
Greenstand Team Library Inside information for volunteers and staff, by invitation only.
Operations
Administrative panel process: How Greenstand tags new tree tokens regarding the tree's age, quality, species, and acceptability.
Administrative panel process: How Greenstand tags new tree tokens regarding the tree's age, quality, species, and acceptability.
Policies:
Index of all Greenstand Polices
How Greenstand Software Engineers Work:
Engineer's Handbook: Information about the teams building the Treetracker software, the tools we use, and how to contribute to the work.
Welcome to Greenstand's Treetracker project: Introduction for prospective sofware developers.
Greenstand APIs:
API Documentation: Reference documentation generated from OpenAPI specifications in Greenstand repositories.
The Wallet API:
The the application for managing and moving Greenstand tree tokens.
github README: Getting Started: How to download, install, and run the development version of the API server.
Contributor guide
No contributing guide indexed for this repository
Research direction
Search the greenstand-documentation repository for the Contributor Documentation content and the repeated Administrative panel process links shown in the issue. Verify each item exists elsewhere before removing confirmed duplicates or obsolete entries, then check the rendered documentation page for remaining content and typos.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100