Editing Guide

From BibleStrength
(Redirected from Editingguide)
Jump to navigation Jump to search

The following is a helpful guide to explain how certain website sections are constructed, as well as stylistic aspects unique to BibleStrength; as the site design differs from other public encyclopedias.

General Style Guide

  • When quoting Bible verses mentioned by a critic, the verse is quoted in its entirety, to preserve context, and avoid cherrypicking of verses by the critic. So long as excessive length doesn't result, additional verses may be quoted. For example, if the critic references Genesis 1:3,5,7,10, it may be preferable to just quote Genesis 1:3-10 to avoid leaving out context ignored (sometimes deliberately by the critic). It is also a common practice by critics to just quote a snippet, a few words, from a verse, rather than the entire sentence. Again, when quoting the verse, also quote the entire verse to ensure context.
  • For the sake of consistency, please quote the King James Version when debunking lists of alleged Biblical criticisms. This is not because I consider the KJV to be a perfect translation, indeed I often refer to the Greek and Hebrew original texts precisely because English translations can mistranslate words from the original text, or at the least fail to provide their ideal or fullest meaning. However, the KJV is the Bible version I have memorized and for the sake of consistency across the site, I'd prefer it continue being used. Furthermore, because it is in the public domain and widely available, unlike the NASB, it ensures easy reference. While a more modern English translation is needed that consistently translates every Greek and Hebrew word the same throughout the Bible, I am not aware of a clear, ideal alternative at this time, and may produce it in the future.
  • APA style format is typically (if not always) used throughout the site, and probably should be used to preserve consistency.

General Coding Guide

The following is a general coding guide showing to aid in editing BibleStrength. For more advanced formatting, see the Help sections at Mediawiki or Wikipedia. For basic table formatting, see the List Page Structure section. Areas on this page with details on formatting not mentioned here, including tables, anchors, and images are bolded in red.


Coding Comments
: Colons serve to indent text. They can be useful on discussion or debate pages to preserve thread order. Each colon creates additional indentation.
[WebUrl TextShown] Displays an external hyperlink to a website, whatever follows after it, as separated by a space, will be the hyperlink text shown.
[[PageName|Text Shown]] Displays an internal hyperlink to a page on BibleStrength, whatever follows after it, as separated by the pipe symbol, will be the hyperlink text shown. It is possible to just put brackets around the page name itself, but the page name will then display exactly as it is named.
= Double equal signs surrounding plain text produce section headings. Each additional pair of equal signs reduces the heading/subheading level.
' Double apostrophes surrounding plain text produce italics, triple apostrophes surrounding plain text produce bold text.
* An asterisk will produce a bullet point. Using multiple asterisks for indented bullet points.
# Hashtags produce numbered lists.
<span style="color: red"></span> This will produce red text. The word red can of course be changed to other color names.
{{Reflist}} Coding to produce sources/references cited. If this coding is not used, an error will occur at the bottom of the page if any references are cited.
<ref>LastName, InitialofFirstName. (Year, Month Day). "[hyperlink_address article_title.]" ''Site_referenced.''</ref> Coding to produce a reference/citation in APA format that will appear in the sources/references section at the bottom of the page.
<ref name=RefName>Reference content</ref> Coding to produce a named reference/citation that can then be referenced again.
<ref name=RefName/> Coding to refer to a previously named reference/citation. Be aware that you cannot name a reference multiple times on a page without producing an error, additional namings should be replaced with this code so that it is only named once.
{{reflist|group=notes}} Coding to produce a notes section at the bottom of the page.
<refgroup=notes>Note content</ref> Coding to produce a note that will appear in the notes section at the bottom of the page.
[[Category:CategoryName]] Coding to categorize the page.
<br> Coding to go down a row, similar to hitting Enter on a keyboard.
{{cquote| }} The cquote tag creates a quote box. Whatever is placed in front of the two closing brackets will be quoted within the quote box.
-~~~~ Use a dash followed by four tildes to sign your name with a date stamp on discussion forums.
------- A series of dashes in a row will create a page break line running horizontally across the page for presentation purposes.

Typical Page Structure

The following is the typical page structure used, although this will vary for certain page types (e.g. Categories, which look better with just a minimal description and no references section).


Coding Comments
[[File:FileName.jpg|thumb|NumericalPixelWidthpx|ImageCaption.]] The page's primary image. The width is determined by the number of pixels. E.g. "[[File:Treaty of Penn with Indians by Benjamin West.jpg|thumb|400px|Treaty of Penn with Native Americans by Benjamin West.]] Make sure images are in the public domain and do not have copyright restrictions. For public domain images, see Mediawiki Commons.
{{TOC right}} The Table of Contents, right aligned. The location may need to be adjusted.
==Heading Title== The Section Heading.
Section content.
===Subheading Title=== The Subsection Heading. Two pairs of equal signs surrounding plain text results in a main heading. Each additional pair of equal signs results in a lower heading level.
Subsection content.
==Heading Title== The Section Heading.
Section content.
===Subheading Title=== The Subsection Heading. Two pairs of equal signs surrounding plain text results in a main heading. Each additional pair of equal signs results in a lower heading level.
Subsection content.
==Sources== The Sources heading
{{Reflist}} Coding to produce sources/references cited. If this coding is not used, an error will occur at the bottom of the page.
[[Category:CategoryName]] Any relevant categories should be included.

