Understanding Database Normalization: The Normal Forms
a { text-decoration: none; color: #464feb; } tr th, tr td { border: 1px solid #e6e6e6; } tr th { background-color: #f5f5f5; }
a { text-decoration: none; color: #464feb; } tr th, tr td { border: 1px solid #e6e6e6; } tr th { background-color: #f5f5f5; }
a { text-decoration: none; color: #464feb; } tr th, tr td { border: 1px solid #e6e6e6; } tr th { background-color: #f5f5f5; }
Design the website around things that exist in the subject matter, not around pages, menus, or articles.
Ask:
"What are the things I want to know about?"
not
I did a bunch of brainstorming with my buddy Coppy, and we came up with these observations and strategies:
What began as a discussion about migrating old Gallery2 and Drupal sites evolved into a broader conversation about information architecture, data modeling, and the long-term sustainability of hobby websites.
This page collects commonly used music symbols — especially accidentals, clefs, and notation marks — so they’re easy to copy and paste into web content, documentation, or project notes. All characters below are standard Unicode and work in CKEditor 5, HTML, and most text fields.
♯ ♭ ♮ 𝄪 𝄫 ♪ ♫ 𝅘𝅥 𝅗𝅥 𝅝 𝄞 𝄢 𝄐 𝄁 𝄂 𝄆 𝄇
These symbols modify pitch and are the most frequently needed in mechanical‑music documentation.
These pages have miscellaneous useful code, snippets, and other stuff
Alright David — I’ve ingested the entire spreadsheet, and here’s the good news: you already have all the raw ingredients for a world‑class organ‑pipe database. What you don’t have yet is structure. Your sheet mixes:
• physical pipe geometry
• musical identity
• rank/stop identity
• instrument identity
• wiring + controller mapping
• presence/condition
• voicing notes
• and even percussion + function controls
…all in one giant flat table.