Anthony, SkipCaptcha, Upload, Automoderated users, edit
1,824
edits
Changes
Jump to navigation
Jump to search
Line 280:
Line 280: − + + − + − + Line 289:
Line 290: + + + + − + − + + + + + + − + − + − + + + + + + + +
Conservapedia's Original Source Project (view source)
Revision as of 13:54, October 13, 2026
, Tuesday at 13:54→for AI
===for AI===
===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 substitue the Conservapedia logo in the example info panel?"
* 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.
* 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.
:* 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 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.
* 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.
* 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.
* 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.
* 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.
* 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====
====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.
* 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.
* Search Conservapedia to determine whether a relevant encyclopedic page already exists. Use the exact existing page title as the link destination, employing a piped link when necessary to preserve the wording used in the original source.
* 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.
* 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 stub creation.
* 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 II the Great|Cyrus]]`, regardless of whether the destination page currently exists.
* For example, if the source text says "Cyrus", and the historical context establishes that it refers to Cyrus II the Great, use `[[Cyrus II the Great|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 `[[Gaius Julius Caesar|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.
* 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. Distinguish between confirmed existing pages and proposed destinations where necessary.
* 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.
* 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.
* 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, not as authority to rewrite the primary source. The supplied source remains the basis of the reproduced text.
* 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 AI prepares the page for human review and publication. The human editor remains responsible for checking the final text, links, metadata, and legal status before publication.
* 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.