Alleged Bible Contradictions

The indexes of Alleged Bible Contradictions are organized within pages related to lists of alleged contradictions. For example, Infidels serves to address the two lists of alleged Bible contradictions from Infidels.org. The page uses a table format to address all alleged contradictions for each list, with built-in anchors for easy linking to specific answers on the list.

Each time a verse is referenced on a given list (e.g. Infidels) the page for that verse is then edited (or created) to include the solution provided.

List Page Structure

The following is the general page structure for lists of alleged Bible contradictions:


Coding Comments
{{TOC right}} The Table of Contents, right aligned.
The following is a complete debunking of [URLOfList UrlName] of alleged Biblical contradictions. [[InternalListPageName]] make the following comments (italicized). Please note that this is just a concise summary of all answers to the alleged contradictions, for more detail and sourcing please see the related pages. Summary, link to list.
<br><br> Extra blank lines to avoid the TOC from running into the tables.
==ListName List== Section Heading for the List
===Claims 1-9=== Subsection Heading for the first nine allegations. This format can be repeated for claims 10-19, 20-29, etc.
{| class="wikitable" style="margin: 1em auto 1em auto;" Formatting for the table specifying the table type and style/margins. To make the table sortable, change class="wikitable" to class="wikitable sortable".
|- A row break, ending the table setup formatting section.
!width="350" style="center"|Allegation Allegation column heading and column width.
!width="400" style="center"|Solution Solution column heading and column width.
|- A row break, ending the column setup formatting section.
{{anchor|ListAnchor1}}1. ''Title of Alleged Contradiction''<br><br>[[ABC:BibleBook BibleChapter|BibleBook BibleChapter:BibleVerse]]<br><br>vs.<br><br>[[ABC:BibleBook BibleChapter|BibleBook BibleChapter:BibleVerse]] List anchor is just an ID used with a number to allow linking to that specific part of the page. With so many allegations on the list, it will be helpful to be able to link to exact parts of the page. The alleged contradictions are then listed in numerical order, with BR tags as blank lines between critic comments and Bible passages referenced.
Solution for the alleged contradiction. The solution to the first alleged contradiction should then be provided.
|- A row break, ending the first row of alleged Bible contradictions.
{{anchor|ListAnchor1}}1. ''Title of Alleged Contradiction''<br><br>[[ABC:BibleBook BibleChapter|BibleBook BibleChapter:BibleVerse]]<br><br>vs.<br><br>[[ABC:BibleBook BibleChapter|BibleBook BibleChapter:BibleVerse]] List anchor is just an ID used with a number to allow linking to that specific part of the page. With so many allegations on the list, it will be helpful to be able to link to exact parts of the page. The alleged contradictions are then listed in numerical order, with BR tags as blank lines between critic comments and Bible passages referenced.
Solution for the alleged contradiction. The solution to the second alleged contradiction should then be provided.
|- A row break, ending the second row of alleged Bible contradictions. Add more rows as needed.
|} The pipe symbol followed by a closing bracket serves to close the table. If the table is not closed properly, the table will not appear.
==Sources== The Sources heading
{{Reflist}} Coding to produce sources/references cited. If this coding is not used, an error will occur at the bottom of the page.
[[Category:CategoryName]] Any relevant categories should be included. Each list of alleged Biblical contradictions should have its own category, e.g. the Infidels list has its own category of Category:Infidels.

Passage Page Structure

The general page structure for a given Bible verse (e.g. ABC:Exodus 20) is as follows:


