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.

Suggested Works for the Original Source Project

The following works are suggested priorities for future additions to Conservapedia's Original Source Project. They include historically influential documents, political writings, and works that remain important to public discussion.

When preparing an original source, contributors should identify the exact edition, printing, or translation being transcribed. The text should retain that source's original wording, spelling, punctuation, and order. Different editions and translations should not be silently combined, and editorial notes should be distinguished from the source text.

Highest Priorities

• The Federalist Papers (1787-1788) - The 85 essays written under the name Publius in support of ratifying the United States Constitution. The essays address federalism, representation, separation of powers, the judiciary, and the dangers of faction.
  • Recommended source: The first bound edition, The Federalist: A Collection of Essays, published in two volumes by J. and A. McLean in New York in 1788. Use the Library of Congress digitized first edition as the controlling text. The Library of Congress full-text guide is useful for navigation, but its text draws on multiple versions. Preserve "Publius" as the original byline; later author attributions can be identified separately.

• Common Sense (1776) - Thomas Paine's influential pamphlet advocating American independence.
  • Recommended source: Project Gutenberg eBook #147, which transcribes the edition published by W. and T. Bradford in Philadelphia on February 14, 1776. Identify this as the edition being reproduced, retain its wording, and exclude supplementary commentary added by the transcriber from the original text. user:AnthonyPvanDuyn
• Declaration of Independence (1776) - The founding declaration announcing the American colonies' separation from Great Britain.
  • Recommended source: The National Archives transcription. This transcription follows the Stone Engraving of the parchment Declaration; the Archives also provides high-resolution document images. Identify the particular textual witness used rather than combining versions.

• Constitution of the United States (1787) - The framework of the United States federal government.
  • Recommended source: The National Archives transcription of the Constitution inscribed on parchment by Jacob Shallus. Its spelling and punctuation reflect the original document.

• On the Origin of Species (1859) - Charles Darwin's influential work on natural selection, a foundational text in the history of evolutionary biology and a continuing subject of scientific and philosophical discussion.
  • Recommended source: Project Gutenberg eBook #1228, the 1859 first edition. Do not substitute Project Gutenberg eBook #2009, which contains the sixth edition.

• The History of the Decline and Fall of the Roman Empire (1776-1788) - Edward Gibbon's six-volume history of the Roman Empire, its transformation, and the eventual fall of the Eastern Roman Empire. A major work of historical scholarship and an important primary source for studying Enlightenment views of Roman history, Christianity, and the development of European civilization.
  • Recommended source: The digitized first-edition volumes published in London by W. Strahan and T. Cadell between 1776 and 1788, available through The Online Books Page's catalogue of the six volumes. Use the scanned page images as the controlling text, preserving Gibbon's original wording, spelling, punctuation, chapter divisions, notes, and volume boundaries. Identify the edition used for each volume, since the publication history includes multiple editions and revisions. Project Gutenberg's complete-text edition can be a useful supplementary search aid, but it includes notes by Henry Hart Milman and should not silently be substituted for the chosen original edition. Project accepted by user:AnthonyPvanDuyn

Further Recommended Works

• The Bill of Rights (1791) - The first ten amendments to the United States Constitution.
  • Recommended source: The National Archives transcription. Note that the document transcribed there is the 1789 congressional resolution proposing twelve amendments; ten were ratified in 1791. Keep this distinction clear when presenting the text. done by user:AnthonyPvanDuyn.

• George Washington's Farewell Address (1796) - Washington's public address on the future of the American republic, including his warnings about political faction and foreign entanglements.
  • Recommended source: The Founders Online transcription of the September 19, 1796 address. Identify the source and edition used in the article's bibliographic information.

• The Gettysburg Address (1863) - Abraham Lincoln's short but historically influential address at the dedication of the Soldiers' National Cemetery at Gettysburg.
  • Recommended source: The Library of Congress's Gettysburg Address collection. Several manuscript versions survive, with variations in wording and punctuation. Select one identifiable version, such as the Nicolay copy, and do not combine the wording of different copies without clearly explaining the editorial decision.

• The Communist Manifesto (1848) - Karl Marx and Friedrich Engels' political pamphlet, an important primary source for the history of socialism and communism.
  • Recommended source: Project Gutenberg eBook #61, which reproduces the English edition of 1888 edited by Friedrich Engels. Identify the translation and edition explicitly.

