Right to Information Wiki - about

Who are Community Builders at RTI INDIA

anonymous@undisclosed.example.com (Anonymous) — Wed, 22 Apr 2026 06:36:07 +0000

2015/05/30 00:40		current
Line 1:		Line 1:
	====== Who are Community Builders at RTI INDIA ======		====== Who are Community Builders at RTI INDIA ======
-	{{http://www.rtiindia.org/forum/images/misc/community_builder.gif }}	+	{{ :social:auto:about-community-builders.png?direct&1200 \|about / community-builders — RTI Wiki}}
		+
		+	{{htmlmetatags>metatag-keywords=(about community builders rti right to information india)
		+	metatag-description=(RTI INDIA community is where people of all ages can participate and obtain information from each other.)}}
		+
		+
		+	{{http://www.rtiindia.org/forum/images/misc/community_builder.gif\|Community builder}}

	RTI INDIA community is where people of all ages can participate and obtain information from each other. Our Community is a vibrant and wonderful places to learn, collaborate, and engage directly into conversations. The RTI INDIA is built around social connection. Our’s is a place where like-minded individuals can meet, express an opinion, and engage in conversation.		RTI INDIA community is where people of all ages can participate and obtain information from each other. Our Community is a vibrant and wonderful places to learn, collaborate, and engage directly into conversations. The RTI INDIA is built around social connection. Our’s is a place where like-minded individuals can meet, express an opinion, and engage in conversation.
Line 67:		Line 73:

	We hope to see you soon as part of our Team :)		We hope to see you soon as part of our Team :)
		+
		+	[<>]
		+
		+
		+	===== Related =====
		+
		+	* [[:about:workshop\|Right to Information Wiki Workshop]].
		+	* [[:about:posting-at-other-threads\|Why You Should Start a New Thread]].
		+	* [[:about:rti-team\|What is RTI Wiki]].
		+	* [[:about:what-is-rti-wiki\|What makes RTI Wiki so good for Documentation?]].
		+	* [[:user:shrawan\|Shrawan]].
		+
		+	//Last reviewed on: 20 April 2026//
		+
		+	{{tag>rti meta about}}
		+

Editor

anonymous@undisclosed.example.com (Anonymous) — Wed, 22 Apr 2026 06:36:07 +0000

2026/04/22 09:04	current
Line 1:	Line 1:
	+	{{htmlmetatags>metatag-keywords=(editor rti wiki,shrawan rti wiki,about rti wiki editor,rti wiki author,rti wiki masthead)&metatag-description=(Shrawan is the editor of RTI Wiki. Background, credentials, editorial principles, and the review cycle under which every page on the site is maintained.)}}
	+
	+	====== Editor =====
	+
	+	{{ :social:auto:about-editor.png?direct&1200 \|about / editor — RTI Wiki}}
	+
	+	//Last reviewed: 20 April 2026//
	+
	+	===== Shrawan =====
	+
	+	Shrawan is the editor of RTI Wiki. The site is an open, practitioner-ready reference on India's Right to Information Act, 2005, maintained in the register of a Department of Personnel and Training or Central Information Commission bench-book.
	+
	+	Credentials and background. Public-policy research on access-to-information law since 2011. Contributed to applicant-side briefs at the Central Information Commission. Long-running editorial interest in administrative law, right-to-know jurisprudence, and open government.
	+
	+	Editorial focus. Legislative changes to the RTI Act and allied rules, Supreme Court and High Court decisions on access-to-information, Information Commission practice, and the interplay with the Digital Personal Data Protection Act, 2023 (in force 14 November 2025).
	+
	+	===== Editorial principles =====
	+
	+	- Current. Every page carries a "Last reviewed on" line. Pages on evolving law (the Act, the Rules, case pages) are reviewed at least once a quarter. Pages are reviewed immediately after any amendment or binding judgment.
	+	- Sourced. Every factual claim on this site carries a citation to the statute, rule, circular, judgment, or Commission order that supports it. Case citations use the standard form ((2013) 1 SCC 212, etc.) and link to the on-site case page or a verified reporter.
	+	- Usable. Every guide closes with a template, a checklist, or a specific next step. A page that does not leave the reader in a position to act is a page that has not done its job.
	+	- Neutral. Third-person, British-Indian spelling. The site is not a law firm. No legal advice is offered. Advocacy positions, where taken (for example, the editorial on the DPDP 2025 amendment), are labelled as editorial.
	+	- Transparent on mistakes. Corrections are logged on the affected page and, for material errors, acknowledged at the top of the relevant entry with the date of correction.
	+
	+	===== Review cycle =====
	+
	+	* Daily. New judgments, Commission notifications, Gazette entries are monitored. Time-sensitive updates (for example, DPDP Rules notification) land within twenty-four hours.
	+	* Weekly. A rolling audit of the ten most-viewed pages against current law.
	+	* Quarterly. A full namespace audit (act, rules, guide, important-decisions, templates).
	+	* Annual. A complete restatement of the top-level guides.
	+
	+	===== Contact =====
	+
	+	Editorial contact and corrections: through the [[https://righttoinformation.wiki/feedback.php\|feedback widget]] at the bottom of any page, the [[https://righttoinformation.wiki/bookmarks.php\|saved-articles page]] (logged-in users), or by email to the publisher at admin@bighelpers.in.
	+
	+	===== Related pages =====
	+
	+	* [[:about:editorial-policy\|Editorial policy — sources, verification, corrections]].
	+	* [[:press:media-kit\|Press and media kit]].
	+	* [[https://righttoinformation.wiki/stats.php\|Site statistics]].
	+
	+	===== Last reviewed on =====
	+
	+	20 April 2026
	+
	+	{{tag>meta editor about rti-wiki}}

Editorial policy

anonymous@undisclosed.example.com (Anonymous) — Wed, 22 Apr 2026 06:36:07 +0000

2026/04/22 09:04	current
Line 1:	Line 1:
	+	{{htmlmetatags>metatag-keywords=(editorial policy rti wiki,rti wiki sources,rti wiki corrections,rti wiki review cycle,rti wiki accuracy)&metatag-description=(The editorial policy of RTI Wiki. How sources are verified, how pages are dated, how corrections are handled, and how conflicts of interest are disclosed.)}}
	+
	+	====== Editorial policy =====
	+
	+	{{ :social:auto:about-editorial-policy.png?direct&1200 \|about / editorial-policy — RTI Wiki}}
	+
	+	//Last reviewed: 20 April 2026//
	+
	+	This page describes how RTI Wiki is edited, sourced, reviewed, and corrected. It applies to every page on the site.
	+
	+	===== Sources =====
	+
	+	Every factual claim on the site carries a citation. Citations draw from, in order of preference:
	+
	+	- The statute itself. The Right to Information Act, 2005; the RTI (Amendment) Act, 2019; the Digital Personal Data Protection Act, 2023; the RTI Rules, 2012; the RTI Fee Rules, 2005; State RTI Rules; the DPDP Rules, 2025.
	+	- Binding judgments. Supreme Court of India decisions cited in the standard form ((2013) 1 SCC 212). High Court decisions cited by writ number and date of decision.
	+	- Central Information Commission and State Information Commission orders. Cited by decision number, date, and decided-by bench.
	+	- Government circulars and Office Memoranda. Department of Personnel and Training OMs, Ministry notifications.
	+	- Academic commentary. Treatises and peer-reviewed work are cited only where the original primary source is also cited.
	+
	+	Service-provider websites, commercial filing portals, and news outlets are used only to cross-reference a primary source that is already on the page.
	+
	+	===== Verification =====
	+
	+	* First draft. Every new page is drafted against the primary statute and the leading case.
	+	* Legal fact-check. Every case citation is checked against the original reporter. Every section reference is checked against the current text of the Act.
	+	* Dated review. Every page carries a "Last reviewed on" line. The date is updated only when the page has been re-read end to end against current law.
	+	* Snapshot link. Where a page cites an external URL that is prone to link-rot, a snapshot date is given.
	+
	+	===== Corrections =====
	+
	+	Corrections are public. On pages where a material error has been corrected, the following is added at the top of the affected section:
	+
	+	> Correction, {date}. {one-line description of the error, the fix, and the source that justified the change.}
	+
	+	Minor corrections (typos, spelling, formatting) are not logged individually. Substantive corrections — to a section reference, a case citation, a procedural step, a timeline, or a legal position — are always logged.
	+
	+	Readers may submit corrections through the [[https://righttoinformation.wiki/feedback.php\|feedback widget]] at the bottom of every page. The editor acknowledges every correction received.
	+
	+	===== Conflicts of interest =====
	+
	+	The editor does not offer paid legal services, does not file RTIs on behalf of clients, and does not take advertising from any entity with a stake in the outcome of an RTI proceeding.
	+
	+	The site carries contextual advertising (Google AdSense). Ad placement is site-wide and not article-specific. Advertisers do not have editorial input.
	+
	+	Where the editor has personal involvement in a matter discussed on the site, that involvement is disclosed on the page itself.
	+
	+	===== Licensing =====
	+
	+	Content on this site is published under GFDL 1.3 unless otherwise marked. Citations from statutes and official sources carry their original copyright. Case-law excerpts are used under the common-law doctrine of fair use for commentary and review.
	+
	+	Reuse is welcomed. See the [[:press:media-kit\|media kit]] for citation guidelines.
	+
	+	===== Related pages =====
	+
	+	* [[:about:editor\|About the editor]].
	+	* [[:press:media-kit\|Press and media kit]].
	+
	+	===== Last reviewed on =====
	+
	+	20 April 2026
	+
	+	{{tag>meta editorial-policy about rti-wiki}}

Editorial Review — Reviewer Onboarding

anonymous@undisclosed.example.com (Anonymous) — Wed, 22 Apr 2026 03:38:15 +0000

2026/04/22 09:04	current
Line 1:	Line 1:
	+	{{htmlmetatags>metatag-keywords=(rti wiki editorial review,retired ic reviewer,rti wiki editorial board,rti content review,editorial process rti)&metatag-description=(RTI Wiki's editorial-review process and how retired Information Commissioners and senior advocates join as reviewers. Scope, commitment, and contact.)}}
	+
	+	====== Editorial Review — Reviewer Onboarding ======
	+
	+	{{page>_snippets:dpdp-banner}}
	+
	+	<WRAP center round info 95%>
	+	RTI Wiki is looking for retired Information Commissioners and senior RTI advocates to join our editorial-review panel. The commitment is light (one sitting per quarter, 30-45 minutes). The contribution is decisive — you tighten our factual accuracy and catch errors before citizens rely on them.
	+	</WRAP>
	+
	+	===== Why RTI Wiki reviews content =====
	+
	+	This site is used by citizens filing their first RTI, by Public Information Officers training in their role, and by First Appellate Authorities drafting reasoned orders. A wrong fee rate, a stale case citation, a superseded clause — each can cause a citizen to miss a deadline or a PIO to sign an appealable order.
	+
	+	We already:
	+
	+	* Verify every published article — a green "Verified" badge appears at the top of the page, backed by the entry in ''conf/verified.json''.
	+	* Cite statute and case law — every ground, exemption, and procedural claim links to the Act section and the binding authority.
	+	* Link to primary sources — CIC orders, SC and HC judgements (via India Kanoon or the court's own portal).
	+	* Track last-reviewed date — visible at the bottom of every article; auto-emitted as `dateModified` in the article's schema.org JSON-LD.
	+
	+	What we do not yet have — independent editorial oversight by people who wrote the rulings, drafted the orders, and appeared in the appeals that shape Indian RTI practice. That is what this panel is for.
	+
	+	===== Who we are looking for =====
	+
	+	* Retired Central or State Information Commissioners — any tenure, any jurisdiction.
	+	* Senior RTI advocates — at least ten years of pleaded RTI appeals in the High Courts or the Commissions.
	+	* Retired Public Information Officers at senior rank — Joint Secretary / Commissioner-level, with a substantive RTI docket history.
	+	* Retired Secretaries / Additional Secretaries who administered Section 4 disclosures.
	+	* Academics specialising in transparency law — tenured faculty with published work on the RTI Act or comparative information-rights regimes.
	+
	+	===== What the commitment looks like =====
	+
	+	==== Quarterly sitting ====
	+
	+	* Frequency. Once per quarter (four times a year).
	+	* Duration. 30 to 45 minutes.
	+	* Format. Video call (Zoom / Google Meet) or a written exchange — whichever the reviewer prefers.
	+	* Agenda. The editor brings 5-10 articles that have been updated since the last sitting. The reviewer flags any factual error, stale citation, or tonal issue. The editor takes the note and fixes.
	+
	+	==== Topic-specific review ====
	+
	+	We may also reach out for a single-article review when the article concerns the reviewer's specialism. Example: an article on PIO procedure under Section 7 might be sent to a retired Information Commissioner who decided many §7(8)(i) matters. A single-article review is usually 15-20 minutes, written.
	+
	+	==== No ghostwriting expected ====
	+
	+	Reviewers do not draft content. The editor drafts; the reviewer flags errors or suggests sharper framing. All edits are the editor's responsibility.
	+
	+	===== What reviewers receive =====
	+
	+	* Public acknowledgement. Reviewers are listed on the Editorial Board page with their designation and tenure — opt-out on request.
	+	* A direct line to the editor. Feedback loops are fast; corrections typically go live within 48 hours.
	+	* Citation credit. Articles a reviewer has substantively shaped carry a small footnote: "Reviewed by [Name], former Chief Information Commissioner, [State]."
	+	* Copies of updates. Reviewers receive a quarterly digest of what changed, for their own records.
	+	* No honorarium or fee (the site runs on ad revenue and is not a commercial publication). We offer this as public-interest volunteer work.
	+
	+	===== What RTI Wiki is not =====
	+
	+	* Not a news outlet. We cover the Act, not daily headlines. We archive significant CIC orders and landmark court rulings; we do not report on breaking news.
	+	* Not a litigation service. Our tools (Generator, First Appeal Builder, PIO Reply Checker, Question Builder) assist the citizen to draft their own application or appeal. They do not file on anyone's behalf.
	+	* Not a partisan platform. Reviewers from across the political spectrum are welcome, so long as the feedback is factual and procedural.
	+
	+	===== Our editorial principles =====
	+
	+	- Statute first, case-law second, commentary last. Every claim cites either a section of the Act, a binding judgement, or a published CIC order. Opinion is clearly marked.
	+	- No "why" questions in sample RTIs. We teach citizens to ask for records, not answers. See our drafting guide at [[:blog:how-to-write-rti-application\|Ask for records, not answers]].
	+	- Case-law currency. After every significant SC / HC ruling, we update the relevant articles within a week.
	+	- Plain-language rule. We aim for a ninth-standard reading level on citizen-facing pages. Legal-practitioner pages (PIO framework, FAA checklist) are written for the trained reader.
	+	- DPDP-compliant privacy. We follow the Digital Personal Data Protection Act, 2023 and the 2025 Rules. See our [[:privacy-policy\|Privacy Policy]].
	+
	+	===== Our commitment to corrections =====
	+
	+	* Response within 24 hours for any substantive correction notice.
	+	* Fix within 48 hours when the correction is clearly supported by source.
	+	* Credit (on request) in the article's footer: "Correction by [Name], [date]".
	+	* Public changelog. See [[:corrections\|corrections page]] for reporting errors and the SLA.
	+
	+	===== How to join =====
	+
	+	Write to [[mailto:admin@bighelpers.in\|admin@bighelpers.in]] with the subject line "Editorial Review — Interest" and a short note:
	+
	+	* Your role(s) in RTI practice over the last ten years.
	+	* Your specialism (e.g. Section 8 case law, police records, service records, forest rights, scheme-specific).
	+	* Whether you are available for quarterly sittings, single-article reviews, or both.
	+	* Whether you are comfortable with public acknowledgement on the Editorial Board page.
	+
	+	The editor will reply within three working days.
	+
	+	===== Current editorial stack =====
	+
	+	* Editor. Shrawan Pathak. Contact: [[mailto:admin@bighelpers.in\|admin@bighelpers.in]].
	+	* Verified articles. Around 190 pages carry the green "Verified" badge, reflecting editor-level review.
	+	* Review cadence. //Last reviewed// dates are published on every article.
	+	* Editorial calendar. Quarterly reviewer sittings are planned from Q2 2026.
	+
	+	===== Related pages =====
	+
	+	* [[:about:editorial-policy\|Editorial Policy]]
	+	* [[:about:what-is-rti-wiki\|What is RTI Wiki?]]
	+	* [[:corrections\|Report a correction]]
	+	* [[:about:editor\|Editor — Shrawan Pathak]]
	+	* [[:privacy-policy\|Privacy Policy]]
	+
	+	----
	+
	+	//Last reviewed: 21 April 2026.//
	+
	+	{{tag>about editorial-review reviewer-onboarding editorial-board}}

Why You Should Start a New Thread

anonymous@undisclosed.example.com (Anonymous) — Wed, 22 Apr 2026 06:36:07 +0000

2015/05/24 15:54		current
Line 1:		Line 1:
	====== Why You Should Start a New Thread ======		====== Why You Should Start a New Thread ======
		+
		+	{{ :social:auto:about-posting-at-other-threads.png?direct&1200 \|about / posting-at-other-threads — RTI Wiki}}
		+
		+	{{htmlmetatags>metatag-keywords=(about posting at other threads rti right to information india)
		+	metatag-description=(RTI INDIA has forums and each forum contains threads and each thread has posts. Forums can be considered as categories, threads as the topic and the posts as...)}}
		+

	RTI INDIA has forums and each forum contains threads and each thread has posts. Forums can be considered as categories, threads as the topic and the posts as the discussions on the topics. A registered member starts a new thread when he intends to ask a question or start a conversation on the topic he is interested into. Once he creates a new thread (Topic), other members poll in and respond to that discussions by making a posts.		RTI INDIA has forums and each forum contains threads and each thread has posts. Forums can be considered as categories, threads as the topic and the posts as the discussions on the topics. A registered member starts a new thread when he intends to ask a question or start a conversation on the topic he is interested into. Once he creates a new thread (Topic), other members poll in and respond to that discussions by making a posts.
Line 18:		Line 24:
	* But worst is that when a user pile upon the other thread simply because he thinks that there are chances of his getting attention to his topic.		* But worst is that when a user pile upon the other thread simply because he thinks that there are chances of his getting attention to his topic.

		+	~~DISCUSSION~~
		+
		+
		+	===== Related =====
		+
		+	* [[:about:workshop\|Right to Information Wiki Workshop]].
		+	* [[:about:rti-team\|What is RTI Wiki]].
		+	* [[:about:what-is-rti-wiki\|What makes RTI Wiki so good for Documentation?]].
		+	* [[:about:community-builders\|Who are Community Builders at RTI INDIA]].
		+	* [[:user:shrawan\|Shrawan]].
		+
		+	//Last reviewed on: 20 April 2026//
		+
		+	{{tag>rti meta about}}

Quarterly Editorial Audit — Top-30 Pages

anonymous@undisclosed.example.com (Anonymous) — Tue, 21 Apr 2026 12:49:48 +0000

2026/04/22 09:04	current
Line 1:	Line 1:
	+	{{htmlmetatags>metatag-keywords=(rti wiki quarterly audit,editorial audit process,rti wiki review schedule,content audit process 2026)&metatag-description=(Quarterly editorial audit schedule for RTI Wiki — which top-30 pages are reviewed when, who reviews, and what counts as a pass.)}}
	+
	+	====== Quarterly Editorial Audit — Top-30 Pages ======
	+
	+	{{page>_snippets:dpdp-banner}}
	+
	+	<WRAP center round info 95%>
	+	Every quarter, RTI Wiki audits its top-30 most-visited pages. The audit confirms that statutory citations are current, case law has not been overturned, amendments are reflected, and internal links resolve. The findings are published on this page; page-level corrections are committed within 10 working days of the audit.
	+	</WRAP>
	+
	+	Part of [[:about:editorial-review\|Editorial Review]].
	+
	+	===== What the audit checks =====
	+
	+	Every audited page goes through this 10-point checklist:
	+
	+	- Section citations. Every §N reference points to a section that still exists and has the same meaning.
	+	- Case-law currency. Cited cases have not been overturned; if refined by later judgement, the refinement is noted.
	+	- DPDP 2025 reflection. Pages touching §8(1)(j) carry the post-14-November-2025 framework.
	+	- Fee rates. Central Rs. 10 / state-specific rates match the rule as of audit date.
	+	- Portal URLs. Central and state RTI portals open; any renamed portal is updated.
	+	- First-appeal / second-appeal timelines. 30 days / 90 days references are consistent.
	+	- Broken internal links. All `[[:slug]]` targets resolve to live pages.
	+	- Anchor-text hygiene. No "click here", "read more", or placeholder anchors.
	+	- Schema.org validity. Article, FAQPage, HowTo, and BreadcrumbList schemas are well-formed and match page content.
	+	- Accessibility. All images carry descriptive alt text; H1 is unique; form inputs have labels.
	+
	+	===== Audit cadence =====
	+
	+	* Q1 — January audit. Post-Republic Day; refreshes pages ahead of the tax / result season.
	+	* Q2 — April audit. Post-fiscal-year; catches new state rules; CIC annual report typically releases around this window.
	+	* Q3 — July audit. Mid-monsoon; post-Budget-Session updates to the Act or Rules.
	+	* Q4 — October audit. Post-Navratri; aligns with CIC's anniversary (12 October).
	+
	+	Each audit is completed within a two-week window. The findings and the "Last reviewed" date on audited pages are updated together.
	+
	+	===== The top-30 list =====
	+
	+	Derived from (i) highest internal-link count, (ii) Google Search Console top pages (when available), and (iii) editorial judgement. The list is refreshed each quarter.
	+
	+	==== The enduring core (always audited) ====
	+
	+	- [[:file-rti-online-india\|How to file RTI online]]
	+	- [[:blog:how-to-write-rti-application\|Ask for records, not answers]]
	+	- [[:explanations:grounds-for-rejection\|Grounds for RTI rejection]]
	+	- [[:why-rti-gets-rejected\|Why RTI gets rejected]]
	+	- [[:faq\|RTI FAQ — 25 most-asked questions]]
	+	- [[:faa-first-appeal-timelines\|First Appeal timelines]]
	+	- [[:faa-appellate-review-checklist\|FAA appellate-review checklist]]
	+	- [[:landmark-cic-decisions\|10 landmark CIC decisions]]
	+	- [[:pio-rti-reply-guide\|PIO RTI Reply Guide]]
	+	- [[:pio-faa-knowledge-base\|PIO / FAA knowledge base]]
	+
	+	==== The recipes (rotated) ====
	+
	+	- [[:guide:applicant:application:sample:fir\|FIR sample RTI]]
	+	- [[:rti-for-fir-status\|FIR not registered]]
	+	- [[:rti-for-gst-refund\|GST refund stuck]]
	+	- [[:rti-for-income-tax-refund\|Income-tax refund]]
	+	- [[:rti-for-pm-kisan-installment\|PM-KISAN installment]]
	+	- [[:rti-for-mgnrega-wages\|MGNREGA wages]]
	+	- [[:rti-for-ration-card-cancelled\|Ration card]]
	+	- [[:rti-for-electricity-bill-dispute\|Electricity bill dispute]]
	+	- [[:rti-for-answer-sheet-inspection\|Answer-sheet inspection]]
	+	- [[:rti-for-water-supply-quality\|Water supply quality]]
	+
	+	==== State and tool pages ====
	+
	+	- [[:file-rti-in-maharashtra\|Maharashtra]]
	+	- [[:file-rti-in-uttar-pradesh\|Uttar Pradesh]]
	+	- [[:file-rti-in-delhi\|Delhi]]
	+	- [[:file-rti-in-tamil-nadu\|Tamil Nadu]]
	+	- [[:file-rti-in-karnataka\|Karnataka]]
	+	- [[:tools:generator\|RTI Application Generator]]
	+	- [[:tools:first-appeal\|First Appeal Builder]]
	+	- [[:tools:pio-reply-checker\|PIO Reply Checker]]
	+	- [[:tools:chat\|RTI Wiki AI]]
	+	- [[:tools:question-builder\|Question Builder]]
	+
	+	===== Recent audits =====
	+
	+	* Q2 2026 (April) — First quarterly audit since the schedule was formalised. Top-30 baseline captured. DPDP 2025 amendment to §8(1)(j) propagated to all affected pages. No case overturned in the review window.
	+	* Q3 2026 (July) — scheduled.
	+
	+	===== How readers help =====
	+
	+	* Spot a stale citation? Report via [[:corrections\|our corrections page]]. Acknowledgement in 24 hours, fix in 48 hours (typical).
	+	* Know a better primary source? Email ''admin@bighelpers.in'' with a link.
	+	* Reviewer interest? See [[:about:editorial-review\|the reviewer onboarding page]].
	+
	+	===== Related pages =====
	+
	+	* [[:about:editorial-review\|Editorial Review — reviewer onboarding]]
	+	* [[:about:editorial-policy\|Editorial Policy]]
	+	* [[:about:web-vitals-audit\|Web Vitals audit baseline]]
	+	* [[:corrections\|Corrections]]
	+	* [[:content-roadmap-implementation\|Implementation plan]] (editorial-internal)
	+
	+	----
	+
	+	//Last reviewed: 21 April 2026.//
	+
	+	{{tag>about editorial-audit quarterly-review process}}

What is RTI Wiki

anonymous@undisclosed.example.com (Anonymous) — Wed, 22 Apr 2026 06:36:07 +0000

2017/12/31 03:51		current
Line 1:		Line 1:
	====== What is RTI Wiki ======		====== What is RTI Wiki ======
-	{{ pages:wiki.png}}	+	{{ :social:auto:about-rti-team.png?direct&1200 \|about / rti-team — RTI Wiki}}
		+
		+	{{htmlmetatags>metatag-keywords=(about rti team rti right to information india)
		+	metatag-description=(An RTI wiki is a web application from RTI INDIA which allows people to add, modify, or delete RTI content in collaboration with others.)}}
		+
		+
		+	{{pages:wiki.png?128x128\|Pages:wiki}}
	===== A RTI Wiki operates on a principle of collaborative trust =====		===== A RTI Wiki operates on a principle of collaborative trust =====
		+	==== Disclaimer: ====
		+
		+	<note tip>All our writings are in Public Domain.
		+	We encourage everyone to copy, quote, translate or print in whole or in part without any reference to RTI WIKI. We would be grateful to them</note>

	An RTI wiki is a web application from RTI INDIA which allows people to add, modify, or delete RTI content in collaboration with others. In a RTI wiki, text is written using a simplified markup language. While RTI wiki is a type of content management system, it differs from a RTI blog or forum in that the content is created without any defined owner or leader, and RTI wiki have little implicit structure, allowing structure to emerge according to the needs of the RTI Experts and contributors.		An RTI wiki is a web application from RTI INDIA which allows people to add, modify, or delete RTI content in collaboration with others. In a RTI wiki, text is written using a simplified markup language. While RTI wiki is a type of content management system, it differs from a RTI blog or forum in that the content is created without any defined owner or leader, and RTI wiki have little implicit structure, allowing structure to emerge according to the needs of the RTI Experts and contributors.
Line 18:		Line 28:
	- Access: RTI Wiki stay on the internet and thus can be referenced at any point in the future, with the click.		- Access: RTI Wiki stay on the internet and thus can be referenced at any point in the future, with the click.
	- Collaboration: It is through collaboration that the most valuable RTI wiki shall be created. RTI Wiki inherently call for additions, deletions, improvements, etc. by participants. The result is often a document that has been created by many authors. This process is exciting. The wiki document can become a published piece, printed out and shared or it can further grow into a new wiki with future contributions.		- Collaboration: It is through collaboration that the most valuable RTI wiki shall be created. RTI Wiki inherently call for additions, deletions, improvements, etc. by participants. The result is often a document that has been created by many authors. This process is exciting. The wiki document can become a published piece, printed out and shared or it can further grow into a new wiki with future contributions.
-	- [[Community-Builders\|About Community Builders]]	+	- [[:about:rti-team\|About Community Builders]]
	{{indexmenu>#1\|js#phoenity.png navbar context nocookie noscroll notoc msort}}		{{indexmenu>#1\|js#phoenity.png navbar context nocookie noscroll notoc msort}}

-	[[What is RTI Wiki]]	+	[[:start\|What is RTI Wiki]]
		+
		+
		+	===== Related =====
		+
		+	* [[:about:workshop\|Right to Information Wiki Workshop]].
		+	* [[:about:posting-at-other-threads\|Why You Should Start a New Thread]].
		+	* [[:about:what-is-rti-wiki\|What makes RTI Wiki so good for Documentation?]].
		+	* [[:about:community-builders\|Who are Community Builders at RTI INDIA]].
		+	* [[:user:shrawan\|Shrawan]].
		+
		+	//Last reviewed on: 20 April 2026//
		+
		+	{{tag>rti meta about}}

Performance Baseline — Core Web Vitals

anonymous@undisclosed.example.com (Anonymous) — Tue, 21 Apr 2026 12:34:07 +0000

2026/04/22 09:04	current
Line 1:	Line 1:
	+	{{htmlmetatags>metatag-keywords=(rti wiki performance,core web vitals,lcp,cls,fid,inp,performance audit 2026)&metatag-description=(Core Web Vitals baseline for top RTI Wiki pages — sampled page-weight and scripting profile as of April 2026. Roadmap for a full Lighthouse audit.)}}
	+
	+	====== Performance Baseline — Core Web Vitals ======
	+
	+	{{page>_snippets:dpdp-banner}}
	+
	+	<WRAP center round info 95%>
	+	Baseline sampled on 21 April 2026 across the five highest-traffic pages. This is a lightweight cURL/weight snapshot, not a full Lighthouse audit. A headless-Chrome pass is the next step — findings will replace this page when complete.
	+	</WRAP>
	+
	+	===== Sampled pages and weights =====
	+
	+	\| Slug \| Transfer size \| Load time (curl) \| `<img>` count \| `<script>` count \|
	+	\| file-rti-online-india \| 386 KB \| 1.04 s \| 21 \| 50 \|
	+	\| explanations/grounds-for-rejection \| 383 KB \| 0.81 s \| 45 \| 48 \|
	+	\| faq \| 353 KB \| 0.72 s \| 20 \| 48 \|
	+	\| blog/how-to-write-rti-application \| 345 KB \| 0.74 s \| 20 \| 50 \|
	+	\| tools/generator \| 334 KB \| 0.68 s \| 19 \| 48 \|
	+
	+	Observations:
	+
	+	* Transfer size is consistently in the 330-390 KB band. Healthy for a full-article page; the theme / framework inflates about 280 KB of this.
	+	* First-byte latency is under 200 ms (via server); full HTML arrives well under a second.
	+	* Scripts per page are 48-50 — mostly inlined (WebLLM bubble, DYK widget, verified-badge JS, breadcrumbs, share-bar, surprise-me, gamification). No external JS calls apart from Google Fonts and AdSense.
	+	* Image count is bounded; the explanations/grounds-for-rejection page has 45 images because of the 15 clause icons (SVG, tiny) + infographic diagrams.
	+
	+	===== Anticipated Core Web Vitals =====
	+
	+	* LCP (Largest Contentful Paint) — most likely the hero banner (~40 KB PNG). Lazy-loaded below the fold on most articles. Target <2.5s (good).
	+	* CLS (Cumulative Layout Shift) — low risk. The floating chat bubble is appended after DOM-ready, well outside the viewport centre. The DYK widget is sidebar, fixed width.
	+	* INP (Interaction to Next Paint) — the main risk area is the DYK widget button (simple DOM swap, negligible) and the floating-chat iframe opening (iframe load time dominates on first click).
	+
	+	===== Recommendations for a full audit =====
	+
	+	- Run Lighthouse on each of the top-20 pages via headless Chrome. Record scores for performance, accessibility, best-practices, SEO.
	+	- Sample with Chrome UX Report (CrUX) for real-user monitoring once traffic is sufficient (currently below the 10k-URLs-per-origin threshold).
	+	- Use PageSpeed Insights API to measure the same set monthly; record in a spreadsheet or dashboard.
	+	- Isolate scripting cost — profile the breadcrumb + surprise-me + DYK + chat launcher stack under CPU throttling. Combine into a single bundle if any one crosses 50 ms on mid-range devices.
	+	- Image optimisation — auto-generated hero banners are already WebP-ready; explicitly specify width/height on `<img>` tags to prevent CLS.
	+	- Font loading — Google Fonts is the only external font; consider `font-display: swap` to eliminate FOIT.
	+
	+	===== Quick wins identified (already applied) =====
	+
	+	* SVG icons instead of raster for the grounds-for-rejection clause list — 45 icons totalling ~6 KB.
	+	* Lazy iframe for the floating chat — does not load /tools/chat-app.html until the bubble is clicked.
	+	* Deferred script loading — the WebLLM library is dynamically imported only when the user opts in to deep analysis.
	+	* Preconnect hints — already in place for Google Fonts in pageheader.html.
	+	* Cache headers — Apache mod_expires already set for images/CSS/JS to 1 year (configured in /home/bighelpers/public_html/rtiwiki/.htaccess).
	+
	+	===== Known caveats =====
	+
	+	* AdSense adds ~30-50 KB of deferred script. Each ad slot triggers a separate render call. Mitigate by keeping ad density low.
	+	* Google Translate widget is on-demand (click-to-load) — zero cost until activated.
	+	* DokuWiki legacy CSS includes several unused selectors; a CSS purge pass could trim ~20 KB.
	+
	+	===== Sources =====
	+
	+	* Measurement methodology: curl with `--write-out` template for transfer size and timing.
	+	* Core Web Vitals thresholds: Google's official guidelines at ''web.dev/vitals''.
	+
	+	----
	+
	+	//Last reviewed: 21 April 2026.// //Baseline snapshot — full Lighthouse audit pending.//
	+
	+	{{tag>performance core-web-vitals audit engineering}}

What makes RTI Wiki so good for Documentation?

anonymous@undisclosed.example.com (Anonymous) — Wed, 22 Apr 2026 06:36:07 +0000

2017/04/15 03:43		current
Line 1:		Line 1:
	====== What makes RTI Wiki so good for Documentation? ======		====== What makes RTI Wiki so good for Documentation? ======
		+
		+	{{ :social:auto:about-what-is-rti-wiki.png?direct&1200 \|about / what-is-rti-wiki — RTI Wiki}}
		+
		+	{{htmlmetatags>metatag-keywords=(about what is rti wiki rti right to information india)
		+	metatag-description=(RTI Wiki is a web-based, free-content Right to Information encyclopedia project supported by the rtiindia.org and based on a model of openly editable content.)}}
		+

	===== Vision of RTI Wiki =====		===== Vision of RTI Wiki =====
-	{{:about:gatekeeper.png?nolink \|RTI Wiki}}	+	{{:about:gatekeeper.png?nolink &201x207\|RTI Wiki}}
	RTI Wiki is a web-based, free-content Right to Information encyclopedia project supported by the rtiindia.org and based on a model of openly editable content. RTI Wiki articles provide links designed to guide the user to related pages with additional information.		RTI Wiki is a web-based, free-content Right to Information encyclopedia project supported by the rtiindia.org and based on a model of openly editable content. RTI Wiki articles provide links designed to guide the user to related pages with additional information.

Line 37:		Line 43:
	* Maybe more I can't remember ;-)		* Maybe more I can't remember ;-)

-	To get started please read our [[wiki:syntax]] to edit RTI wiki. Visit our [[about:workshop]] to find out broken links and correct them.	+	To get started please read our [[:wiki:syntax]] to edit RTI wiki. Visit our [[:about:workshop]] to find out broken links and correct them.
		+
		+
		+
		+	===== Related =====
		+
		+	* [[:about:workshop\|Right to Information Wiki Workshop]].
		+	* [[:about:posting-at-other-threads\|Why You Should Start a New Thread]].
		+	* [[:about:rti-team\|What is RTI Wiki]].
		+	* [[:about:community-builders\|Who are Community Builders at RTI INDIA]].
		+	* [[:user:shrawan\|Shrawan]].
		+
		+	//Last reviewed on: 20 April 2026//
		+
		+	{{tag>rti meta about}}

-	====== Visit RTI INDIA forums for Discussions ======
-	{{rss>http://www.rtiindia.org/forum/external.php?type=RSS2 20 author date 1h }}

2026/04/22 09:04	current
Line 1:	Line 1:
	+	{{htmlmetatags>metatag-keywords=(rti wiki editorial review,retired ic reviewer,rti wiki editorial board,rti content review,editorial process rti)&metatag-description=(RTI Wiki's editorial-review process and how retired Information Commissioners and senior advocates join as reviewers. Scope, commitment, and contact.)}}
	+
	+	====== Editorial Review — Reviewer Onboarding ======
	+
	+	{{page>_snippets:dpdp-banner}}
	+
	+	<WRAP center round info 95%>
	+	RTI Wiki is looking for retired Information Commissioners and senior RTI advocates to join our editorial-review panel. The commitment is light (one sitting per quarter, 30-45 minutes). The contribution is decisive — you tighten our factual accuracy and catch errors before citizens rely on them.
	+	</WRAP>
	+
	+	===== Why RTI Wiki reviews content =====
	+
	+	This site is used by citizens filing their first RTI, by Public Information Officers training in their role, and by First Appellate Authorities drafting reasoned orders. A wrong fee rate, a stale case citation, a superseded clause — each can cause a citizen to miss a deadline or a PIO to sign an appealable order.
	+
	+	We already:
	+
	+	* Verify every published article — a green "Verified" badge appears at the top of the page, backed by the entry in ''conf/verified.json''.
	+	* Cite statute and case law — every ground, exemption, and procedural claim links to the Act section and the binding authority.
	+	* Link to primary sources — CIC orders, SC and HC judgements (via India Kanoon or the court's own portal).
	+	* Track last-reviewed date — visible at the bottom of every article; auto-emitted as `dateModified` in the article's schema.org JSON-LD.
	+
	+	What we do not yet have — independent editorial oversight by people who wrote the rulings, drafted the orders, and appeared in the appeals that shape Indian RTI practice. That is what this panel is for.
	+
	+	===== Who we are looking for =====
	+
	+	* Retired Central or State Information Commissioners — any tenure, any jurisdiction.
	+	* Senior RTI advocates — at least ten years of pleaded RTI appeals in the High Courts or the Commissions.
	+	* Retired Public Information Officers at senior rank — Joint Secretary / Commissioner-level, with a substantive RTI docket history.
	+	* Retired Secretaries / Additional Secretaries who administered Section 4 disclosures.
	+	* Academics specialising in transparency law — tenured faculty with published work on the RTI Act or comparative information-rights regimes.
	+
	+	===== What the commitment looks like =====
	+
	+	==== Quarterly sitting ====
	+
	+	* Frequency. Once per quarter (four times a year).
	+	* Duration. 30 to 45 minutes.
	+	* Format. Video call (Zoom / Google Meet) or a written exchange — whichever the reviewer prefers.
	+	* Agenda. The editor brings 5-10 articles that have been updated since the last sitting. The reviewer flags any factual error, stale citation, or tonal issue. The editor takes the note and fixes.
	+
	+	==== Topic-specific review ====
	+
	+	We may also reach out for a single-article review when the article concerns the reviewer's specialism. Example: an article on PIO procedure under Section 7 might be sent to a retired Information Commissioner who decided many §7(8)(i) matters. A single-article review is usually 15-20 minutes, written.
	+
	+	==== No ghostwriting expected ====
	+
	+	Reviewers do not draft content. The editor drafts; the reviewer flags errors or suggests sharper framing. All edits are the editor's responsibility.
	+
	+	===== What reviewers receive =====
	+
	+	* Public acknowledgement. Reviewers are listed on the Editorial Board page with their designation and tenure — opt-out on request.
	+	* A direct line to the editor. Feedback loops are fast; corrections typically go live within 48 hours.
	+	* Citation credit. Articles a reviewer has substantively shaped carry a small footnote: "Reviewed by [Name], former Chief Information Commissioner, [State]."
	+	* Copies of updates. Reviewers receive a quarterly digest of what changed, for their own records.
	+	* No honorarium or fee (the site runs on ad revenue and is not a commercial publication). We offer this as public-interest volunteer work.
	+
	+	===== What RTI Wiki is not =====
	+
	+	* Not a news outlet. We cover the Act, not daily headlines. We archive significant CIC orders and landmark court rulings; we do not report on breaking news.
	+	* Not a litigation service. Our tools (Generator, First Appeal Builder, PIO Reply Checker, Question Builder) assist the citizen to draft their own application or appeal. They do not file on anyone's behalf.
	+	* Not a partisan platform. Reviewers from across the political spectrum are welcome, so long as the feedback is factual and procedural.
	+
	+	===== Our editorial principles =====
	+
	+	- Statute first, case-law second, commentary last. Every claim cites either a section of the Act, a binding judgement, or a published CIC order. Opinion is clearly marked.
	+	- No "why" questions in sample RTIs. We teach citizens to ask for records, not answers. See our drafting guide at [[:blog:how-to-write-rti-application\|Ask for records, not answers]].
	+	- Case-law currency. After every significant SC / HC ruling, we update the relevant articles within a week.
	+	- Plain-language rule. We aim for a ninth-standard reading level on citizen-facing pages. Legal-practitioner pages (PIO framework, FAA checklist) are written for the trained reader.
	+	- DPDP-compliant privacy. We follow the Digital Personal Data Protection Act, 2023 and the 2025 Rules. See our [[:privacy-policy\|Privacy Policy]].
	+
	+	===== Our commitment to corrections =====
	+
	+	* Response within 24 hours for any substantive correction notice.
	+	* Fix within 48 hours when the correction is clearly supported by source.
	+	* Credit (on request) in the article's footer: "Correction by [Name], [date]".
	+	* Public changelog. See [[:corrections\|corrections page]] for reporting errors and the SLA.
	+
	+	===== How to join =====
	+
	+	Write to [[mailto:admin@bighelpers.in\|admin@bighelpers.in]] with the subject line "Editorial Review — Interest" and a short note:
	+
	+	* Your role(s) in RTI practice over the last ten years.
	+	* Your specialism (e.g. Section 8 case law, police records, service records, forest rights, scheme-specific).
	+	* Whether you are available for quarterly sittings, single-article reviews, or both.
	+	* Whether you are comfortable with public acknowledgement on the Editorial Board page.
	+
	+	The editor will reply within three working days.
	+
	+	===== Current editorial stack =====
	+
	+	* Editor. Shrawan Pathak. Contact: [[mailto:admin@bighelpers.in\|admin@bighelpers.in]].
	+	* Verified articles. Around 190 pages carry the green "Verified" badge, reflecting editor-level review.
	+	* Review cadence. //Last reviewed// dates are published on every article.
	+	* Editorial calendar. Quarterly reviewer sittings are planned from Q2 2026.
	+
	+	===== Related pages =====
	+
	+	* [[:about:editorial-policy\|Editorial Policy]]
	+	* [[:about:what-is-rti-wiki\|What is RTI Wiki?]]
	+	* [[:corrections\|Report a correction]]
	+	* [[:about:editor\|Editor — Shrawan Pathak]]
	+	* [[:privacy-policy\|Privacy Policy]]
	+
	+	----
	+
	+	//Last reviewed: 21 April 2026.//
	+
	+	{{tag>about editorial-review reviewer-onboarding editorial-board}}

2026/04/22 09:04	current
Line 1:	Line 1:
	+	{{htmlmetatags>metatag-keywords=(rti wiki quarterly audit,editorial audit process,rti wiki review schedule,content audit process 2026)&metatag-description=(Quarterly editorial audit schedule for RTI Wiki — which top-30 pages are reviewed when, who reviews, and what counts as a pass.)}}
	+
	+	====== Quarterly Editorial Audit — Top-30 Pages ======
	+
	+	{{page>_snippets:dpdp-banner}}
	+
	+	<WRAP center round info 95%>
	+	Every quarter, RTI Wiki audits its top-30 most-visited pages. The audit confirms that statutory citations are current, case law has not been overturned, amendments are reflected, and internal links resolve. The findings are published on this page; page-level corrections are committed within 10 working days of the audit.
	+	</WRAP>
	+
	+	Part of [[:about:editorial-review\|Editorial Review]].
	+
	+	===== What the audit checks =====
	+
	+	Every audited page goes through this 10-point checklist:
	+
	+	- Section citations. Every §N reference points to a section that still exists and has the same meaning.
	+	- Case-law currency. Cited cases have not been overturned; if refined by later judgement, the refinement is noted.
	+	- DPDP 2025 reflection. Pages touching §8(1)(j) carry the post-14-November-2025 framework.
	+	- Fee rates. Central Rs. 10 / state-specific rates match the rule as of audit date.
	+	- Portal URLs. Central and state RTI portals open; any renamed portal is updated.
	+	- First-appeal / second-appeal timelines. 30 days / 90 days references are consistent.
	+	- Broken internal links. All `[[:slug]]` targets resolve to live pages.
	+	- Anchor-text hygiene. No "click here", "read more", or placeholder anchors.
	+	- Schema.org validity. Article, FAQPage, HowTo, and BreadcrumbList schemas are well-formed and match page content.
	+	- Accessibility. All images carry descriptive alt text; H1 is unique; form inputs have labels.
	+
	+	===== Audit cadence =====
	+
	+	* Q1 — January audit. Post-Republic Day; refreshes pages ahead of the tax / result season.
	+	* Q2 — April audit. Post-fiscal-year; catches new state rules; CIC annual report typically releases around this window.
	+	* Q3 — July audit. Mid-monsoon; post-Budget-Session updates to the Act or Rules.
	+	* Q4 — October audit. Post-Navratri; aligns with CIC's anniversary (12 October).
	+
	+	Each audit is completed within a two-week window. The findings and the "Last reviewed" date on audited pages are updated together.
	+
	+	===== The top-30 list =====
	+
	+	Derived from (i) highest internal-link count, (ii) Google Search Console top pages (when available), and (iii) editorial judgement. The list is refreshed each quarter.
	+
	+	==== The enduring core (always audited) ====
	+
	+	- [[:file-rti-online-india\|How to file RTI online]]
	+	- [[:blog:how-to-write-rti-application\|Ask for records, not answers]]
	+	- [[:explanations:grounds-for-rejection\|Grounds for RTI rejection]]
	+	- [[:why-rti-gets-rejected\|Why RTI gets rejected]]
	+	- [[:faq\|RTI FAQ — 25 most-asked questions]]
	+	- [[:faa-first-appeal-timelines\|First Appeal timelines]]
	+	- [[:faa-appellate-review-checklist\|FAA appellate-review checklist]]
	+	- [[:landmark-cic-decisions\|10 landmark CIC decisions]]
	+	- [[:pio-rti-reply-guide\|PIO RTI Reply Guide]]
	+	- [[:pio-faa-knowledge-base\|PIO / FAA knowledge base]]
	+
	+	==== The recipes (rotated) ====
	+
	+	- [[:guide:applicant:application:sample:fir\|FIR sample RTI]]
	+	- [[:rti-for-fir-status\|FIR not registered]]
	+	- [[:rti-for-gst-refund\|GST refund stuck]]
	+	- [[:rti-for-income-tax-refund\|Income-tax refund]]
	+	- [[:rti-for-pm-kisan-installment\|PM-KISAN installment]]
	+	- [[:rti-for-mgnrega-wages\|MGNREGA wages]]
	+	- [[:rti-for-ration-card-cancelled\|Ration card]]
	+	- [[:rti-for-electricity-bill-dispute\|Electricity bill dispute]]
	+	- [[:rti-for-answer-sheet-inspection\|Answer-sheet inspection]]
	+	- [[:rti-for-water-supply-quality\|Water supply quality]]
	+
	+	==== State and tool pages ====
	+
	+	- [[:file-rti-in-maharashtra\|Maharashtra]]
	+	- [[:file-rti-in-uttar-pradesh\|Uttar Pradesh]]
	+	- [[:file-rti-in-delhi\|Delhi]]
	+	- [[:file-rti-in-tamil-nadu\|Tamil Nadu]]
	+	- [[:file-rti-in-karnataka\|Karnataka]]
	+	- [[:tools:generator\|RTI Application Generator]]
	+	- [[:tools:first-appeal\|First Appeal Builder]]
	+	- [[:tools:pio-reply-checker\|PIO Reply Checker]]
	+	- [[:tools:chat\|RTI Wiki AI]]
	+	- [[:tools:question-builder\|Question Builder]]
	+
	+	===== Recent audits =====
	+
	+	* Q2 2026 (April) — First quarterly audit since the schedule was formalised. Top-30 baseline captured. DPDP 2025 amendment to §8(1)(j) propagated to all affected pages. No case overturned in the review window.
	+	* Q3 2026 (July) — scheduled.
	+
	+	===== How readers help =====
	+
	+	* Spot a stale citation? Report via [[:corrections\|our corrections page]]. Acknowledgement in 24 hours, fix in 48 hours (typical).
	+	* Know a better primary source? Email ''admin@bighelpers.in'' with a link.
	+	* Reviewer interest? See [[:about:editorial-review\|the reviewer onboarding page]].
	+
	+	===== Related pages =====
	+
	+	* [[:about:editorial-review\|Editorial Review — reviewer onboarding]]
	+	* [[:about:editorial-policy\|Editorial Policy]]
	+	* [[:about:web-vitals-audit\|Web Vitals audit baseline]]
	+	* [[:corrections\|Corrections]]
	+	* [[:content-roadmap-implementation\|Implementation plan]] (editorial-internal)
	+
	+	----
	+
	+	//Last reviewed: 21 April 2026.//
	+
	+	{{tag>about editorial-audit quarterly-review process}}

2026/04/22 09:04	current
Line 1:	Line 1:
	+	{{htmlmetatags>metatag-keywords=(rti wiki performance,core web vitals,lcp,cls,fid,inp,performance audit 2026)&metatag-description=(Core Web Vitals baseline for top RTI Wiki pages — sampled page-weight and scripting profile as of April 2026. Roadmap for a full Lighthouse audit.)}}
	+
	+	====== Performance Baseline — Core Web Vitals ======
	+
	+	{{page>_snippets:dpdp-banner}}
	+
	+	<WRAP center round info 95%>
	+	Baseline sampled on 21 April 2026 across the five highest-traffic pages. This is a lightweight cURL/weight snapshot, not a full Lighthouse audit. A headless-Chrome pass is the next step — findings will replace this page when complete.
	+	</WRAP>
	+
	+	===== Sampled pages and weights =====
	+
	+	\| Slug \| Transfer size \| Load time (curl) \| `<img>` count \| `<script>` count \|
	+	\| file-rti-online-india \| 386 KB \| 1.04 s \| 21 \| 50 \|
	+	\| explanations/grounds-for-rejection \| 383 KB \| 0.81 s \| 45 \| 48 \|
	+	\| faq \| 353 KB \| 0.72 s \| 20 \| 48 \|
	+	\| blog/how-to-write-rti-application \| 345 KB \| 0.74 s \| 20 \| 50 \|
	+	\| tools/generator \| 334 KB \| 0.68 s \| 19 \| 48 \|
	+
	+	Observations:
	+
	+	* Transfer size is consistently in the 330-390 KB band. Healthy for a full-article page; the theme / framework inflates about 280 KB of this.
	+	* First-byte latency is under 200 ms (via server); full HTML arrives well under a second.
	+	* Scripts per page are 48-50 — mostly inlined (WebLLM bubble, DYK widget, verified-badge JS, breadcrumbs, share-bar, surprise-me, gamification). No external JS calls apart from Google Fonts and AdSense.
	+	* Image count is bounded; the explanations/grounds-for-rejection page has 45 images because of the 15 clause icons (SVG, tiny) + infographic diagrams.
	+
	+	===== Anticipated Core Web Vitals =====
	+
	+	* LCP (Largest Contentful Paint) — most likely the hero banner (~40 KB PNG). Lazy-loaded below the fold on most articles. Target <2.5s (good).
	+	* CLS (Cumulative Layout Shift) — low risk. The floating chat bubble is appended after DOM-ready, well outside the viewport centre. The DYK widget is sidebar, fixed width.
	+	* INP (Interaction to Next Paint) — the main risk area is the DYK widget button (simple DOM swap, negligible) and the floating-chat iframe opening (iframe load time dominates on first click).
	+
	+	===== Recommendations for a full audit =====
	+
	+	- Run Lighthouse on each of the top-20 pages via headless Chrome. Record scores for performance, accessibility, best-practices, SEO.
	+	- Sample with Chrome UX Report (CrUX) for real-user monitoring once traffic is sufficient (currently below the 10k-URLs-per-origin threshold).
	+	- Use PageSpeed Insights API to measure the same set monthly; record in a spreadsheet or dashboard.
	+	- Isolate scripting cost — profile the breadcrumb + surprise-me + DYK + chat launcher stack under CPU throttling. Combine into a single bundle if any one crosses 50 ms on mid-range devices.
	+	- Image optimisation — auto-generated hero banners are already WebP-ready; explicitly specify width/height on `<img>` tags to prevent CLS.
	+	- Font loading — Google Fonts is the only external font; consider `font-display: swap` to eliminate FOIT.
	+
	+	===== Quick wins identified (already applied) =====
	+
	+	* SVG icons instead of raster for the grounds-for-rejection clause list — 45 icons totalling ~6 KB.
	+	* Lazy iframe for the floating chat — does not load /tools/chat-app.html until the bubble is clicked.
	+	* Deferred script loading — the WebLLM library is dynamically imported only when the user opts in to deep analysis.
	+	* Preconnect hints — already in place for Google Fonts in pageheader.html.
	+	* Cache headers — Apache mod_expires already set for images/CSS/JS to 1 year (configured in /home/bighelpers/public_html/rtiwiki/.htaccess).
	+
	+	===== Known caveats =====
	+
	+	* AdSense adds ~30-50 KB of deferred script. Each ad slot triggers a separate render call. Mitigate by keeping ad density low.
	+	* Google Translate widget is on-demand (click-to-load) — zero cost until activated.
	+	* DokuWiki legacy CSS includes several unused selectors; a CSS purge pass could trim ~20 KB.
	+
	+	===== Sources =====
	+
	+	* Measurement methodology: curl with `--write-out` template for transfer size and timing.
	+	* Core Web Vitals thresholds: Google's official guidelines at ''web.dev/vitals''.
	+
	+	----
	+
	+	//Last reviewed: 21 April 2026.// //Baseline snapshot — full Lighthouse audit pending.//
	+
	+	{{tag>performance core-web-vitals audit engineering}}