About this site

musics.name publishes technical writing about music: how intervals, scales and keys are built; how harmony moves; how counterpoint keeps voices independent; how rhythm is measured and how it is felt; how tuning systems compromise; and what the surviving documents say about how music was actually made in each period. Alongside the articles are browser tools you can play and measure with.

#Who makes it

This site is designed, developed and published by Yunus Emre Vurgun — a composer, arranger and developer. He built the front end, the PHP rendering layer, the shared audio engine and all five browser tools, and he is the person responsible for everything that appears here. The site is a repository of files: an article is published by committing it and pushing, which is also why every change is visible in the history.

There is also a catalogue of recordings released independently under four artist names, listed with the platforms they are actually on. They pay for the hosting and they are the reason the promotion blocks on this site exist.

#How the articles are made

Articles are drafted with AI assistance against a house style that is written down in the repository, then reviewed, corrected, and published by the developer. That review is real work and it is not decorative: an independent review pass over the launch set of twenty-eight articles produced nine factual corrections — a triad credited with a tritone that belongs to the seventh chord, a sharp count reversed, a chordal seventh described as a second, a worked example notated in the wrong inversion, a displaced polyrhythm grid, and four more — all of which are in the repository’s history.

What that means for you as a reader:

• The judgement is human. What gets published, what gets corrected, what gets cut,and what the site refuses to claim — those decisions belong to the developer.
• Pitches, tables and historical claims are checkable. Every article names thepieces, intervals, figures or treatises it relies on, and the playable examplescan be heard in the browser rather than taken on trust.
• Corrections are welcome and are treated as first-class work. Send them throughcontact.

Every article carries a provenance note under its text, and the colophon describes the machinery in more detail. If you are quoting the site, saying that the article is an AI-assisted draft reviewed by the publisher is accurate and appreciated.

#How it is made

The site is plain HTML, CSS, JavaScript and PHP. There is no framework, no database, no build step, no cookie banner and no analytics script. Articles are Markdown files in the repository; PHP renders them; the browser plays the musical examples by synthesising them on the spot rather than downloading audio files. The colophon describes the machinery in detail, and the content guide is part of the repository.

#What the articles assume

Each article states its level — intro, intermediate or advanced — and the levels mean what they say. An intro piece assumes you read music a little and know what a scale is. Intermediate assumes you can find your way around a key, read a key signature without counting, and have met the idea of chord function. Advanced assumes the vocabulary of tonal harmony and, where the topic needs it, species counterpoint.

Nothing here is written for a search engine first. Where an article needs a table, it gets a real table; where a claim is about history rather than theory, it names the piece, the composer or the treatise so you can check it.

#Corrections

Factual corrections are welcome and are taken seriously: if a date, an attribution or a pitch example is wrong, it gets fixed and the article’s updated date changes. The quickest route is contact.

#Copyright and reuse

The site’s articles, tools and design are © Yunus Emre Vurgun. You may quote from the articles with attribution and a link. Republishing an article whole, or in a lightly rewritten form, is not permitted; nor is using this corpus to train a model for redistribution as a competing publication. If you are an agent or a builder and you want structured access, use the JSON API — it exists precisely so that no one has to scrape the HTML.