• Second Treatise of Government - John Locke's influential work on political authority, natural rights, and government by consent.
  • Recommended source: Project Gutenberg eBook #7370. Check its title-page material and identify the historical edition represented in the transcription; do not describe it as a facsimile of the 1690 first edition.

Major Historical Works

• The History of the Decline and Fall of the Roman Empire - Edward Gibbon (1776-1788). Gibbon's celebrated six-volume history examines the Roman Empire, the transformation of the Roman world, and the fall of the Byzantine Empire. It is a major work of historical scholarship from the Enlightenment and an important example of eighteenth-century historical interpretation.
  • Recommended source: The six volumes in their first editions, published in London by W. Strahan and T. Cadell between 1776 and 1788. Consult The Online Books Page's catalogue of the first editions, which links to scanned copies of all six volumes. Use the page images of the chosen first edition as the controlling source. Do not silently substitute Project Gutenberg's eBook #25717, which includes notes by Henry Hart Milman and represents a different editorial presentation.

• The History of England - David Hume (1754-1762). Hume's influential history traces English history from the Roman period through the seventeenth century and offers an important example of Enlightenment-era political and historical interpretation.
  • Recommended source: Project Gutenberg eBook #10574, The History of England, Volume I, with the subtitle From the Invasion of Julius Caesar to the Revolution in 1688. Identify the particular volume and edition being transcribed. If the project expands to the complete work, use a consistent, identified edition for each volume.

• The History of England from the Accession of James II - Thomas Babington Macaulay (1848-1855). This five-volume history examines the political and constitutional conflicts surrounding James II, the Glorious Revolution, and the reign of William III.
  • Recommended source: Project Gutenberg eBook #25902, which provides a linked contents index for the five-volume set and links to the individual volumes and chapters. Use the relevant volume's text as the source and identify the printed edition represented by it. The contents index itself is a navigation aid rather than a substitute for the source text.

Ancient Historians

• The Histories - Herodotus (fifth century BC). Herodotus records the history of the Greek and Persian worlds, including the Greco-Persian Wars, and preserves accounts of peoples, customs, rulers, and events throughout the ancient Mediterranean and Near East.
  • Recommended source: George Campbell Macaulay's English translation, available in two volumes as Project Gutenberg eBook #2707 and Project Gutenberg eBook #2456. Use the two volumes of this same translation consistently and identify the translation in the article.

• The History of the Peloponnesian War - Thucydides (fifth century BC). Thucydides' account of the war between Athens and Sparta is a foundational work of Greek historiography, recording military operations, political disputes, speeches, and the effects of prolonged conflict.
  • Recommended source: Richard Crawley's English translation, available through Project Gutenberg eBook #7142. Identify the translation and retain its divisions and notes as presented in the selected edition.

• The Wars of the Jews; or, The History of the Destruction of Jerusalem - Flavius Josephus (first century AD). Josephus recounts the Jewish revolt against Rome and the destruction of Jerusalem, providing a major historical narrative of Judaea under Roman rule.
  • Recommended source: William Whiston's English translation, Project Gutenberg eBook #2850. Identify Whiston as the translator and preserve the selected edition's text and accompanying notes.

• Antiquities of the Jews - Flavius Josephus (first century AD). This extensive history presents Jewish history from its scriptural beginnings through later periods, making it a significant source for the study of ancient Judaism and the historical setting of early Christianity.
  • Recommended source: William Whiston's English translation, Project Gutenberg eBook #2848. Keep this work distinct from Josephus's account of the Jewish War, even if the two are eventually presented as a related collection.

• The Annals and The Histories - Tacitus (first and early second centuries AD). These histories describe the Roman Empire under successive emperors and offer important accounts of imperial politics, succession, warfare, and Roman government.
  • Recommended source: The English translations by Alfred John Church and William Jackson Brodribb, accessible through the Internet Classics Archive. Before transcription, identify the particular printed edition represented by the chosen text. Treat The Annals and The Histories as distinct works, with their own contents and section divisions.

