Template:MuGlobe/genre
This is the published first-pass outline for Genre articles on MuGlobe.com, extrapolated from Ed's Country template at his request on October 17, 2026.
Required sections must contain substantive text. Optional sections may be omitted; when included they must contain substantive text. Keep sections in the listed order. Subheadings are allowed within each section. Cite sources and use representative musical examples where available.
- Summary: Introduce the genre and its recognizable musical identity.
- Contemporary and trending: Describe its present musical life and recent developments; acknowledge limited or revival activity where appropriate.
- History: Explain origins, development and influences without inventing a single birthplace or date when these are uncertain.
- Musical characteristics: Describe rhythm, instruments, singing, form or dance in approachable language.
- Geography and communities: Distinguish origin, later adoption and diaspora scenes, linking countries and regions.
- Artists: Introduce representative musicians and groups and examples of their music.
- Related genres (optional): Explain useful connections and distinctions.
These are editable editorial guidelines. Existing articles retain their recorded template version until deliberately migrated.
- Hotspot mushrooms: The final section represents inferred musical landscapes, not a catalogue of cited cities. Its seven-column editable table contains ID, Location, Latitude, Longitude, Radius (km), Strength and Notes. Begin with regional understanding, synthesize varied perspectives and lived knowledge, then choose the fewest useful broad fields. Nearby strong cities generally indicate a connected heartland including intervening communities. Sources are not a field or a per-row publication gate.
The retained article bibliography can support the broader narrative. Radius marks the zero edge of a linear fade; review the entire regional field rather than only its center. Coordinates remain manually authored and the compiler remains deterministic.
Representative performances supplies the editable genre playlist. Each row contains artist, title, canonical YouTube embedded player URL and explanatory notes. Native citations document the recording and its relevance. Explicit compilation publishes validated entries to the globe; ordinary edits never regenerate map assets.
Listening correction — October 18, 2026
Curate 1–10 specific recordings with artist, title, canonical YouTube embed URL and notes. Verify the exact recording's musical identity and local scene, not only its artist or URL metadata. Keep useful historical and live examples. For default listening, use the last ten years: popular music needs both recent original repertoire and recent recording; traditional/classical repertoire may be older but its recording must qualify. Uploads, remasters, compilations and later live versions do not reset the original popular repertoire date. Unknown dates remain unknown. Prefer a suitable prompt-start studio/official recording first; good live performances belong later in the playlist and must not be deleted simply for being live.
The listening profile describes how this genre is used. Repertoire is popular, traditional or classical. Field use is regional or context-only: broad umbrella/uncorroborated fields are contextual evidence and cannot establish local dominance. Explain this judgment in Notes. Neither field is an audience measurement.
| Repertoire | Field use | Notes |
|---|
Each track has its own Repertoire kind (popular, traditional or classical); a genre may contain more than one. Dates preserve known precision: YYYY-MM-DD, YYYY-MM or YYYY; enter unknown otherwise. Format is audio, music-video, live or unknown. Opening is prompt, delayed or unknown; record actual evidence, never infer a prompt start solely from the format. Places use semicolon-separated country:Name or region:ID keys supported by the musical scene, not nationality or concert location alone. Fit is supported, pending or rejected. Evidence contains supporting HTTPS links; Review note explains what those sources establish and any limits. Supported means the specific recording was reviewed; oEmbed alone is insufficient. Add native footnotes in Notes for readers. The explicit compiler retains exact native revisions; ordinary builds never author content. Historical/undated examples remain separate from automatic contemporary listening.
| Artist | Performance / song / title | Embedded player URL | Notes | Repertoire kind | Repertoire date | Recording date | Format | Opening | Places | Fit | Evidence | Review note |
|---|