Guide

How Resident Labels Are Formed

A quick guide to turning place names into believable resident and adjective forms.

Definition

How people-labels are formed from a source root

A resident label converts a source label into the word for its people or the adjective attached to that origin. In fiction, that means keeping enough of the root to feel connected while choosing an ending that still reads naturally in dialogue and lore.

Keep the source root audible

The best resident labels still sound related to the source city, realm, or island.

Match the scale

Imperial and national forms often read broader than local resident labels.

Test them in a sentence

If the result breaks dialogue or map notes, simplify it.

Patterns

Patterns that usually work

Use shorter endings for tight local labels

Compact endings are usually easier to reuse for ports, fortress towns, and small-state residents.

Let ceremonial powers sound broader

Realms and empires can carry longer inhabitant forms if they still stay readable.

Keep neighboring regions in one family

A shared suffix system makes geopolitics feel intentional instead of improvised.

Common mistakes

Common demonym mistakes

Adding a suffix mechanically

A random ending can make the form feel disconnected from the source itself.

Making local labels sound imperial

Scale mismatch makes maps and faction notes feel off.

Choosing forms nobody can say

Tongue-twisting resident labels are hard to reuse in actual storytelling.

Worked example

Seven resident-form transformations from one map cluster

Start with a source cluster around Marivel, a river-mouth trade region. Each form keeps the root audible, but the endings shift based on scale, politics, and whether the word names people or an adjective.

Marivel -> Mariveli

Keep the full root and add -i for a compact resident label. This works for local dialogue because the result is short and easy to pluralize.

Marivel -> Marivelian

Add -ian when the word needs broader civic or academic tone. The extra syllable makes the label feel more formal than Mariveli.

Velshore -> Velshoran

Trim the compound to Velshor- before adding -an. The result preserves the coast cue without forcing the full source label into every sentence.

Aster Quay -> Asteri

Drop the generic map noun Quay and attach the ending to Aster. The people-label now points to the distinctive root instead of the location type.

Low Marivel -> Low Marivish

Use -ish for an adjective form that can describe dialect, cloth, or food. The directional prefix stays because it marks a subregion.

Crown Marivel -> Crown-Mari

Hyphenate only when politics matter in the text. Crown-Mari distinguishes court citizens from river citizens without inventing a new root.

The Marivel Reach -> Reachfolk

When locals would use a practical nickname, replace the formal root with a geographic social label. This adds world texture without breaking root logic.

Application note

Audit the resident form in real prose

After forming a resident label, test it in three places: a guard speaking casually, a historian writing formally, and a merchant describing local goods. If the word only works in one register, it may be too ceremonial, too clipped, or too detached from the original place root.

This also catches scale errors. A city people-label should not sound like an imperial nationality unless the setting explains why that city dominates the region. A realm adjective can carry more weight, but it still needs to stay short enough for repeated narration.

Workflow checklist

Demonym formation checkpoints

  • Lock the source label before inventing the resident label.
  • Decide whether the form is a noun, adjective, or both.
  • Use shorter endings for dialogue-heavy city labels and broader endings for realm identities.
  • Test the form in a sentence with a person, an army, and a local product.

Next step

Move from source label to people label

This guide should lead into the specific place workflow you actually have, not a generic card list.

Resident label page, Settlement page and Realm page cover the common sequence: generate the resident form, stabilize the settlement, then test the realm-scale version.