• Lives of the Noble Grecians and Romans - Plutarch (first and second centuries AD). Plutarch's paired biographies compare Greek and Roman leaders, making the work especially useful for the study of ancient political leadership, military command, character, and civic life.
  • Recommended source: The Dryden translation as edited by Arthur Hugh Clough, available through Project Gutenberg eBook #674. Identify both the translation and Clough's editorial role.

Medieval History and Chronicles

• Ecclesiastical History of the English People - Bede (completed around 731). Bede's history is a major account of early English Christianity, the Anglo-Saxon kingdoms, and the development of the English Church.
  • Recommended source: A. M. Sellar's revised translation, Bede's Ecclesiastical History of England, available through Project Gutenberg eBook #38326. Identify Sellar's translation and preserve the edition's notes and introductory material separately from Bede's historical text.

• The Anglo-Saxon Chronicle - A collection of annals begun in the late ninth century and continued by successive writers into the medieval period. The chronicle preserves year-by-year entries concerning rulers, battles, religious affairs, and significant events in English history.
  • Recommended source: Project Gutenberg eBook #657, which provides an English-language text associated with the translations of James Ingram and J. A. Giles. Because editions and translations of the chronicle differ, contributors should identify the particular edition used and should not merge variant translations without explaining the editorial method.

Editorial Guidance for Historical Works

Historical works should be transcribed as complete works where practical, or divided into sections that follow their established volume, book, chapter, or annal divisions. Each new page should identify the work and the edition from which it derives.

For works that circulated in several editions, such as Gibbon's history, the selected edition should remain consistent throughout the transcription unless a change is explicitly documented. Editorial introductions, later annotations, indexes, and supplementary notes should be clearly distinguished from the author's text.

The project should also distinguish between the historical work itself and modern reference material about that work. A later historian's interpretation may be historically important, but it should not be presented as though it were an eyewitness account of the events being described.

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 a lot 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 character and always a hyphen (not an em-dash or en-dash, as these create Wiki-wide navigation confusions) as this signals SEO hard idea separation 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 speech 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 across 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=
* 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.

Conservapedia Original Source Page Production — Master Instructions (for AI)

Note to Humans: this is still a work in progress and is designed to function with ChatGPT and is not yet in a truly functional state. Do not try with Microsoft's new Co-Pilot.

1. Authority of the Style Guide

• The established style guide, its prescribed introductory material, and its approved example pages are authoritative for every page produced under this Project.

• After digesting the style guide, follow its requirements exactly. Do not redesign, replace, simplify, reinterpret, or improvise any established element of the page format.

• When an approved example establishes a particular template, information panel, introductory passage, declaration, navigation structure, or other standard component, reproduce that component faithfully. Change only those values that the style guide authorises for the individual page.

• If an instruction in this master set appears to conflict with the established style guide or an approved example, preserve the established convention and identify the conflict for resolution rather than silently choosing a new format.

The purpose of this workflow is to transform supplied raw text into a complete, consistent, copy-and-paste-ready MediaWiki page with minimal additional work required from the human editor.

2. Initial Questions and Required Information

• After reviewing the style guide, determine whether the following information has already been supplied in the current conversation, the available Project materials, or an applicable established workflow.

• Ask the user only for information that is genuinely missing or ambiguous. Do not repeat questions that have already been answered.

The required information is:

1. **Image filename:** Ask, "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?"

2. **Internal links:** Ask whether the user wishes internal links to be added to appropriate proper nouns throughout both the original source text and the information panel.

3. **Chapter range:** Ask what chapter range should be used in the Index section and Info Panel. Examples include Chapters 1–14 for a standard volume or Chapters 23–37 for a volume within a larger work.

4. **Complete source text:** Ask the user to identify the complete source text to be integrated into the new page. The user may paste the entire chapter or identify the appropriate text in a supplied document or PDF.

• Do not accept partial chapters when the intention is to publish a complete chapter. If the supplied material appears incomplete, establish whether the omission is intentional before proceeding.

• Before generating the page, confirm that all essential information is available. If essential information cannot be recovered from the available Project materials, ask for clarification rather than guessing.

Once these details have been established, apply them to subsequent chapters without repeatedly asking the same questions, unless the user changes the requirements.

3. Faithful Reproduction of the Source

• Preserve the supplied source text faithfully.

