Content type
Wiki explainer
Primary use
Use this page to compare source lanes, place anchors, and wording limits before repeating a historical claim as settled.
What this page adds
It should add source-aware context, place anchors, wording limits, and a clearer next step than a raw claim or isolated source link can provide.
Evidence level
Starter
Claim status
Open
You should leave with a narrower question, a clearer place context, and a better sense of what the current source trail can support.
Overview
Contact-era history in Florida and Georgia should be written as disruption, negotiation, survival, coercion, missionization, alliance, war, and record change. Colonial records can be important, but they do not contain every Native, African, or local voice.
What this page adds
- It turns a topic, place, or naming question into a source-led learning page instead of leaving it as a vague claim or isolated citation.
- It separates what the current record can support from what still needs comparison, correction, or stronger evidence.
- It gives readers a next-step research path instead of pretending the page is the last word.
What this helps you learn
- Contact-era pages should name the place, people, date range, and source type before making broad claims.
- Spanish, French, British, mission, military, and traveler records can each preserve different details and omissions.
- Timucua, Apalachee, Muscogee, Seminole, Black, African, and Atlantic histories intersect in some places, but each needs its own evidence trail.
Careful claims
- Do not treat colonial records as neutral or complete.
- Do not merge Timucua, Apalachee, Muscogee, Seminole, Mexica, Muur, Moor, and Black American histories into one unsupported continuum.
- Do not use contact-era context to certify identity, ancestry, tribe, nationality, DNA conclusions, legal status, descent, or membership.
Research path
- Build a place timeline before interpretation: date, source creator, people named, event, and claim limit.
- Pair colonial summaries with archaeology, park interpretation, living-community language, maps, and source-review notes.
- Send translation, sacred-site, missionization, or identity-sensitive wording to Fact Check before strengthening it.
Reader quality check
- Can you name the exact place, period, institution, or source type this page is using?
- Can you separate a direct source detail from an interpretation or community-memory reading?
- Can you identify which sentence would need a Source Table, Place Packet, or Claim Review Card before reuse?
- Can you explain what would change the wording: a new source, a contradiction, a boundary change, a name variant, or a privacy concern?
Before reusing this page
- Copy the claim only with its evidence label, place context, and uncertainty note.
- Check whether the page is explaining a source, a memory lane, an interpretation, or a working hypothesis.
- Use Source Review before turning the page into stronger identity, ancestry, legal-status, descent, DNA, membership, or Nation-language wording.
- Use Community Notes or Fact Check if a missing source, changed boundary, name variation, or contradiction would alter the public wording.
Source trail
- FOBA St. Augustine Area hub – Contact, fort, mission, refuge, and free Black settlement source trail.
- FOBA Jacksonville-Timucuan hub – Timucuan, Fort Caroline, Kingsley, marsh, river, and coastal context.
- FOBA Tallahassee-Lake Jackson hub – Lake Jackson, Anhaica, Apalachee, and Mission San Luis pathway.
What remains open
This starter should be treated as a working research surface. Dates, naming, family continuity, identity-adjacent conclusions, and disputed interpretation may still need Source Review, Fact Check, Community Notes, or stronger corroboration.
Evidence note: This starter entry is educational. Add sources, dates, maps, Community Notes, and Fact Checks as research develops.