Coding Comments
{{TOC right}} The Table of Contents, right aligned.
==Verse #== The verse number heading, ordered numerically. If there are multiple alleged contradictions for the same verse, they can be distinguished through an identifier in parentheses (e.g. Verse 4, Verse 4 (Again), Verse 4 (Yet Again). If the passages are not distinguished from one another, there will be confusion when linking to the different sections occurs.
[[List Link]] claims the Bible is wrong about the passage (and makes the following comments (italicized).<ref>LastName, InitialofFirstName. (Year, Month Day). "[hyperlink_address article_title.]" ''Site_referenced.''</ref> E.g. "American Atheists claims the Bible is wrong about the passage (and makes the following comments (italicized).[1]" The exact wording does not have to be identical so long as all lists referencing the alleged Bible contradiction are mentioned, it is pointed out that their comments are italicized, and a reference to the list is made with ref tags. Citation is via APA format.
{{cquote|[[ABC:BibleBook BibleChapter|BibleBook BibleChapter:BibleVerse]] Bible verse claimed to contradict quoted from the KJV. The cquote tag creates a quote box. The Bible verses alleged to contradict are then placed in the quote box, along with any italicized comments made by the list. For the sake of consistency I always quote from the King James Version (in part because that is the Bible version I have memorized). E.g. "Psalms 145:9 The LORD is good to all: and his tender mercies are over all his works."
''CommentsMadeClaimingAContradictionInList'' Any comments made by the critic as part of the list should be italicized (double apostrophes surrounding something serve as italics). As a general rule, the comments should be above the passage they are referring to. If the critic makes no comments and just presents the passages themselves, then italics may not be needed, in which case the passages themselves can be quoted.
[[ABC:BibleBook BibleChapter|BibleBook BibleChapter:BibleVerse]] Bible verse claimed to contradict quoted from the KJV. The second passage alleged to contradict should similarly be quoted from the King James Version. Typically there are at least two passages claimed to contradict, although if only one is referenced then just one may need to be quoted; or in some cases three or more may need to be quoted. E.g. "Jeremiah 13:14 And I will dash them one against another, even the fathers and the sons together, saith the LORD: I will not pity, nor spare, nor have mercy, but destroy them."
}} The double closing brackets serve to close the quote box. If the quote box is not closed, the quote box will not appear.
Solution for the alleged contradiction. The solution to the alleged contradiction should then be provided. E.g. "Biblically, mercy is the result of repentance and turning from evil, it is conditional upon one's actions. Ultimately God could not be good if He did not punish the evil actions of wicked people. God does send goodness upon all, sending rain on both the just and unjust, but must ultimately punish the wicked to stop their perpetuation of evil. With the Jeremiah passage, the unusually harsh punishment was in part because Israelite society was burning their own children alive in sacrifice to idols. (See Destruction of Canaanites)"
==Sources== The Sources heading
{{Reflist}} Coding to produce sources/references cited. If this coding is not used, an error will occur at the bottom of the page.
[[Category:CategoryName]] Any relevant categories should be included. Each list of alleged Biblical contradictions should have its own category, e.g. the Infidels list has its own category of Category:Infidels.

Helpful Advice

The following is information you may find useful for improving research and editing efficiency:

  • When referencing the original Greek or Hebrew text, I use PowerBible CD's Interlinear feature, and when citing their definitions, I refer to those at BibleStudyTools (since the Strong's definitions referenced in PowerBible CD are not online and thus can't be cited with hyperlinks so the reader can easily verify what they are being told). While you are of course free to use whatever software programs and websites you find helpful, they may prove useful for interlinear analysis, to see how a given Greek or Hebrew word is used throughout the entire Bible.
  • You can resize multiple internet windows to see multiple pages and programs at once. For example, if copying Bible verses from PowerBible CD to BibleStrength, you could resize the internet window to take up half the screen, and resize PowerBible to take up half the screen. This allows you to see both windows at once. If typing headings from a critic list into BibleStrength, you could have two internet windows, one for editing BibleStrength, and one to see the critic list, so that you can merge list information from one easily to the other.
  • Keyboard shortcuts will greatly improve your efficiency; including CTRL+X to cut, CTRL+C to copy, CTRL+V to paste, CTRL+A to select all, CTRL+Z to undo, CTRL+Y to redo, CTRL+T to open a new tab, CTRL+N to open a new window, tab to alternate between webpage sections, etc.
  • It helps to work on tasks of the same type while doing CTRL+C/CTRL+V copy/paste. For example, since the pipe character does not appear on a keyboard, you could copy and then paste the following code every time you need to refer to a Bible passage, and then simply fill in each verse reference.
    [[ABC:|
    Thus by working on all Bible verse passage references at one time you would work more quickly than if writing everything as you went.
  • You can easily replicate all content on a page by editing one page, clicking in the edit box, using CTRL+A to select all content, CTRL+C to copy, and then creating a new page and pasting in everything using CTRL+V. This could be used to copy all content from a list of alleged contradictions, paste it to create a new list as a new page, and then simply edit everything, replacing content as needed.
  • If you need to Google for information, you can go to Tools on the right-hand side below the search bar (only works on a computer or if using Desktop view on a phone) for additional search features, including searching by date range, which is useful for checking news articles within a certain time period. Use double quotes around a phrase to search for that exact phrase or a hyphen/minus sign in front of a word or phrase to exclude it from search results. There are more features in Google's Advanced Search which can be accessed through Settings, which is just to the left of Tools, including site-specific searching. For science articles, if you do not have access to JSTOR or other databases, you can search at Google Scholar. Nature and Pubmed have some free articles that are publicly visible as well.

Sources

  1. N.a. (2019). "Biblical Contradictions? American Atheists.