Skip to content

Documentation for Next-Gen SDK support#6510

Open
postindustria-code wants to merge 7 commits intoprebid:masterfrom
postindustria-tech:google_next_gen_sdk_support
Open

Documentation for Next-Gen SDK support#6510
postindustria-code wants to merge 7 commits intoprebid:masterfrom
postindustria-tech:google_next_gen_sdk_support

Conversation

@postindustria-code
Copy link
Copy Markdown

  • Add documentation for prebid-rendering integration
  • Add documentation for original api integration

Documentation for the feature release prebid/prebid-mobile-android#925

🏷 Type of documentation

  • new bid adapter
  • update bid adapter
  • new feature
  • text edit only (wording, typos)
  • bugfix (code examples)
  • new examples

📋 Checklist

  • Related pull requests in prebid.js or server are linked -> Paste link in this list or reference it on the PR itself
  • For new adapters check submitting your adapter docs

- Add documentation for prebid-rendering integration
- Add documentation for original api integration
@netlify
Copy link
Copy Markdown

netlify bot commented Mar 30, 2026

Deploy Preview for prebid-docs-preview ready!

Name Link
🔨 Latest commit 9353c92
🔍 Latest deploy log https://app.netlify.com/projects/prebid-docs-preview/deploys/69ca9f16e990820009d33ac7
😎 Deploy Preview https://deploy-preview-6510--prebid-docs-preview.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@postindustria-code
Copy link
Copy Markdown
Author

postindustria-code commented Mar 30, 2026

I had to disable MD058 rule as it's conflicting with the current Kramdown IAL syntax. This rule requires a blank line before every table, while IAL must be placed directly adjacent to its target block - inserting a blank line between it and the table breaks the styling. HTML disable comments () were also considered, but Kramdown parses them as block-level elements, which breaks table rendering entirely. Existing files follow the same pattern for tables.

Is it fine, or should we consider a better solution?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant