Sitemap of the betkwiff editorial publication.

The editorial hubs are the publication's six longform desks: games, how to play, strategy, reviews, safety, and . Each hub is a longform piece — 1,500 to 3,000 words — that opens a topic and links to the related coverage across the publication. A reader who arrives at the games hub should be able to find the rules in how to play, the strategy limits in strategy, the platform usability in reviews, the payment rails in safety, and the recent state-level shifts in news.

The hub map is not a content tree — it is a list of the trunks that the desk's coverage grows from. A reader who wants to read the publication end-to-end can start at the games hub and follow the links across the publication in any order; the hubs are designed to be read in any order, and the desk's editorial position is that a reader who reads the desk in any order gets a complete picture of the ecosystem as the desk sees it.

The support pages below the hubs are the desk's editorial back-office: responsible play, is rummy legal?, customer care, and wallet and KYC. The company pages below the hubs are the desk's about-pages: about the desk, who operates betkwiff, contact, terms, and privacy. The news desk below the hubs is the rolling thread of state-rules, KYC and platform-usability updates.

The XML version of the sitemap is at /sitemap.xml. The XML version is the canonical sitemap for search engines and is generated from the publication's editorial set on a quarterly cadence. The XML version reflects the same set of pages as the human-readable sitemap on this page; pages that are not in the editorial set are not in the XML version. The XML version includes last-modified timestamps for each page, which allows a search engine to prioritise recent updates.

The XML version is not a substitute for the human-readable sitemap on this page. The human-readable sitemap is grouped by editorial hub, support page, company page and news thread; the XML version is a flat list with last-modified timestamps. Readers who want to navigate the publication should use the human-readable sitemap; search engines should use the XML version.

The XML version is updated whenever a new page is published, whenever a page is corrected, and whenever a page is retired. Retired pages remain in the XML version for a grace period of 90 days after retirement, with a "noindex" robots directive appended to the page; after the grace period, the page is removed from the XML version and the canonical URL returns a 410 Gone response. The desk's editorial position is that retired pages should be retired cleanly, with a visible note and a 410 response, rather than silently redirected.

The is the publication's rolling thread of state-rules, KYC, and platform-usability updates. The news desk is filed under the regulation editor's byline and is reviewed by the desk's regulation editor before publication. The news pieces are 200–800 words and are linked to the primary source where the source is public; secondary sources are quoted and attributed. The news desk is not a wire feed; news pieces are original editorial work and are filed under a byline.

The editorial calendar is internal and is not published. Readers who want to be notified when a new long-read is filed can subscribe to the RSS feed. The RSS feed is updated at the time of publication and includes the masthead, the section number, and the byline. The RSS feed is the desk's primary distribution channel; the desk does not currently use email newsletters or social media distributions.

The desk's editorial position on the news desk is unchanged: the news desk is editorial, not promotional. A news piece is not a sponsored placement; a news piece is not a review; a news piece is a desk-filed file on a topic the desk has decided to cover. Readers who want to send a news tip can use the contact page with the subject line "News tip"; the desk reads every tip and acknowledges receipt within five working days.

The editorial calendar is roughly twelve weeks per issue. Each issue opens with a planning note that lists the long-reads, news pieces and re-tests for the issue; the planning note is internal and is not published. The desk publishes a quarterly summary of what the desk covered in the issue, the topics the desk decided to defer, and the topics the desk decided to retire. The quarterly summary is filed as a desk-note on the and is linked from the publication's RSS feed.

The quarterly summary also includes a list of corrections filed in the issue. The corrections log is a desk-filed file on every correction made to a published page in the issue, with the date, the page, the original sentence, and the corrected sentence. The corrections log is a public file and is linked from the bottom of every page on the publication. The desk's editorial position is that the corrections log is part of the publication, and the log is as much a part of the publication's editorial line as the long-reads themselves.

The publication's editorial set is curated by the desk. The set is not exhaustive of the Indian rummy ecosystem; the set is the part of the ecosystem the desk has decided to cover. A reader who wants to find coverage of a topic the desk has decided to defer can use the contact page to suggest a topic; the desk reads every suggestion and acknowledges receipt within five working days. The desk's editorial position on suggestions is that the desk considers every suggestion but reserves the right to defer or refuse coverage without explanation.

The publication's editorial set is grouped by hub, support, company and news. The grouping is editorial, not technical: the grouping reflects the desk's view of the publication's coverage, and the grouping is what a reader sees in the masthead and the homepage index rail. The grouping is not a list of sections in a content management system; the grouping is a manifest of the desk's editorial scope. The grouping is reviewed at the end of each issue and adjusted as the editorial set evolves.

The publication's editorial set has grown since the first issue. The first issue covered the legal-infrastructure side of paid rummy in India, a state-by-state notes file, a usability stack of the platforms a reader was most likely to encounter, and a long-read on the strategy limits of skill-game play. The current issue covers the same scope, with a quarterly re-test of the platforms in the reviews stack and a rolling news thread on state-rules, KYC and platform-usability shifts. The desk's editorial position is that the publication's editorial set should grow slowly, and the desk should be able to defend any new addition against the question of why the publication is the right place for the coverage.

The publication is designed to be read in any order, but a reader who wants a complete picture of the Indian rummy ecosystem as the desk sees it should start with the is rummy legal? hub, then the games hub, then the how to play hub. The legal hub sets the regulatory frame; the games hub names the formats a reader is most likely to encounter on a paid platform; the how-to-play hub names the sequence, set, joker, drop, and show mechanics that every format is built on. Together, the three hubs give a reader enough vocabulary to read the strategy hub, the reviews hub, and the news desk without having to look up a term mid-read.

A reader who has played a few formats and wants to push past the basics should jump to the strategy hub and the reviews hub. The strategy hub is where the desk files its limits on skill-game play: which decisions are math, which decisions are read, and which decisions are noise. The reviews hub is where the desk files its quarterly re-tests of the platforms in the stack, with a focus on payment rails, customer-care reachability, and the friction a real reader encounters at signup, deposit, and withdrawal. The two hubs are designed to be read together: a strategy reader who hasn't read the reviews will end up re-discovering the same platform limits in a different vocabulary.

A reader who wants to keep up with the live state of the ecosystem should subscribe to the RSS feed and read the weekly. The news desk is the desk's filing channel for state-rules shifts, KYC standard changes, and platform-usability incidents that are reported by readers and verified by the desk. The desk's editorial position is that the news desk is the part of the publication where the desk's reporting shows up first; a reader who reads the news desk weekly will read the long-reads later with the right context.

A reader who is about to open a real-money account anywhere on the Indian rummy stack should read the responsible play page, the wallet & KYC page, and the customer care page before the first deposit. The responsible play page is the desk's editorial position on boundaries, controls, and helplines. The wallet & KYC page is the desk's notes on verification, deposit, and withdrawal friction. The customer care page is the desk's notes on how to reach a real person on a paid platform, and what to expect from the reply when one arrives.

The publication's editorial set is small on purpose. The desk's editorial position is that a small, well-curated editorial set is more useful to a reader than a large one. A reader who reads the hubs in the order above will end up with a complete picture of the ecosystem as the desk sees it. A reader who reads only the news desk will miss the longform context that the news desk is written against. A reader who reads only the longform hubs will miss the live state-rules shifts that the longform hubs are written against. The publication is designed to reward the reader who reads all of it; the publication does not pretend to reward the reader who reads only part of it.