Create a place to highlight/document the officially maintained Go SDK
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 42/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- go
- Domain
- documentation
Research direction
Review the existing miscellaneous SDK page and the surrounding documentation navigation to understand where SDK references currently live. Confirm how the official Go SDK should be advertised without moving its repository-hosted docs, then update the documentation so the SDK has a clear, maintained home.
Written by the indexing model from the issue text.
Description
Request Type
Missing section coverage
What needs to be documented?
@cap10morgan maintains an official Go SDK for Harper that was previously included in a "miscellaneous" SDK page that contained many other unmaintained and unofficial Harper SDKs. We need to find a new home for the Go SDK. The docs for it do live within the repo of it itself; we do not need to consider moving those docs here. But we should at least advertise the existence of the Go SDK in our official docs. I'm not against a new SDK page somewhere.
Where should this be documented?
No response
Why is this needed?
No response
Existing information
No response
Priority/Impact
Medium - important but not urgent
Are you planning to fix this issue?
No, just reporting the issue
First-time contributor support
- I'm new to contributing and would appreciate guidance on the process
- I'd like help understanding the project structure
- I need assistance with setting up the development environment
- I'm comfortable contributing but new to this project specifically
- Dominant language
- MDX
- Stars
- 9
- Forks
- 9
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 16
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from HarperFast/documentation
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
HarperFast/documentation#690 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
HarperFast/documentation#677 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 Half a day Newbie friendliness 88/100
HarperFast/documentation#675 ·
Maintainers usually reply within 2 days
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
HarperFast/documentation#665 ·
Maintainers usually reply within 2 days
-
content
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
HarperFast/documentation#478 ·
Maintainers usually reply within 2 days
All issues in HarperFast/documentation
Similar issues
-
feature
Difficulty 1/5 Under an hour Newbie friendliness 72/100
vercel-labs/skills#2370 ·
Maintainers usually reply within 1 day
-
sync-en
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 1 day
-
sync-en
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 3 days
-
bug developer portal
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
discord/discord-api-docs#8645 ·
Maintainers usually reply within 1 day
-
Перевод устарел
Difficulty 1/5 1-3 hours Newbie friendliness 88/100