Essential Smoke & Mirrors
For your project, the most useful knowledge is not just “desert history” in a broad sense. The real strength comes from fields that explain how land, water, movement, and human use fit together.
The highest-value fields:
- Historical geography.
This is probably the single best umbrella field for your work. It lets you connect routes, settlements, springs, railroads, mining districts, passes, and change land use across time. Your project is already built around corridors, nodes, and regional structure, so historical geography gives the whole thing coherence. - Geology and geomorphology.
These explain why the Mojave looks and functions the way it does. Basin formation, faulting, alluvial fans, playas, dunes, volcanic fields, canyon cutting, and erosion patterns all shape where travel, settlement, water, and industry happen. This field gives your project a physical backbone. - Hydrology.
For a Mojave project, water is destiny. Springs, intermittent rivers, sink systems, groundwater, pluvial lakes, flood channels, and dry lake basins all matter. Hydrology helps explain why camps, roads, ranches, mines, and towns appeared where they did and why some vanished. - Archaeology.
This gives depth before the wagon-road and railroad eras. It helps place Indigenous occupation, trade corridors, seasonal use, rock art, settlement patterns, and long-term human adaptation into the landscape rather than treating history as if it began with Euro-American travel. - Ethnography and ethnohistory.
These are essential because they keep the project from becoming only a transportation-and-settlement story. They help you understand Native place use, regional exchange, plant knowledge, movement patterns, and cultural landscapes in a more grounded way. - Environmental history and historical ecology.
These help track how people and landscapes have changed over time. Grazing, mining, railroads, reservoirs, exotic species, tourism, military use, conservation, and park-making all fit here. This field is especially useful for tying natural and human history together. - Transportation history.
This is already one of your strongest existing lanes. Wagon roads, trails, rail corridors, depots, highway realignments, and interstates are central to your project. This field helps explain movement, logistics, and corridor succession. - Cartography and GIS.
Even if used simply, these are extremely valuable. Your project is structural by nature, so maps are not decoration – they are evidence. Good spatial thinking will strengthen every page, especially the corridor, basin, and node pages. - Archival research and source criticism.
This is what keeps the project honest. Knowing how to weigh maps, reports, local histories, memoirs, newspapers, surveys, and agency documents will protect you from drift, folklore creep, and repeated errors. - Public history and interpretation.
This matters because your work is not just research – it is a presentation. You are building something people can read and navigate. Public history helps turn hard material into a clear, usable interpretation without flattening it.
The best supporting fields for your project are paleontology, biogeography, literary studies, photography, and design/illustration. These may not be the main frame, but they add texture, visual force, and cultural reach.
If I had to rank the most beneficial fields overall for your project, I would put them in this order: historical geography, geology/geomorphology, hydrology, archaeology/ethnohistory, transportation history, and cartography.
In plain terms: geology tells you what the land is, hydrology tells you how it works, archaeology tells you who used it earliest, transportation history tells you how movement changed it, and historical geography ties the whole system together.
how about for system design and html coding?Thought for a few seconds
Yes. For your project, system design and HTML coding are not side skills. They are part of the structure that makes the whole thing usable.
For system design, the most helpful knowledge areas are these:
- Information architecture.
This is one of the most important. It helps you decide how pages relate to one another: system -> spine -> corridor -> node -> site-core -> support page. For your project, this is what prevents drift, duplication, and orphan pages. - Taxonomy and classification design.
You have a large body of material across geology, railroads, hydrology, Indigenous corridors, parks, towns, and sites. Good taxonomy helps you decide what belongs where, what counts as a parent page, what should be a child page, and what should just be a support note. - Navigation design.
Your project depends on people being able to move through it logically. This includes breadcrumb structure, related-page logic, index pages, thematic indexes, and cross-links that are controlled rather than random. - Content modeling.
This is the discipline of deciding what a page type contains. For example, every corridor page gets geography, early travel, rail development, highway era, connections, and significance. Every site-core page gets settings, history, physical context, and related nodes. This makes the site scalable. - Editorial systems thinking.
This matters a great deal to you. It means building rules for page identity, length, split triggers, naming conventions, citation handling, and maintenance. In old-fashioned terms, it is the difference between a library and a junk drawer. - Database thinking, even without a formal database.
Even if the site is mostly hand-built HTML, it helps to think in structured fields: title, alternate names, district, corridor, period, themes, related nodes, sources, coordinates, tags. That mindset makes later expansion far easier. - User experience design.
Not modern fluff – plain practical usability. Can a reader tell where they are? Can they move outward or inward from a page? Can they find rail pages separate from ecology pages? Can they tell the difference between a corridor and a town? That is UX.
For HTML coding, the most useful fields are these:
- Semantic HTML.
Very important. Use proper headings, lists, paragraphs, nav, article, section, figure, footer, and so on. This gives pages a clear structure, improves accessibility, and makes the site easier to maintain. - CSS layout and visual hierarchy.
Even if the site stays simple, you need control over spacing, headings, sidebars, image captions, quote blocks, and metadata. Good CSS makes an old-style content site feel solid rather than cluttered. - Accessibility.
This is underrated and highly useful. Clear heading order, alt text, readable contrast, keyboard-friendly navigation, and sensible link text all improve the site for everyone, not just assistive users. - Responsive design.
Your pages should still work well on phones and tablets without becoming messy. This does not require flashy modern design. It requires dependable layout rules. - Basic SEO and metadata structure.
Title tags, meta descriptions, canonical thinking, heading hierarchy, internal links, and clean page focus all help search engines understand what each page is about. For a large historical site, that is important. - Front-end performance.
Lean pages, properly sized images, limited scripts, and clean markup matter. A project like yours benefits from fast-loading, durable pages more than from heavy interactive features. - Template design.
This may be the single most useful coding habit for you. Build repeatable page templates for corridor pages, site-core pages, timeline pages, district indexes, and bibliography/support pages. That gives the whole site consistency.
If I were ranking the most valuable knowledge for your project specifically, I would put them like this:
For system design:
information architecture, content modeling, taxonomy, navigation design, editorial governance.
For HTML coding:
semantic HTML, CSS layout, accessibility, responsive design, metadata/SEO, performance.
In plain terms, system design decides what the project is, while HTML decides how clearly that structure is expressed on the page.
For your particular project, the strongest path is probably this:
Build the system like an archive.
Build the navigation like an atlas.
Build the HTML like a durable reference site.
That approach fits your material better than chasing trendy web design.
How about for photography and map graphiicsThought for a couple of seconds
Very much so. For your project, photography and map graphics are not decoration. They are evidence, orientation, and interpretation.
Photography helps most when it draws from these knowledge areas:
- Documentary photography.
This is probably the best fit. It teaches you to record a place clearly and honestly: what is there, its condition, how it sits in the landscape, and what details matter. For site-core pages, this is gold. - Landscape photography.
Useful not just for beauty, but for scale, landform, weathering, basin structure, passes, washes, dunes, rail grades, and settlement setting. A good landscape photograph can explain geography faster than three paragraphs. - Architectural and vernacular-structure photography.
Very important for depots, cabins, mining ruins, roadside remains, ranch structures, bridges, culverts, retaining walls, and old commercial buildings. This helps you show how people actually occupied and modified the desert. - Field documentation methods.
This means knowing how to photograph a site systematically: wide shots, mid-range context shots, close-up details, orientation views, approach views, inscriptions, construction materials, damage, and surroundings. Old survey habits still work because they are sensible. - Visual storytelling.
A single image is useful, but a sequence is stronger. For example: approach to a site, site in setting, key feature, detail, then outward view showing its corridor relationship. That turns photos into interpretation. - Lighting and seasonal awareness.
In the desert, light can make or ruin a photograph. Early and late light bring out relief, texture, trail traces, rock art surfaces, ruins, and fault scarps. Midday light often flattens everything into mush. - Basic photo editing and archival practice.
Not flashy effects. Just careful cropping, exposure correction, color restraint, file naming, captions, dates, and location notes. This keeps the image library useful over time.
For map graphics, the most helpful fields are these:
- Cartography.
This is the big one. Cartography teaches selection, hierarchy, scale, labeling, symbol use, and clarity. A map should answer a question, not merely exist. - GIS thinking.
Even if you are not running a full GIS workflow every day, thinking in layers is extremely useful: hydrology, railroads, roads, ecosections, protected lands, settlements, faults, mining districts, Indigenous corridors. That matches your whole project structure. - Relief and terrain interpretation.
You work in a landscape where topography matters constantly. Passes, basin edges, fans, playas, escarpments, springs, and canyon mouths all become clearer when you know how to show terrain well. - Historical cartography.
Very valuable for your project. It helps you compare older routes, naming conventions, settlement shifts, rail alignments, and vanished places against the modern landscape. This is one of the strongest ways to show continuity and change. - Diagram design.
Not every map has to be geographically exact in the same way. Some of your best project graphics may be system diagrams: spines, corridor relationships, node hierarchies, basin connections, transport succession. Those are part map, part explanatory diagram. - Labeling and annotation.
This is more important than many people think. A good label can quietly teach geography. A bad one can clutter the whole page and turn a strong map into a headache. - Color and contrast control.
Maps need discipline. Too many colors, line types, textures, and labels can bury the point. For your work, restrained palettes and clear hierarchy would probably serve better than modern overdesigned map styling.
For your project specifically, photography is strongest when it does four jobs:
show setting,
show evidence,
show condition,
show relationship to the wider corridor or basin.
Map graphics are strongest when they do four jobs:
locate,
compare,
connect,
simplify.
So if I rank the most beneficial knowledge areas for each:
For photography:
documentary photography, field documentation, landscape composition, architectural recording, and archival captioning.
For map graphics:
cartography, GIS/layer thinking, historical cartography, terrain representation, diagram design.
In practical terms, your project would benefit a lot from building two consistent visual systems.
First, a photography system:
site overview,
approach view,
key feature,
detail shot,
outward context view.
Second, a map system:
regional locator map,
corridor map,
node map,
site detail map,
system diagram.
That would give the whole project a steady backbone. The old rule still holds: a good photograph shows what was there, and a good map shows why it matters.
—
This is a list of things I have learned throughout my varied technical career and interests that have led me to do what I do the way I do. God Bless America and the First Amendment.