Skip to content

docs: add monetization guide - #15

Open
resenhadobar wants to merge 2 commits into
Jaabaali:mainfrom
resenhadobar:codex/monetization-docs
Open

resenhadobar wants to merge 2 commits into
Jaabaali:mainfrom
resenhadobar:codex/monetization-docs

Conversation

@resenhadobar

Copy link
Copy Markdown

What does this change?

Adds the supplied “Add Jabali Ads to Your Game” document as a Monetization page, covering placement practices, Bali prompts, Preview testing, and published-game verification. Preserves the document's content with Markdown formatting, adds a sidebar entry, and links to the guide from the publishing page.

Validation

  • npm run build passed: 51 pages built and all internal links valid.
  • git diff --check passed.
  • Checked the generated HTML for all five Bali prompt blocks.

Checklist

  • Every new or changed page has a title and a description (50–160 characters)
  • Images have alt text that describes the screenshot (no images added)
  • Internal links start with /docs/ and end with /
  • It documents features that are already released — maintainer to confirm availability of the supplied monetization workflow
  • I previewed the change (checked generated HTML)

@qodo-code-review

Copy link
Copy Markdown

PR Summary by Qodo

Document how to add and verify Jabali ads

📝 Documentation 🕐 10-20 Minutes

Grey Divider

AI Description

• Add a monetization guide covering ad placement, Bali prompts, and SDK integration.
• Explain how to verify rewards and gameplay recovery in Preview and after publishing.
• Link the guide from the Studio sidebar and publishing page.
Diagram

graph TD
  Sidebar["Studio sidebar"] --> Guide["Monetization guide"] --> Placement["Choose placement"] --> Bali["Ask Bali"] --> Preview["Verify Preview"] --> Published["Verify published game"]
  Publish["Publishing page"] --> Guide
Loading
High-Level Assessment

A dedicated guide linked from the existing navigation and publishing page is appropriate: it keeps detailed monetization instructions separate from the general publishing workflow. No SDK or application change is needed for this documentation PR; maintainers should confirm that the documented controls and workflow are released.

Files changed (3) +120 / -0

Documentation (3) +120 / -0
astro.config.mjsAdd Monetization to the Studio sidebar +1/-0

Add Monetization to the Studio sidebar

• Registers the new guide under Build your game, immediately after the publishing page.

astro.config.mjs

monetization.mdDocument Jabali ad setup and verification +118/-0

Document Jabali ad setup and verification

• Adds placement practices and five Bali prompts for evaluating, implementing, and testing ads. Provides separate Preview and published-game checklists covering rewards, cooldowns, dismissal, and gameplay recovery.

src/content/docs/studio/monetization.md

publish.mdLink publishing guidance to monetization +1/-0

Link publishing guidance to monetization

• Adds the monetization guide to the publishing page’s related links.

src/content/docs/studio/publish.md

@qodo-code-review

qodo-code-review Bot commented Nov 10, 2026 •

Copy link
Copy Markdown

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0) 🔗 Cross-repo conflicts (0) 📜 Skill insights (0)

Grey Divider


Remediation recommended

1. Monetization guide goes live for a feature not yet confirmed 🐞 Bug ≡ Correctness
Description
The new sidebar entry in astro.config.mjs and the Related pages link in publish.md make the
guide studio/monetization reachable from the public navigation. The PR's own checklist leaves the
item 'documents features that are already released' unchecked, so the guide can describe Preview
monetization and the Jabali SDK workflow to users before that workflow is available.
Code

astro.config.mjs[119]

+						'studio/monetization',
Evidence
The sidebar addition at line 119 publishes the page in navigation, and publish.md line 70 links to
it from an existing page. The PR description states that the availability of the supplied
monetization workflow is still unconfirmed, so the public docs would advertise an unreleased
capability. Keep the page out of the sidebar and the publish link until a maintainer confirms the
feature is released.

astro.config.mjs[119-119]
src/content/docs/studio/publish.md[70-70]

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

Issue description
The PR adds a public sidebar entry and a Related pages link to a monetization guide, but its checklist says the documented Jabali ads workflow has not been confirmed as released. Public navigation would expose instructions for an unavailable feature.

Fix Focus Areas
- astro.config.mjs[116-120]
- src/content/docs/studio/publish.md[68-72]

Recommended Fix
Either get maintainer confirmation of availability before merging, or defer the sidebar entry in astro.config.mjs and the Related pages link in publish.md until the feature ships. The page itself can remain on a draft or unlisted path.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Dismiss ↗ | View ↗



Informational

2. Published-game test step relies on undefined 'approved test delivery' ✓ Resolved

Resolving commit: fba9dc0

Resolution reason
Removed the undefined phrase 'using approved test delivery' from the published-game testing step, so
the step no longer references an undefined mechanism. It does not link to a test-delivery page or
state the mechanism explicitly, so it is a different (removal-based) resolution than the suggested
fix.
Description
Section 4 instructs readers to verify completion, dismissal and rewards 'using approved test
delivery' without defining what that is or how to obtain it. Readers following the published-game
checklist cannot tell how to trigger ads on the live player page in a way that is permitted for
testing, so the verification step is not actionable.

Grey Divider

Context sources
✅ Cross-repo context — repo relationships
✅ REVIEW.md
Review mode: Auto: 🚀 Fast: Docs-only page plus a one-line sidebar and link addition; localized, low risk.

Grey Divider

Tip of the day
💡 Did you know, you can import rules and skills only from the repositories your team follows

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

Grey Divider

Qodo Logo

Comment thread astro.config.mjs
'studio/design-and-polish',
'studio/version-history',
'studio/publish',
'studio/monetization',

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remediation recommended

1. Monetization guide goes live for a feature not yet confirmed 🐞 Bug ≡ Correctness

The new sidebar entry in astro.config.mjs and the Related pages link in publish.md make the
guide studio/monetization reachable from the public navigation. The PR's own checklist leaves the
item 'documents features that are already released' unchecked, so the guide can describe Preview
monetization and the Jabali SDK workflow to users before that workflow is available.
Agent Prompt
Issue description
The PR adds a public sidebar entry and a Related pages link to a monetization guide, but its checklist says the documented Jabali ads workflow has not been confirmed as released. Public navigation would expose instructions for an unavailable feature.

Fix Focus Areas
- astro.config.mjs[116-120]
- src/content/docs/studio/publish.md[68-72]

Recommended Fix
Either get maintainer confirmation of availability before merging, or defer the sidebar entry in astro.config.mjs and the Related pages link in publish.md until the feature ships. The page itself can remain on a draft or unlisted path.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Dismiss ↗ | View ↗

Comment thread src/content/docs/studio/monetization.md Resolved

This branch has not been deployed

No deployments
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