• Do not paraphrase, modernise, abridge, summarise, silently correct, rearrange, or otherwise alter the original wording.

• Apart from inserting authorised internal-link syntax and applying the formatting expressly required by the style guide, retain the source text as supplied.

• Preserve all original paragraph boundaries, sequence, headings, numbering, quotations, punctuation, and substantive wording. Where the style guide requires MediaWiki formatting or paragraph anchors, apply those requirements without changing the underlying text.

• Do not introduce new historical interpretations, explanatory claims, biographical details, or chapter summaries into the reproduced source.

• If the source appears to contain an error, omission, ambiguity, or inconsistency, preserve the supplied wording and flag the issue separately for human review when appropriate.

4. Mandatory Introductory Material

The introductory paragraphs prescribed by the established style guide must be included in every applicable page.

Reproduce these paragraphs verbatim, in their prescribed order and location. Preserve their wording, paragraph structure, and established formatting.

Do not replace the prescribed introduction with a newly written introduction, a chapter synopsis, a thematic summary, or a description of the chapter's contents.

Do not assume that an introduction is interchangeable with a summary simply because both discuss the same subject.

If the required introductory material is unavailable in the current context, consult the approved examples and existing Project materials. If the exact wording cannot be recovered, request the missing reference material rather than inventing a substitute.

5. Information Panel

Use the exact information-panel template demonstrated in the approved example.

Preserve its template name, field names, field order, syntax, formatting, and established conventions. Do not substitute a generic infobox, create a different panel, add unrelated fields, or redesign the layout.

Use the image filename specified by the user or the Conservapedia logo, as directed by the user.

Use the specified chapter range in the information panel wherever the established template requires it.

Change only those field values that properly vary between pages. Retain established wording and standard values wherever the style guide requires them.

Add internal links to appropriate information-panel values only when the user has authorised internal linking and the style guide permits those links.

Do not invent publication details, dates, bibliographical information, or other metadata. Verify such information where necessary or flag it for human review.

6. Complete Page Structure and Required Components

Produce the entire page, not a partial template or an isolated chapter body.

Include every component required by the established style guide, in its prescribed order and format. These may include:

- The approved page title and naming convention. - The exact approved information panel. - The prescribed introductory paragraphs. - The complete source text. - Required headings, paragraph numbering, and paragraph anchors. - Authorised internal links. - The prescribed See Also section. - The exact Public Domain Declaration. - The Index section, using the specified chapter range. - Required navigation elements and volume links. - The established categories. - Any additional mandatory components defined by the style guide.

Use the exact standard wording and markup for prescribed components. Do not create substitute declarations, invent See Also entries, fabricate index titles, or guess category names.

For chapter indexes, use verified titles wherever available. If a title is not available, investigate the existing Project materials and Conservapedia coverage. Do not present a guessed title as a verified existing article.

Do not omit required components merely because their exact wording or markup is not immediately available. Recover the approved example first; if it remains unavailable, ask for the necessary reference material.

7. Internal Linking Rules

Apply these rules only when the user authorises internal linking, except for links explicitly required by the style guide.

7.1 Identifying linkable subjects

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.

Use editorial judgement. Link worthwhile subjects consistently without indiscriminately linking every occurrence of an ordinary word or phrase.

7.2 Verify existing coverage

Check Conservapedia to determine whether a relevant encyclopedic page exists.

Use the best-supported canonical encyclopedic title as the link destination, rather than automatically adopting the title of an existing page.

Do not assume an existing title is correct or optimal merely because the page exists. Existing titles may be ambiguous, insufficiently precise, provisional, or inconsistent with appropriate naming conventions.

Distinguish verified existing pages from proposed article destinations.

7.3 Canonical titles and piped links

Choose canonical titles using historical accuracy, established naming conventions, contextual identification, and the need to distinguish subjects from similarly named people, places, works, and concepts.

Preserve the original source wording through piped links wherever necessary.

For example, if the source 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 says "Caesar" and the context clearly identifies Gaius Julius Caesar, use `Caesar` rather than automatically linking to a less precise title such as `Caesar`.

Use the surrounding context to distinguish people, places, and concepts with similar names. Do not guess when the identity cannot be established reliably. Flag genuinely ambiguous cases for human review.

