Conversation
Read-only findings from the static marketing repo and live ojapos.app / ojapos.ng. No product rewrite and no deploy. Co-authored-by: Jamiu Awoke <Vanka07@users.noreply.github.com>
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Review-doc only. No product rewrite, no copy fix, no deploy.
REVIEW.mdmaps every page, the pricing copy, every CTA, and the only payment-shaped file (payment-callback.html). Rechecked liveojapos.app/ojapos.ngon 2026-08-24 against the 2026-08-23 facts.Headline: this repo is a static Vercel brochure. All “Try Free / Start Free Trial” buttons go to
https://app.ojapos.appwith no plan or checkout. There is no billing stack here.Confirmed live:
/docsis a Vercel 404; no docs file exists.Wired vs marketing: the Paystack callback is an optimistic UI stub (any
reference/trxref→ “Business plan activated”).catalog.htmlis a client-side hash renderer. Real signup/upgrade would be in the separate Expo app, which this review did not audit.Did not change landing HTML. The FAQ/pricing conflict needs an entitlements source of truth before a copy patch.