mlevkov opened a new pull request, #41:
URL: https://github.com/apache/iggy-website/pull/41

   ## Summary
   
   - Adds `content/docs/connectors/sinks/http.mdx` (~179 lines) — a curated 
subset of the upstream 
[`core/connectors/sinks/http_sink/README.md`](https://github.com/apache/iggy/tree/master/core/connectors/sinks/http_sink),
 with a `<Callout>` at the top pointing readers back to the canonical README 
for the full surface.
   - Inserts `"http"` in `content/docs/connectors/sinks/meta.json` between 
`iceberg` and `stdout` so the sidebar reflects the new page.
   - Adds `Generic HTTP` to the Sink row of the Available Connectors table in 
`content/docs/connectors/introduction.mdx`.
   
   Naming and content-scope decisions (file slug, page title, table cell 
wording, what to include vs. summarize-and-link) are documented in #39, 
including the rationale for `Generic HTTP` (vs. plain `HTTP`) — the qualifier 
disambiguates a transport-level connector from the several sinks that already 
speak HTTP under the hood (Elasticsearch, Quickwit).
   
   ## Test plan
   
   - [x] `npm run build` passes locally — 77/77 static pages generated, no 
MDX/TS errors
   - [x] `/docs/connectors/sinks/http` renders at HTTP 200 with all expected 
section headings (Configuration, Configuration Options, Batch Modes, Metadata 
Envelope, Authentication, Retry & Delivery Semantics, Example Configurations, 
Deployment & Performance, Known Limitations)
   - [x] `/docs/connectors/introduction#available-connectors` shows `Apache 
Iceberg, Generic HTTP, Stdout` in the Sink row
   - [x] Sidebar on any `sinks/*` page lists the new entry between `iceberg` 
and `stdout`
   - [x] Fumadocs `<Callout type="info">` renders at the top of the new page
   
   Closes #39
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to