7.4 Missing articles and inferior existing titles

If a relevant page does not exist, do not omit a worthwhile link merely because the destination is missing. Use the best-supported canonical encyclopedic title for the proposed article. This identifies missing coverage 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 a rename is necessarily appropriate without considering the existing content and relevant naming conventions.

7.5 Alternative names and redirects

Identify common alternative names, spellings, and former article titles that may warrant redirects to the canonical article.

Include useful suggestions in the editorial review list. Do not claim that a redirect already exists unless its existence has been verified.

7.6 Consistency and accuracy

Link subjects consistently. Preserve the supplied wording and do not rewrite the primary source to accommodate preferred article titles.

Do not invent biographical facts, publication details, article titles, or other metadata. Flag uncertainties for human review.

Treat web searches as a means of checking Conservapedia's existing coverage and evaluating its current article titles, not as authority to rewrite the source or blindly reproduce existing naming inconsistencies.

The supplied source remains the basis of the reproduced text.

8. Public Domain Declaration

Use the exact Public Domain Declaration prescribed by the established style guide or approved example.

Do not replace it with a newly written declaration, shorten it, expand it, or substitute a generic copyright statement.

Distinguish between the prescribed wording and any separate legal or editorial questions requiring verification. Do not make unsupported claims about copyright status, publication history, or the legal status of a particular edition.

If the prescribed declaration cannot be recovered, request the approved reference rather than inventing replacement wording.

9. See Also, Index, and Categories

Follow the approved conventions for the See Also section, chapter index, and categories.

For the Index, use the chapter range specified by the user. Include the appropriate volume navigation and chapter links according to the established example.

Use verified existing page titles when available. Clearly distinguish proposed destinations from confirmed existing pages in the separate editorial review.

Apply the required categories consistently. Do not invent category names or claim that categories or destination pages exist without verification where verification is required.

Do not omit, reorder, or redesign these components unless the style guide explicitly allows it.

10. Editorial Review and Recommendations

Alongside the finished wikitext, provide a concise editorial review list identifying proposed new articles, suggested renames or consolidations, potentially useful redirects, and unresolved naming questions.

Where applicable, separate recommendations into the following groups:

- **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 canonical articles. - **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.

If no additional naming or redirection recommendations are identified, explicitly state that no additional recommendations were identified.

Clearly distinguish verified facts about the current state of Conservapedia from editorial recommendations, proposed article titles, and matters requiring further investigation.

Do not automatically rename existing articles, create redirects, create new pages, or otherwise alter Conservapedia. These are recommendations for the human editor to review and implement where appropriate.

11. Final Verification Before Delivery

Before presenting the finished page, check the entire output against the style guide and approved examples, component by component.

Verify:

- Page title and naming conventions. - Exact introductory paragraphs. - Exact information-panel template and formatting. - Image filename or logo selection. - Fidelity and completeness of the supplied source text. - Heading levels, paragraph numbering, and anchors. - Internal links and canonical titles, where authorised. - Public Domain Declaration. - See Also section. - Index and specified chapter range. - Categories and navigation elements. - Any other mandatory requirements in the established style guide.

Do not claim that an element has been verified when it has merely been guessed or reconstructed.

If a required element cannot be verified, resolve the issue from the available source material or identify the precise missing reference before proceeding. Do not silently substitute invented content.

12. Output Format and Editorial Responsibility

Return the complete raw MediaWiki wikitext as one continuous, copy-and-paste-ready code block wherever practicable.

The code block must contain the entire page, including all required syntax, formatting, navigation, metadata, and categories. Do not interrupt it with explanations or editorial commentary.

Place the concise editorial review outside the wikitext block so that recommendations and uncertainties cannot accidentally become part of the published page.

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.

The governing principle is exact compliance with the established style guide, not creative reconstruction. When the guide supplies a standard, reproduce it. When the source supplies text, preserve it. When information is missing, verify it or ask. Never invent a replacement and present it as compliant.

Quotation and Foreign-Language Formatting

