[Bug]: Uploaded API landing content (web/apiContent.md) shows a blank landing page
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 71
- Forks
- 111
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 110
Description
Please select the area the issue is related to
Developer Portal
Please select the aspect the issue is related to
Aspect/UI (Frontend layouts, components, styling)
Description
When I upload a content pack to an API (Edit API → Content → Upload content) that includes a landing page under web/apiContent.md, the API's landing page goes blank instead of showing my content. The default overview disappears, but my uploaded content is not shown either — so the page ends up empty except for the title banner and the Documentation / Try with AI buttons.
Downloadable docs in the docs/ folder work fine (they appear under Documentation), so it's specifically the landing-page content that doesn't display.
Steps to Reproduce
- Edit an API in the portal and go to the Content step.
- Upload a ZIP containing web/apiContent.md (some Markdown) and optionally docs/*.md. [1]
- Click Upload content (it reports success).
- Open the API's landing page.
Severity Level of the Issue
Severity/Major (Important functionality is broken. Should be prioritized. Doesn't need immediate attention)
Environment Details (with versions)
MacOS, Chrome
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by reproducing the upload flow with the linked api-content-sample.zip, checking web/apiContent.md and docs/*.md separately. Compare the rendered API landing page with the Documentation view; done means landing-page Markdown appears while the existing title banner and Documentation / Try with AI buttons remain usable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- markdown
- Domain
- api, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100