Guidance on improving GlossAPI website documentation
- Dominant language
- HTML
- Stars
- 2
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Hello 👋
I’ve been exploring the GlossAPI website codebase and README in detail, especially around the WordPress API integration, internationalization (Greek/English), and overall project structure.
I’d like to contribute by improving documentation clarity and maintainability, and possibly proposing small structural or performance improvements (without introducing a build step).
Before proceeding, I wanted to ask:
>Are there any specific areas you feel need better documentation or refactoring?
>Would you prefer changes as incremental PRs (e.g., README + small JS improvements) or a single focused contribution?
I’d really appreciate any guidance on where a first contribution would be most useful.
Thank you for your time!
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.