Conservapedia's Original Source Project

The Conservapedia’s Original Source Project is an initiative by user:AnthonyPvanDuyn to preserve, structure, and present public‑domain primary texts in a clear, accessible, and SEO‑aligned format while also improving user experience through a more complete service and referencing improvements. Its purpose is to:

• provide easy public access to PD works
• provide easy copy and pastable materials
• provide easy original source references through Internal Links
• strengthen Conservapedia’s authority signals
• and strengthen Conservapedia’s trust signals

All done by simply hosting historically significant public domain works in a consistent, scholarly, and navigable manner. Each page follows a strict style guide to ensure consistency, readability, and SEO Trust Signals. Internal Links may be used to jump directly to specific paragraphs, such as Original Source: Sir Isaac Newton - Observations on Daniel, Chapter 1#1. These anchors improve user experience and strengthen SEO Trust Signals.

Purpose

The Original Source Project provides Conservapedia readers with reliable, well-formatted public-domain texts. Each work is presented in either an entire volume or chapter-by-chapter format, with stable paragraph anchors, consistent headings, and clear navigation. This allows encyclopedic articles to reference specific paragraphs with precision.

Style Guide

This style guide applies to all Original Source pages and will be enforced.

1. Page Naming Convensions

Entire Books per Page or Single Chapter per Page?

Users are free to decide themselves if it is more appropriate to host an entire book on a single page or single chapter per page, but are asked to consider that while WikiMedia has no fixed text limit, pages do become unstable above ~2 MB of wikitext leading to a host of problems. Smaller portions may be appropriate and may improve stability. If alot of artwork is involved, single chapters may improve load times. The choice to host the entire volume or by the chapter is up to the content uploader; but the naming convension must be adhered to.

Naming Convension

Each page name in Conservapedia's Original Source Project must:

• prefix with the designation of Original Source: followed by a space.
• include a professional title if applicable such as Dr. or Sir as this signals Experience and Expertise under the SEO E‑E‑A‑T Standard.
• follow with First Name and then Last Name', which is then followed by a space charcter and always a hyphen (not an em-dash or en-dash, as these create Wiki-wide navigation confusions) as this signals SEO hard idea seperation between the author's name and the following volume title.
• ensure that there is another space and insert the volume's working title
• If you are using the single chapter standard, add a comma' then insert a space and Chapter followed by a space and chapter indicator / number.

Examples

• Whole volume - Original Source: Sir Isaac Newton - Observations on Daniel
• Single chapter - Original Source: Sir Isaac Newton - Observations on Daniel, Chapter 1

2. Intro Paragraphs

Each page begins with the below standard intro paragraphs:

Introduction Text

This page is part of Conservapedia's Original Source Project, which preserves public-domain primary texts in a structured yet academically referencable format that can be easily copy-and-pasted by users.

All readers are actively encouraged to create internal links to Conservapedia's related encyclopedic articles. Readers are also asked to add internal links and references from the encyclopedic articles back to these original source documents. Internal links can jump directly to specific paragraphs, such as Original Source: Sir Isaac Newton - Observations on Daniel, Chapter 10#1. These internal anchors improve user experience and strengthen SEO Trust Signals. Please enjoy and make full use of the materials below.

Format Rules

• the intro paragraphs are not to have any headings above them,
• they are not to be indented,
• they are not to be universally italicised or bolded,
• they are not to appear with speech marks.
• they are to preserve all existing formatting and syntax.
• The internal link example must always be a link to the same page so as not to draw the reader away from the page they have come to.
• The intro paragraphs must always be followed by two empty lines in order to reduce visual clutter by separating the WikiMedia generated contents table from the text.

3. Headings

• All major headings use Level-1 syntax: `=Heading=`
• Chapter titles use Level-1 headings.
• Paragraphs use Level-4 headings: `====1====`, `====2====`, etc.

4. Paragraph Formatting

• Each paragraph begins with a Level-4 heading containing only a numeric index to minimise visual load and improve copy-and-paste processes:

 ====1====

• This conforms with standard academic referencing and avoids the visual clutter of a full ====Paragraph 1==== designator.
• This allows Internal Links to jump users directly to the desired paragraph for improved referencing.
• Each new paragraph text block begins with a single colon to produce a consistent indent for better visual uniformity:

 :

• No "blockquote" tags are permitted as these can fail or break formatting.
• No HTML formatting is to be used except where absolutely necessary.
• Users are encouraged to insert appropriate internal links to encyclopedic content only, not essays, political or religious commentary, debates, or opinion pieces. This improves user experience and compounds SEO Trust Signals inside this major SEO Authority Signal to build Domain Authority for Conservapedia at large.
• an example can be found at Original Source: Sir Isaac Newton - Observations on Daniel, Chapter 2#1

