Family Trees
Buchanan Project (view) (launch FTE)
people: 266
Cowan Project (view) (launch FTE)
people: 24
Crumley Project (view) (launch FTE)
people: 28
Direct Ancestors ONLY (view) (launch FTE)
people: 484
Family - Adame (view) (launch FTE)
people: 168
Family - Campbell (view) (launch FTE)
people: 1757
Family - Clark (view) (launch FTE)
people: 591
Family - Lumadue (view) (launch FTE)
people: 194
Family - Rice (view) (launch FTE)
people: 3797
Family - Saunders (view) (launch FTE)
people: 7816
Family - Symons (view) (launch FTE)
people: 22
General Research or Maintenance (view) (launch FTE)
people: 26262
History of Cleveland (view) (launch FTE)
people: 83
History of Knox county Illinois (view) (launch FTE)
people: 107
In-laws (view) (launch FTE)
people: 1188
Knopf family (view) (launch FTE)
people: 31
Ricker - Nonrelative (view) (launch FTE)
people: 13
Sell-Borders (view) (launch FTE)
people: 577
Shawnee County, Kansas (view) (launch FTE)
people: 1066
Topeka Capital-Journal Obits (view) (launch FTE)
people: 692
US Cemeteries (view) (launch FTE)
people: 3768
US Census Records (view) (launch FTE)
people: 9526
US Counties (view) (launch FTE)
people: 1259
US State Census Records (view) (launch FTE)
people: 30
US Townships (view) (launch FTE)
people: 2212
User pages
Khaentlahn/Apollos Moore Mystery
Khaentlahn/Census Project
Khaentlahn/Census Project/Alabama
Khaentlahn/Census Project/Alaska
Khaentlahn/Census Project/Arizona
Khaentlahn/Census Project/Arkansas
Khaentlahn/Census Project/California
Khaentlahn/Census Project/Colorado
Khaentlahn/Census Project/Connecticut
Khaentlahn/Census Project/Delaware
Khaentlahn/Census Project/District of Columbia
Khaentlahn/Census Project/Florida
Khaentlahn/Census Project/Georgia
Khaentlahn/Census Project/Idaho
Khaentlahn/Census Project/Illinois
Khaentlahn/Census Project/Indiana
Khaentlahn/Census Project/Iowa
Khaentlahn/Census Project/Kansas
Khaentlahn/Census Project/Kentucky
Khaentlahn/Census Project/Louisiana
Khaentlahn/Census Project/Maine
Khaentlahn/Census Project/Maryland
Khaentlahn/Census Project/Massachusetts
Khaentlahn/Census Project/Michigan
Khaentlahn/Census Project/Minnesota
Khaentlahn/Census Project/Mississippi
Khaentlahn/Census Project/Missouri
Khaentlahn/Census Project/Montana
Khaentlahn/Census Project/Nebraska
Khaentlahn/Census Project/Nevada
Khaentlahn/Census Project/New Hampshire
Khaentlahn/Census Project/New Jersey
Khaentlahn/Census Project/New Mexico
Khaentlahn/Census Project/New York
Khaentlahn/Census Project/North Carolina
Khaentlahn/Census Project/North Dakota
Khaentlahn/Census Project/Ohio
Khaentlahn/Census Project/Oklahoma
Khaentlahn/Census Project/Pennsylvania
Khaentlahn/Census Project/South Carolina
Khaentlahn/Census Project/Texas
Khaentlahn/Census Project/Utah
Khaentlahn/Census Project/Vermont
Khaentlahn/Census Project/Virginia
Khaentlahn/Census Project/Washington
Khaentlahn/Census Project/West Virginia
Khaentlahn/Census Project/Wisconsin
Khaentlahn/Census Project/Wyoming
Khaentlahn/Notes and Rambles
Khaentlahn/Talk Archive 2012
Khaentlahn/Talk Archive 2013
Khaentlahn/Talk Archive 2014
Khaentlahn/Things To Do