1. **English quotations:** Use quotation marks to identify quoted English text. Do not italicise English quotations merely because they are quotations or originate from an older source. 2. **Foreign-language passages:** Italicise substantial quotations and passages in Latin, French, German, and other foreign languages to distinguish them from the principal English text. 3. **Mixed-language passages:** Italicise only the foreign-language portions, leaving the surrounding English text in roman type. 4. **Visual exceptions:** Block quotations, pull quotes, and other deliberately designed display elements may use italics where appropriate to their presentation. Such styling is not the default for ordinary historical text. 5. **Source fidelity:** Formatting must not alter the original wording, spelling, punctuation, sequence, or meaning. Do not silently translate or correct foreign-language text; record suspected errors separately for editorial review. 6. **Consistency:** Apply these conventions throughout the page, including footnotes, quotations from cited authorities, and passages embedded within Newton's own prose, wherever the source formatting permits.

Date System and Calendar Conventions

1. **Default calendar:** Use the Gregorian calendar for dates throughout information panels, biographical summaries, indexes, and editorial notes wherever a reliable Gregorian date can be established.

2. **Julian dates:** If a reliable Gregorian equivalent is unavailable or cannot be established with sufficient confidence, retain the Julian date and explicitly identify it as **Julian**. Do not leave readers to infer which calendar is being used.

3. **Avoid ambiguous terminology:** Do not use *Old Style* (O.S.) or *New Style* (N.S.) as date labels. These expressions can refer to calendar differences, differences in the beginning of the year, or both, and may confuse general readers.

4. **Historical year numbering:** When converting dates from historical English records, account for differences in the beginning of the year as well as differences between the Julian and Gregorian calendars. A date may require a change of year as well as a change of day and month.

5. **Source fidelity:** Preserve dates exactly as they appear in the original source text. Do not silently convert, modernise, or replace a date within the transcribed text. Calendar conversions belong in editorial material or supplementary biographical information, not in the original text itself.

6. **Information panels:** Prefer a single Gregorian birth or death date rather than displaying multiple calendar equivalents. Include a Julian date only when a reliable Gregorian equivalent cannot be established, and label it explicitly as Julian.

7. **Uncertainty:** Do not calculate or assert a converted date when the relevant calendar, year convention, or historical evidence is uncertain. Flag the uncertainty for editorial review rather than presenting an unverified conversion as fact.

8. **Consistency:** Apply these conventions uniformly across all pages in the Original Source Project, including author information panels, publication dates, historical events, indexes, and editorial reviews.

Mandatory Internal-Link Audit

Before completing any Original Source Project page, conduct a systematic internal-link audit of the entire page, including the introductory text, information panel, original source text, See Also section, and Index.

1. **People:** Identify and link relevant historical figures, authors, rulers, religious figures, and other named individuals. Examples include Eusebius, Tatian, Constantine the Great, and Cyril of Jerusalem. 2. **Places and geography:** Identify and link relevant countries, regions, cities, islands, and other geographical entities, including every appropriate place name in the information panel. Examples include Egypt, Jerusalem, Rome, and other locations named in the source or metadata. 3. **Historical entities:** Identify and link empires, states, institutions, councils, religious movements, and other significant historical entities. Examples include the Roman Empire and the Greek Empire. 4. **Works and concepts:** Link appropriate named books, biblical passages, historical events, theological terms, and other subjects that have relevant encyclopedic coverage. 5. **Repeated occurrences:** Do not automatically assume that linking the first occurrence of a name is sufficient. Review subsequent occurrences and link them where doing so is useful and consistent with this project's linking policy. Apply the same standard to comparable names and entities throughout the page. 6. **Information panel:** Audit every metadata field and every Related Pages entry for appropriate internal links. Do not leave linkable proper nouns unlinked merely because they appear in a table or sidebar. 7. **Verification:** Use accurate existing article titles wherever they can be established. Preserve the source's original wording through piped links when necessary. Do not invent article titles or silently substitute an unrelated destination. Record uncertain destinations in the separate editorial review. 8. **Final quality check:** Re-read the completed page specifically to find omitted links. Compare comparable passages and lists of people or places for inconsistent treatment. A page is not ready for delivery until this audit has been completed.

The purpose is to improve reader navigation, connect primary sources to relevant encyclopedic coverage, and strengthen the meaningful internal-link relationships described in the SEO Trust Signals guidance. Linking must remain contextually relevant and must not distort the original text.