5. ASCII-Only Rule

To prevent broken links and anchor mismatches:

• Use only ASCII apostrophes `'`
• Use only ASCII hyphens `-`
• Do not use smart apostrophies or speach marks (`’`, `“`, `”`)
• Do not use en-dashes or em-dashes (`–`, `—`)

This ensures stable internal links and consistent page titles.

6. Internal Linking

Paragraph anchors are created automatically by Level-4 headings. Otherwise as already mentioned: Users are encouraged to insert appropriate internal links to encyclopedic content only, not essays, political or religious commentary, debates, or opinion pieces. This improves user experience and compounds SEO Trust Signals inside this major SEO Authority Signal to build Domain Authority for Conservapedia at large by building overall Search Engine Optimization accross the domain.

7. Public Domain Declaration

Every Original Source page must include a Public Domain Declaration using a Level-1 heading. This declaration must appear immediately above the =Index= section. It ensures legal clarity, improves SEO Trust Signals, and maintains consistency across all chapters.

Standard format:

=Public Domain Declaration=
This text is in the public domain. [Author]'s [Work Title] may be freely reproduced.

8. See Also

Each chapter page must include a =See Also= section linking to relevant Conservapedia pages. This improves internal navigation, strengthens SEO Trust Signals, and helps readers discover related content.

Standard format:

=See Also=
* Conservapedia's Original Source Project
* Original Source Naming Standard
* Internal Links
* SEO Trust Signals

9. Index and Contents

Each Original Source published under the chapter-by-chapter model, must include an =Index= section below the =See Also= section and directly above the Categories information.

The Index must list all chapters in the work, even if the list is long. This provides complete navigation and ensures readers can move through the work without relying on templates.

By ensuring that Indexies appear at the bottom of the page, it allows users to predict that they have a chapter progression point at the very bottom of every the page and near the top via the info panel.

Standard format:

=Index=
* Original Source: Professional Title, First & Last Name - Work Title, Chapter 1
* Original Source: Professional Title, First & Last Name - Work Title, Chapter 2
* Original Source: Professional Title, First & Last Name - Work Title, Chapter 3

10. Numbering Rules

All chapter and volume references must use Arabic Numerals only (1, 2, 3, etc.). Roman Numerals (I, II, III, IV, X, etc.) must not be used in page names, info panels, or example links. This ensures better catalogueing and correctly sequential display of information.

Examples:

Correct: Original Source: Sir Isaac Newton - Observations on Daniel, Chapter 3#1

Incorrect: Original Source: Sir Isaac Newton - Observations on Daniel, Chapter III#1

11. Info Panel Standard

All Original Source Project pages must include a right‑aligned informational panel at the top of the page. It provides a consistent, structured summary of the author, work, publication details, and related pages. Regarding the related pages section, in single‑page volumes the related pages section links to related volumes; but in the case of multi‑page volumes (classically large books), the related pages section not only acts as a navigation pane, but to a Search Engine crawl bot, it signals that these pages are a single book and there is a corresponding reward for this consistency granting an SEO boost. Therefore, for the benefit of all parties, the panel must follow the formatting rules below.

Required Sections

• Author biography (brief)
• Birth and death details
• Major works
• Publication notes
• Related Pages (see rules below)
• Categories

Related Pages Standard

Single‑Page Volumes

The Related Pages section is recommended for linking to genuinely related volumes, such as similar works by the same author or comparable books by different authors.

Multi-Page Volumes

For multi-page works (e.g., books with multiple chapters), the Related Pages section must list:

• 1. only the chapters belonging to that specific volume.
• 2. every chapter from that volume so that it acts like a contents or index page.

This section is not for general links, external references, or encyclopedia articles. It is strictly for volume navigation.

Required Format for Multi‑Chapter Works

Each chapter link must use the following simplification model to increase human readability and avoid appearing as a block of raw hyperlinks:

• Observations on Daniel, Chapter 1
• Observations on Daniel, Chapter 2
• Observations on Daniel, Chapter 3

This format ensures:

• consistent naming
• predictable link structure
• readable chapter titles
• strong internal SEO signals
• clear volume identity
• reliable navigation for editors and readers

Important Rules

• The link must end with ]] and nothing may follow it except whitespace or a new line.
• Do not include anchors, metadata, or comments after the closing brackets.
• Do not include unrelated pages in the Related Pages section.
• All chapter titles must follow the same naming pattern for consistency.