Genealogy has been a passion of mine for more years than I care to remember, but Wikis, on the other hand, are a fairly recent endeavor. The following information is more for my own benefit than others, but I realized that if I was needing reminders, perhaps others might as well.



Citing Death Certificates

Certificate of Death: Charles S Mote, in Missouri, United States. Missouri Death Certificates, 1910-1961. (State Board of Health, Bureau of Vital Statistics). Filed 23 Jul 1918, Reg Dist No. 6290, File No. 22831, Informant: Opal Mote [Decedent's daughter by his first marriage]

The order of the information is basically irrelevant, but sticking with a standard makes understanding the information easier. It is also important to differentiate between information culled from the record and information inferred from other sources. Always use brackets for information not directly derived from the death certificate.

Citing U.S. Census Records

Page creation on WeRelate

This is the standard, copied (with stylistic revisions and additions), which I found on the Source Page Titles help file. [As of 19 Nov 2012]

The standard page title style for United States census records is: County name, State name, United States. XXXX U.S. Census Population Schedule (Example:Source: Crawford, Illinois, United States. 1870 U.S. Census Population Schedule)

  • In the Source type drop-down, select Government/Church records
  • In the Title field, enter: XXXX U.S. Census Population Schedule. The system will use this information to create the proper page title.
  • In the Publisher field, enter: National Archives and Records Administration Publication XXXX where XXXX is the publication designation. (Addition to Standard)
  • In the Place issued field, enter: Washington D.C. (Addition to Standard)
  • In the Place covered field, enter: County name, State name, United States (Example: Lawrence, Ohio, United States). A drop-down will suggest the proper selection. (If the drop-down does not appear, please check your spelling.)
  • In the Year range fields, enter: XXXX' & XXXX where XXXX is equal to the census year date. (Addition to Standard)
  • In the Subject field, select: Census Records (Addition to Standard)
  • In the Text field at the bottom of the page, enter: (Order of these three lines is irrelevant.)
    • {{XXXXCensus}}, which will add usage tips via a template where XXXX is equal to the census year.
    • [[Category:XXXX [Insert the State name here, do not include these two brackets] census]] and where XXXX is equal to the census year.
    • ==Usage Tips===

Citing on individual pages

I want to enter a census record as a source to one of my ancestors. The record is an 1820 U.S. Census for Overton County, Tennessee. Here's my method, which generally follows standards for citing U.S. census records while incorporating WeRelate's census page creation method. I haven't found one actual standard for citing census records. What I have found is that all of the information contained in the various citations is primarily the same, but the order or detail of the record may be different.

  • In the Citation's Source box, I choose Source.
  • Under Title I enter Overton, Tennessee, United States. 1820 U.S. Census Population Schedule
If the title doesn't exist, it can be created using the "Page creation on WeRelate" method. Ideally, the page will already exist and the process can continue.
  • In the Text box I put all the details that make the citation complete, Pg 254, Line 3, NARA microfilm publication M33, roll 122.

At this point, a link can be made to the actual page of the census record if it exists in a format that others can view online. Examples would be an uploaded image of the page or a link to a free website displaying the page. I usually attempt to find the image on Family Search, since it's free, so I can link directly to the image on their site in my sources. So here's the back end of my Text box detail:

  • [ Pg 254, Line 3, NARA microfilm publication M33, roll 122]

Once this is done, clicking on Save Page or Show Preview should have the citation appearing like the following example:

Overton, Tennessee, United States. 1820 U.S. Census Population Schedule
Pg 254, Line 3, NARA microfilm publication M33, roll 122

Wallah! Now if you want to enter more details, like a transcription of what was found on the record, have fun and do so. Otherwise, all done!

You might be asking, why go to so much effort if I'm linking to the image online? I'm afraid I'd have to answer that question with a question. What if the link to the image breaks? With this method the record is accurate enough that anyone down the road can trace through the census (by hand, if need be) and find the exact page for which they're looking, even if the original image link goes away.

Addendum: I have, since the writing of this portion, changed how I enter the citation. Since my main source for census records is Family Search, I have chosen to instead copy the citation they have already generously provided on individual census links under Document Information. I copy the information from FamilySearch to before the NARA portion of the citation. NARA should be included as part of the original census source. The majority, if not entirety, of the information which I gathered and used originally is generally included in this information.

Census Enumeration Dates: US Federal

Every US Federal census record has what is called an enumeration date printed on each form. It is the date that census takers were supposed to use as their point of record. It is different than the date written on the records, which is the day they actually acquired the information. The difference between these two dates is simple. The census takers were supposed to write down information as if the date they were recording the information was the enumeration date printed on the form, not as of the date they were recording the information. We as researchers can only make the assumption that the census takers did their job correctly. If we start assuming otherwise, then we are adding another level of possible error onto a source which should be avoided. The official enumeration dates of the United States Federal Census are as follows and are the dates I always enter as the date for those records:

  • 2 Aug 1790
  • 4 Aug 1800
  • 6 Aug 1810
  • 7 Aug 1820
  • 1 Jun 1830
  • 1 Jun 1840
  • 1 Jun 1850
  • 1 Jun 1860
  • 1 Jun 1870
  • 1 Jun 1880
  • 1 Jun 1890
  • 1 Jun 1900
  • 15 Apr 1910
  • 1 Jan 1920
  • 1 Apr 1930 (1 Oct 1929 in Alaska, also, since 1930, the census date has been 1 Apr)

Census Enumeration Dates: US States

State census records were also restricted by enumeration dates, but these were generally NOT printed on the forms. It is, at times, difficult to determine a State's enumeration date without a bit of digging.



  • 1855
  • 1865
  • 1875
  • 1 Mar 1885
  • 1 Mar 1895
  • 1 Mar 1905
  • 1 Mar 1915
  • 1 Mar 1925

Standards and Standardization: Is it really that important?

What's the point? Why does it matter? Is it really that important?

It is, quite simply, very important if you want anyone to find your work, help you with your research or you want to make a valid contribution to the core system. Without standardizing the information on WeRelate, there will be 100 different ways to reference Albany County, New York with no one way for anyone to have a clue if someone else is doing research in that area or if there is a reference book that has something to do with that area.

Standards are also important for continuity. The more contiguous a site is, the easier it is to navigate and the more likely you will want to be there. Humans are creatures of habit and, in general, we don't like it when we are hit with the big red change sign. When one page shows a date formatted one way (ie, 25 Jun 1950) and another page shows a date formatted completely different (ie, 1950-06-25 or even 25 JUN 1950), it tends to jar our sense of aesthetics and hits us upside the head with unneeded change. Perhaps this isn't a huge irritant for you, which is fabulous and wonderful, but for many people, it is. Don't get me wrong, change can be good for many people, but I have found when reading, it is a bad thing. (past tense/present tense conflicts anyone?)

I can't stress this enough, standards are amazingly important, especially with so much information available. It may feel like a pain in the neck sometimes, but a pain now saves on countless headaches in the future.

Theory vs Practice

...But (Random Name Designated Area Inserted Here) Didn't Exist Before XXXX. Now what?

This is one of those areas of Theory vs Practice, where I get it, but I don't. I understand that researchers want to be accurate in how their particular information is displayed (e.g., showing Virginia Colony instead of Virginia, United States). On a theory level, I get it. It would be great if there were webpages that would reflect all of these various iterations of a particular land mass so that researchers could be accurate down to minutiae, but it's not practical in practice, especially on a website. Ultimately though, whether the United States "existed" in 1650 or not is irrelevant. The page United States refers to a specific GPS location. If it referred to a series of GPS locations, all the better... oh wait, those are taken by States, Counties, Cities, etc., so it already does. Therefore, WeRelate already has a Place system that works and connects with a geographical location designated by GPS coordinates. This is the practice side that makes more sense to me. It's clean, it's clear and it's very specific.

So then we have the "pipe" system ( | = a pipe ), which, if you're unaware what that means, it's an option that has been used for Place names to allow for "other" names to appear instead of the original GPS referenced name (e.g., Virginia, United States|Virginia Colony). This solves the problem, right? No, not really, because most of the time the "pipes" are used by the back-end of the WeRelate system to catch typographical errors in Place names entered on a particular page, which the researcher input incorrectly. Also, utilizing the "pipes" by manually adding them for personal preferences, regardless of the accuracy of the research, tends to be confusing for most other researchers which come after the initial researcher who chose to use the "pipe". A collaborative website such as this needs to be kept as simple as possible to appeal to and be utilized by average website users, which makes up about 80% of the general population.

Here's a separate real world example... Programming. That's okay, if you know nothing about programming, don't run away. This will make sense, I hope.

The programming language (or code) that a computer most easily understands is machine code, though it is the furthest thing from a language that is easy for a human to understand. Think binary with all the ones and zeros you may (or may not) have learned about in school. (By the way, if you know someone who programs in machine code, give them a cookie and a pat on the back.) Most programmers today use high-end programming languages like Python, Java, etc. If you were to take an average computer user and teach them how to write the very basic "Hello World" program in Java, it wouldn't be that difficult for them to understand with some explanation, even if they may never use it again in their entire life. Were you to do the same with machine code... uh, no. Not happening. Basically, the average user needs something simple and basic. Now what about other programming languages? Sure, there are other high-end languages that will also work, but in a collaborative system, only one language should be used and agreed upon, otherwise you get what is called spaghetti code (though even with one language this can happen and often does).

Now let's connect the dots... Here we have machine code, which equates to GPS coordinates, and the "Hello World" program, which equates to the information that researchers enter into WeRelate. Now we need the programming language between them, which is the structured WeRelate Place name system. All things considered, this is fairly simple and straightforward, but then you get researchers who want to introduce other languages, like the "pipes" or redundant pages with more details. I don't know about you, but as much as I like spaghetti, I prefer it kept away from either programming or webpages. Anything that makes these pages more complex should be avoided. Simplicity is necessary for the website to grow.

Also, have you considered researchers outside of your own country when modifying Place names with "pipes" or otherwise? If you came across a page showing Redcliffe Penal Colony, would you know automatically to what it was referencing? If you're from Australia, most likely, but would people from Thailand, the United States or Russia (ignoring language barriers) know that you entered a "pipe" that actually references Redcliffe, Queensland, Australia? Perhaps, eventually, but the unnecessary ambiguity stops the original flow of research. Instead, the most viable solution would be to leave the Place name alone and put the added or modified description in the "Description" column... imagine that.

All this to say that while in Theory more specific research places is preferable, in Practice too much detail in the Places column will simply make the whole website cumbersome, difficult to understand, and a challenge to maintain.



  • Sources needed -- {{sources needed}}
  • Speedy Delete as found under the Admin menu option -- (This can really be your friend to get rid of those pesky pages that pop up with the gremlins.)


  • Conjectured Information on this Page -- {{Conjectured|Text}}, which looks like this:
Conjectured Information on this Page

As of this writing [20 Nov 2012], the text centers in the box, but the box does not center on the page.

Family Connections

Unfortunately, family connections are not always clean for one reason or another...

parents for a sibling relationship are conjectured, but not known,
parents are still living for a deceased child, but the grandparents are deceased
a connection between families should be maintained even if there are living individuals
an adoption relationship should be shown without causing duplicate parents issues
a deceased son-in-law or daughter-in-law should be able to connect with their spouse's family, but their spouse is alive

These are all perfectly valid, so I found a few templates and came up with few templates to help these situations. They all use the same basic format. {{Template name|Person (or Family) name}} used in the Event area of a page with the Other option chosen. More clarity can be found on the actual template pages. When you use one of these templates on a family page, the end result will be shown on both parents individual pages as well as the main family page.


  • BillionGraves Index -- {{Bgraves|####|Name}}
  • Find A Grave -- {{Fgravemem|####|Name}}
  • Find A Grave Cemetery -- {{Fgravecem|####|Cemetery Name}}
  • Wikipedia content -- {{source-wikipedia|wikipedia page name}} - Initially, this will only add a line that says the text in this section is copied from an article in Wikipedia. An automated process will take over from there, which can sometimes take upwards of several months before completed.
For Category Wikipedia entries -- [[Category:7th New Hampshire Infantry (Civil War)]] [[Category:Source templates|Wikipedia]] (NOTE: I haven't tried this one yet.)
  • Wikipedia links -- [[Wikipedia:Article name|Article name]] -- This is for linking to Wikipedia instead of bringing information over from Wikipedia.

Errors and Solutions

Dealing with Pages Created in Error

Everyone is going to do it at some point... a page gets created that is later found to already exist, so what do you do with the new page? If it was only created in the past day or so, you can send it to Speedy Delete and only the SD committee is the wiser. If it was created months ago, that could be another kettle of fish.

Deleting a Page

Sending a page to the Speedy Delete committee is the cleanest way to get rid of a recently created page. Here's my solution.

  • 1. Make sure there isn't anything pertinent that should be saved from the page. If a duplicate source was made, copy anything unique from the duplicate to the original source.
  • 2. Erase everything (or anything) in the Text box.
  • 3. Insert the template from the Speedy Delete page, found through the Admin pull-down menu. Make sure to update it with an actual reason and date.

...and Save. Simple and you can go about your work, nothing to see here.

Redirecting a Page

So the page has been around a few months and it's possible someone else linked to it from another website. Great, so now what? It's fairly simple. The duplicate page needs to be redirected to the original page. Follow Steps 1-2 for Deleting a Page, then continue to Step 3.

  • 3. Insert the following onto the first line of the duplicate page's Text box:
#redirect [[Namespace:Name of the original page]] -- (As found on How to redirect pages if more clarity is needed.)

...and Save. Again, simple, and the world is back in order.

Reverting to a Previous Revision

Going along my merry way, I made some changes to a couple of pages, which I considered the right thing to do at the time. A few days later (almost a week), I realized I had made a rather huge mistake in my changes. We learn as we go, right? ...and since no one else caught my error, I wanted to figure out how to fix it, but I had no clue.

Here's the scenario:

I changed the basic information for a census record source, which at the time I assumed was incorrect because it contained a rather specific author. Authors on census records? Not likely... so I changed them thinking something was seriously wrong with the original creator's thinking (arrogance strikes again). Little did I take into consideration that the page was an index that someone else had created OF the original census. Realizing my error later, I knew I had to put all the book citation information back into the source file and change the source file name back to what it was (yes, I changed the source file name too). Here was the response I received when I couldn't figure out the proper way to do it with the least amount of mess.

I need to roll a page back to a previous version. I changed the page by mistake. How would I go about doing this?
Select "History" (top left hand list), select the version you want, click "edit" and then save the page. That's how I do it - not sure if anyone else knows a better way. AndrewRT
That's the right way.--Dallan

That thankfully answered my question and the pages are back to normal. *Phew*

General Wiki: Tips and Tricks

History Option

To the left of just about every WeRelate page is a History menu option, which leads to the Revision History of that page.

What is the page all about and how do you use it?

This page is for viewing what changes have happened to the page and to help you compare different versions of the page. Viewing the history is the easiest, just click on the History option and the Revision History page opens showing the entire change history from the page's beginning until its most recent version.

What if you want to compare changes that have been made to the page? Say someone made four or five changes to a page and you want to see all of those changes in one comparison instead of looking through all of them individually. There are a couple of ways to do this.

Any comparison can be done with the radio buttons (the little circles that turn green when you click on them). Click on the two revisions you want to compare regardless of where they are in the list and click the Compare selected versions and a comparison page will come up with the older of the two revisions on the left and the more current revision on the right.

You can also use the (cur) and (last) options for quicker viewing.

If you want to compare an old revision with the most current revision:
  • Click on the (cur) option to the left of the old revision.
If you want to compare an old revision with a revision either directly above or below it:
  • Click on the (last) option to the left of the latest of the two revisions.
For example: There are two revisions, one from 15:42, 19 December 2012 and one below it showing 11:51, 18 December 2012, to compare just these two, you want to click on the (last) option by the 15:42, 19 December 2012.

Inserting External Links

How to make it look neat and crisp like Example 1 and not awkward like Example 2.

Example 1:
Missouri Digital Heritage - More than 6.8 million records can be accessed through Missouri Digital Heritage, including the collections of the Missouri State Archives, the Missouri State Library and other institutions from across the state.
Example 2:
Missouri Digital Heritage [1] - More than 6.8 million records can be accessed through Missouri Digital Heritage, including the collections of the Missouri State Archives, the Missouri State Library and other institutions from across the state.

Here's how each example looks on the backend:

Example 1:
[ Missouri Digital Heritage] - More than 6.8 million records can be accessed through Missouri Digital Heritage, including the collections of the Missouri State Archives, the Missouri State Library and other institutions from across the state.
Example 2:
Missouri Digital Heritage [] - More than 6.8 million records can be accessed through Missouri Digital Heritage, including the collections of the Missouri State Archives, the Missouri State Library and other institutions from across the state.

Put the name inside the brackets, but don't forget a space between the URL and the name.

Inserting References to Sources in Body Text

You've seen the body of a page with so much narrative it would make your head spin and scattered among the narrative are footnote links. How are those done? It is pretty simple. They used the ref tag as follows:

<ref name="S1"/> - References S1 in the Sources section of the page.
<ref name="Any other text"/> - Creates a source in the References section which is independent of already created Source.

For something so simple, you'd think it would be simple to remember, but if you don't use them very often... well, you get the idea.

Wiki Tables

Since I seem to return to the help page for this more times than I care to remember, I thought it would be good to put an example here for future reference. How to use a very basic table in wiki format... It's really quite easy, but I always seem to forget one step, that one step that makes it all break.

{| class="wikitable"
| This || Effort
| That || Production
This Effort
That Production

Wiki Page Creation

New U.S. Cemetery Pages

How to Create

New cemetery pages can be created in a couple of ways and I will explain both of them here. These examples use cemeteries in the United States, but the creation method works for any country from what I've been able to determine.

The first method utilizes the Add feature.

  • Click on Add at the top of the page and select Place.
  • Enter the name of the Cemetery in the Name field utilizing the entire name of the cemetery without abbreviation.
  • Enter the City, County, State, Country or Township, County, State, Country, or some lesser variation dependent on how specific the location is able to be. Every effort should be made to include the city or township, but if only the County is know, then enter only the County, State, Country. The more detailed place name is preferred. (City over Township over County)
  • Click Next.
  • Check to make sure whether the Cemetery already exists. If it does, select the cemetery, if not, click Add Page and you will be taken to the Edit page.

The second method is used when a cemetery is created directly on a person's page or some other page, which basically skips the above steps. Simply type the cemetery into the Burial field of an individual's page (Cemetery Name, City/Township, County, State, Country), save the page, then click on the Cemetery pages' placeholder, which will appear red on the individual's timeline. This will take you directly to the Edit page, which is explained next. This method has the advantage of bringing up the names of cemeteries which may already be entered in the automated drop-down selection box which appears as you type in any place. The drawback is that this list only contains the place names which match what you're typing exactly (or if the Cemetery has that exact name listed in it's "Alternate Names" box, which is not as straight-forward to determine from this list). Basically, if someone entered a cemetery as New Hartford Cemetery and you're entering the same cemetery as Hartford Cemetery, the list may not bring up the other cemetery in the automated dropdown box (unless, the New Hartford Cemetery has Hartford Cemetery listed in the "Alternate Names" box on the cemetery page). In any case, if duplicate cemeteries are entered, at some point these cemeteries should be merged when the duplicates are found, but efforts not to create duplicates are greatly appreciated.

What to Include

From here, both methods of creating cemetery pages merge into one, the all-powerful Edit page. The Edit page has a few options and entries that need to be made to create a standard Cemetery page.

  • Type must be filled in with the option: Cemetery.
  • Latitude and Longitude are preferable, but not required to complete the page.
  • Located in is derived from the original entry of the Cemetery.
  • Also Located in is used for more detail about the place that could not be entered into the title. Put the County, State information here. It may seem redundant, but this field flows through to the main page for the County you're editing. Township, State would be an appropriate usage of this place, if the original name created on the cemetery is a city/town/village, otherwise, a link to the County's Category page for Cemeteries should be included on the County's Place page so as to eliminate a huge list on the County's right sidebar. This is a much cleaner method of information presentation than my original assertion.
  • Text box should contain the some of the following:
(Examples use Maple Park Cemetery, Aurora, Lawrence, Missouri, United States):
(Optional) ==Location=== with a brief or detailed description and/or address of where the cemetery may be found on the next line.
(Optional) ==Resources== which could contain some of the following on subsequent lines:
(Optional) *{{bgravescem|62531|Mapel Park Cemetery}} ( add a link to the cemetery's BillionGraves page. bgravescem is the template that WeRelate uses for billiongraves cemeteries. The number between the | | (pipes) is the cemetery ID number at BillionGraves. It can be found in the URL of the cemetery page right after both the cemetery name, MapleParkCemetery/62531 or right after the #cemetery_id=62531.
(Optional) *{{fgravecem|29981|Maple Park Cemetery}} ( add a link to the cemetery's FindAGrave page. fgravecem is the template that WeRelate uses for FindAGrave cemeteries. The number between the | | (pipes) is the cemetery ID number at FindAGrave. It can be found in the URL of the cemetery page right after CRid=. The name at the end of the template is however you want the cemetery to appear on the main page, but keeping it the same name as the Place name you created will likely keep confusion to a minimum in the future.)
(Optional) *[ Rootsweb: Maple Park Cemetery] (...if you want to add a link to some other website that gives information on the cemetery you're creating.)
(Required) [[Category:Cemeteries of Lawrence, Missouri, United States|Maple Park Cemetery]]
(Optional) [[Category:Lawrence, Missouri, United States|Cemetery Maple Park]] This sorts all of the cemeteries to the 'C' slot on the Cemeteries of Lawrence, Missouri, United States Category page. This is not necessary, but I personally find that the Category page is easier to navigate when items are sorted.

Once these are complete, save the page and it's done!

Optional Category Inclusions

Some cemeteries may be further categorized with the following (including example pages):

Ethnic / Religious
[[Category:African American cemeteries|Heuston Cemetery]]
[[Category:Amish cemeteries|Amish Cemetery]]
[[Category:Anglican cemeteries|Trinity Anglican Cemetery]]
[[Category:Baptist cemeteries|South Union Baptist Church Cemetery]]
[[Category:Catholic cemeteries|Calvary Cemetery]]
[[Category:Dutch Reformed Church cemeteries|Wright City Christian Reformed Cemetery]]
[[Category:Episcopal cemeteries|Grace Episcopal Cathedral Columbarium]]
[[Category:Jewish cemeteries|Clifton United Jewish Cemetery]]
[[Category:Lutheran cemeteries|Estherville Lutheran Cemetery]]
[[Category:Mennonite cemeteries|Peters Mennonite Cemetery]]
[[Category:Methodist cemeteries|Hermon Methodist Church Cemetery]]
[[Category:Presbyterian cemeteries|Old Kingsport Cemetery, Kingsport, Sullivan, Tennessee, United States]]
[[Category:Protestant cemeteries|Grace Episcopal Church Cemetery]]
[[Category:Quaker cemeteries|Cedar Creek Friends Cemetery]]
[[Category:Shaker cemeteries|Otterbein-Shaker]]
[[Category:United Church of Christ cemeteries|Swamp Church Cemetery]]
[[Category:Community cemeteries|West Park Cemetery]]
[[Category:Military Cemeteries|Fort Leavenworth National Cemetery Cemetery]]
[[Category:National cemeteries of the United States|Leavenworth National Cemetery]]
[[Category:Family cemeteries|Baker Cemetery]]
[[Category:Private cemeteries|Buena Vista Park]]