SEO and Navigation Benefits

Using this model creates:

• a dense internal link mesh
• a coherent “volume identity”
• improved crawlability for search engines
• predictable structure for editors
• stronger authority signals for the entire corpus

This is the recommended and required format for all multi‑page Original Source Project works.

Formatting Requirements

• The panel must be created using a standard MediaWiki table.
• The panel must float right.
• Width should be approximately 260px.
• Only ASCII characters may be used (classic culprits are smart characters such as apostrophes and speech marks).
• No blockquotes, and no HTML outside the table structure.
• All links must be internal Conservapedia links.

Required Fields

Each info panel must contain the following fields:

• Title Header – The subject’s name (e.g., "Sir Isaac Newton").
• Title Header Link – Title headers should be linked to the author's page (e.g., Isaac Newton|Sir Isaac Newton).
• Image – A Conservapedia‑hosted image, centred.
• Born – Birth date and location.
• Died – Death date and location.
• Occupation – Primary roles or professions.
• Known For – Key achievements or works.
• Major Works – List of major publications or contributions.
• Publication Notes – Notes relevant to the original source text.
• Related Pages – Internal links to all chapters or related OS pages (according to the rules above).

Image Selection

The image used in the info panel should normally match the image used on the author's main encyclopedic Conservapedia page, so that all Original Source pages remain visually consistent. Editors are free to choose a different image if they believe it is more appropriate for the specific work or context. All images must be internal Conservapedia files.

Placement

The info panel must appear:

• Immediately below the page title
• Before the introductory paragraph
• Before any chapter text

Example Panel

Below is the standard template used for Newton’s Observations on Daniel pages; a live example can be found here. All future OS pages should follow this structure, adjusting fields as appropriate for the author or work.

LINKED SUBJECT NAME
Born	Birth details
Died	Death details
Occupation	Occupation details
Known For	Key achievements
Major Works	Major publications
Publication Notes	Notes relevant to the OS text
Related Pages	Related Page 1 Related Page 2 Related Page 3

Purpose

The info panel:

• Provides consistent metadata across all OS pages
• Creates predictable navigation for readers
• Reinforces internal link structure
• Supports Conservapedia’s educational mission
• Strengthens SEO trust signals through structured content

All contributors are encouraged to maintain this standard for every new Original Source Project page.

12. Categories

Every Original Source page must include the following categories at minimum:

Category:Conservapedia's Original Source Project
Category:Original Sources
Category:Public Domain Works

Additional categories may be added for:

• the author (e.g.,)
• the subject matter (e.g.,)
• historical or thematic relevance

Categories must always appear at the bottom of the page.

13. Instructions When Using AI

for Humans

AI systems cannot see the raw wikitext of Conservapedia pages. They only see text that is pasted directly into the chat or uploaded as a file. AI systems cannot read the contents of browser tabs, edit windows, or rendered HTML pages. Because of this limitation, AI output may occasionally reconstruct text instead of preserving exact formatting and syntax.

To ensure accurate and consistent results, editors should follow these rules when using AI to generate or update Original Source pages:

• Click the Edit tab on this page.
• Select all the raw data

• Click somewhere and
• press CTRL + A, then
• CTRL + C

• Immediately press the back button or the Read page tab to reduce the chance of text contamination.
• Open the AI chat window and paste (press CTRL + V) the entire data set.
• Press Enter and then answer the questions.

for AI

• After digesting this style guide, begin by asking the user: "What is the already uploaded to Conservapedia image filename you wish me to use? Or should we simply substitute the Conservapedia logo in the example info panel?"
• Ask the user whether they wish internal links to be added to appropriate proper nouns throughout both the original source text and the information panel.

• If the user agrees, follow the internal linking rules below. If the user declines, do not add new internal links to the supplied source text, except for links explicitly required by this style guide.

• Ask the user what is the chapter range to be used in the Index section and Info Panel. Example: 1-14 (standard style), or 23-37 (such as in large works spanning multiple volumes such as Edward Gibbon's work).
• Ask the user to identify the complete source text to be integrated into the new page. The user may provide an entire chapter by copying and pasting it or by identifying the appropriate text such as in a supplied PDF. Do not accept partial chapters when the intention is to publish a complete chapter, as omissions complicate the production process and may compromise the integrity of the source.
• Before generating the page, ensure that the necessary information has been obtained. If essential information is missing or ambiguous, ask the user for clarification rather than inventing details.
• Produce the complete raw MediaWiki wikitext, including all required syntax, formatting, navigation, metadata, and categories specified in this style guide. Present the result in a single copy-and-paste-ready code block wherever practicable.
• Preserve the supplied source text faithfully. Do not paraphrase, modernise, abridge, silently correct, or otherwise alter the original wording. Apart from inserting authorised internal-link syntax and applying the formatting required by this style guide, retain the source text as supplied.
• Before presenting the finished wikitext, check it against the style guide for naming conventions, introductory paragraphs, heading levels, paragraph numbering, paragraph anchors, the information panel, the Public Domain Declaration, See Also, Index, categories, and all other applicable requirements.
• Alongside the finished wikitext, provide a concise editorial review list identifying proposed new articles, suggested renames of existing articles, and potentially useful redirects. If no such actions are identified, explicitly state that no additional naming or redirection recommendations were identified.
• Do not automatically rename existing articles, create redirects, or make other changes to Conservapedia. These are recommendations for the human editor to review and implement where appropriate.
• Clearly distinguish verified facts about the current state of Conservapedia from editorial recommendations, proposed article titles, and matters requiring further investigation.

Internal Linking Rules

• When the user authorises internal linking, identify appropriate proper nouns and other historically significant subjects in both the original source text and the information panel. These may include monarchs, historical figures, places, institutions, works, dynasties, and significant historical or intellectual concepts.
• Check Conservapedia to determine whether a relevant encyclopedic page already exists. Use the best-supported canonical encyclopedic title as the link destination, not automatically the title of an existing page.
• Do not assume that an existing Conservapedia title is correct or optimal merely because the page exists. Existing titles may be ambiguous, insufficiently precise, provisional, or inconsistent with appropriate encyclopedic naming conventions.
• Choose canonical titles using historical accuracy, established naming conventions, contextual identification, and the need to distinguish the subject from similarly named people, places, works, and concepts.
• If a relevant page does not exist, do not omit a worthwhile link merely because the destination is missing. Instead, use the best-supported canonical encyclopedic title for the proposed article. This intentionally helps identify missing articles and facilitates future article creation.
• If an existing article uses an inferior or ambiguous title, use the best-supported canonical title in the generated wikitext where appropriate and include the existing article in the editorial review list for consideration of a rename, consolidation, or other corrective action. Do not assume that a rename is necessarily appropriate without considering existing content and naming conventions.
• For example, if the source text says "Cyrus", and the historical context establishes that it refers to Cyrus II the Great, use `Cyrus`, regardless of whether the destination page currently exists.
• Similarly, if the source text says "Caesar", and the context clearly identifies Gaius Julius Caesar, use `Caesar`, rather than automatically linking to a less precise title such as `Caesar`.
• Identify common alternative names, spellings, and former article titles that may warrant redirects to the canonical article. Include these as suggestions in the editorial review list when useful. Do not claim that a redirect already exists unless its existence has been verified.
• Use the surrounding context to distinguish between people, places, and concepts with similar names. Do not guess when the identity cannot be established reliably. Flag genuinely ambiguous cases for human review.
• Do not claim that a destination page exists unless its existence has been verified. Clearly distinguish confirmed existing pages from proposed destinations where necessary.
• Link subjects consistently and use editorial judgement to avoid indiscriminate linking that reduces readability. Preserve the original wording of the source text through piped links wherever required.
• Do not invent biographical facts, publication details, page titles, or other metadata. Where required information cannot be verified or supplied, flag the uncertainty for human review rather than presenting an unsupported assertion.
• Treat web searches as a means of checking Conservapedia's existing coverage and evaluating its current article titles, not as authority to rewrite the primary source or blindly reproduce the encyclopedia's current naming inconsistencies. The supplied source remains the basis of the reproduced text.
• The editorial review list should, where applicable, separate recommendations into:

 :* **New articles:** worthwhile subjects for which no suitable existing article has been verified.
 :* **Potential renames or consolidations:** existing articles whose titles or coverage may warrant editorial review.
 :* **Potential redirects:** alternative spellings, common names, and former titles that may usefully redirect to the canonical article.
 :* **Items requiring human review:** uncertain identities, competing naming conventions, or recommendations that cannot be resolved confidently.

• For each recommendation, provide the proposed canonical title and a brief reason. Identify the current page title when verified and relevant. Do not present an unverified page, redirect, or article status as an established fact.
• Do not automatically rename articles, create redirects, create new pages, or otherwise alter Conservapedia. The AI prepares recommendations and copy-and-paste-ready content; the human editor decides which changes to implement.
• The AI prepares the page for human review and publication. The human editor remains responsible for checking the final text, links, metadata, naming decisions, and legal status before publication.