Proposed Developments and Enhancements

This page records possible future developments, improvements, and design ideas for the music archive website. These are not all urgent tasks. Some are small practical improvements, while others are longer-term ideas that may or may not be needed as the site grows.

Last Updated: 6 July 2026

Immediate / Small Improvements

  1. Make music-list.php page title dynamic. The visible page heading is already dynamic, but the browser title can also be made dynamic.
  2. Hide the “groups of twelve” text on filtered pages. Pages such as instrument, genre, and status currently show all matching tracks on one page, so the wording about groups of twelve may not always apply.
  3. Add “no tracks found” messages. For example, a valid URL such as music-list.php?view=instrument&value=Octopus should say that no tracks were found, rather than showing an empty page.
  4. Make value handling safer. Use $_GET['value'] ?? '' rather than plain $_GET['value'], so the page does not produce warnings if a value is missing.
  5. Add a top anchor. Since the page includes “Back to top” links, add either <body id="top"> or <a id="top"></a> near the top of the page.
  6. Add redirects for old or mistaken pages. For example, consider redirecting contact.php to feedback.php, and possibly contests.php to contents.php.

music-list.php Improvements

  1. Keep the current valid / invalid view system. Known views include title, ref, recent, lyrics, instrument, genre, and status. Anything else should show the friendly “Sorry” page.
  2. Possibly refactor filtered views later. Instrument, genre, and status currently each have their own query. This is clear and readable. Later, repeated code could be reduced if it becomes worth doing.
  3. Possibly paginate filtered views later. At present, filtered views show all matching tracks on one page. That is fine while the numbers are small.
  4. Preserve value in pagination links if filtered views are paginated later. For example, the page should preserve view=genre&value=Adult Contemporary&page=2.
  5. Possibly make headings more specific. For example, Tracks for Adult Contemporary could eventually become Genre: Adult Contemporary, and Tracks for Sketch could become Status: Sketch.

contents.php Improvements

  1. Add links under Composition Status. Statuses should link to pages such as music-list.php?view=status&value=Sketch.
  2. Keep Genres and Instruments linked. These now link through to filtered music-list.php pages.
  3. Possibly make Overall totals linkable. For example, Tracks with Lyrics could link to music-list.php?view=lyrics, and Total Tracks could link to music-list.php?view=title.
  4. Possibly add a Tracks with Artwork view. A future view could be music-list.php?view=artwork.
  5. Possibly add a Tracks with YouTube view. A future view could be music-list.php?view=youtube.

Track Page Improvements

  1. Show artwork only when artwork exists. The track page should not show an empty artwork section.
  2. Use the images folder for artwork. Artwork files are stored in images/, not in a separate artwork/ folder.
  3. Make empty sections disappear. If a track has no YouTube video, lyrics, comments, artwork, or feedback, avoid showing an empty heading.
  4. Possibly improve YouTube display. Only show the YouTube section when there is actually a YouTube link.
  5. Display genres, status, and instruments more neatly. Later, these could become clickable links back to filtered music-list.php pages.
  6. Add previous / next track navigation. For example: Previous track, Back to list, Next track.
  7. Improve track title and browser title. The browser title should ideally reflect the current track.

Feedback System Improvements

  1. Filter public feedback by visibility. Public track pages should only show feedback where is_visible = 1.
  2. Admin hide / unhide feedback. Feedback should be hideable without deleting it.
  3. Admin delete feedback. This is a possible future admin action, but should be handled carefully.
  4. Confirmation before deleting feedback. Use a browser confirmation before permanently deleting a feedback record.
  5. Include Feedback ID in notification emails. The ID should be added after the database insert, using the last inserted ID.
  6. Admin feedback list page. A page for listing feedback records in date order.
  7. Admin feedback view page. A page for viewing one feedback record in detail.
  8. Make Track ID clickable in feedback admin. Where feedback relates to a track, the Track ID should link to that track page.
  9. Show dashes for general feedback. General feedback may not have a track ID or track title, so display a dash instead of a blank value.
  10. Possibly add admin notes later. This would allow private notes about how feedback has been handled.
  11. Possibly add feedback categories later. For example: General comment, Bug report, Track feedback, or Suggestion.

Admin and Security Improvements

  1. Protect admin pages. Admin feedback pages should eventually be hidden from the public.
  2. Create a simple admin login. One administrator account is enough for the current stage of the project.
  3. Use sessions. A session can record whether the admin user is logged in.
  4. Create includes/admin-auth.php. Admin pages could include this file at the top to protect them.
  5. Possibly create an admin folder. Admin pages could later move into an admin/ folder.
  6. Avoid multiple users and roles for now. Do not overbuild the admin system until there is a real need.
  7. Create an admin dashboard. A simple page linking to feedback admin, track admin, developer pages, and other tools.

Database and Content Management Improvements

  1. Composition status definitions page. A page explaining what different statuses mean.
  2. Review actual status names. Current statuses include items such as Developing, Experimental, Fragment, Draft, Released, Sketch, and Finished. These may need rationalising later.
  3. Possibly improve the status model later. At present, one track has one status. A more flexible model is possible later, but only if needed.
  4. Add track editing / admin pages. Eventually, tracks could be edited through web forms rather than directly in the database.
  5. Add artwork management. Allow artwork to be uploaded, selected, or changed through an admin page.
  6. Add YouTube management. Allow YouTube links to be added or edited through an admin page.
  7. Add genre and instrument management. Allow genres and instruments to be added or removed from tracks through the site.
  8. Add validation for missing audio files. Check whether every database filename exists in the audio folder.
  9. Add validation for missing artwork files. Check whether every artwork filename exists in the images folder.

Search Improvements

  1. Search by reference. This has already been discussed and added.
  2. Search by title. This is already part of the search system.
  3. Search by instrument. This is already part of the search system.
  4. Search by genre. This is already part of the search system.
  5. Search by composition status. This is already part of the search system or has been discussed.
  6. Improve search help text. The search page should clearly explain what users can search for.
  7. Possibly search lyrics later. This could be useful, but is not urgent.
  8. Possibly search comments later. This may be useful for archive work.
  9. Possibly highlight search terms in results. This would be a nice future improvement, but is not essential.

Navigation and Menu Improvements

  1. Browse dropdown menu. The Browse menu includes options such as By Title, With Lyrics, Recent, and By Ref.
  2. Keep By Ref lower in the menu. By Ref is especially useful for internal work, but probably less important for general visitors.
  3. Possibly add Browse by Genre. This may not be necessary because the Contents page already provides genre links.
  4. Possibly add Browse by Instrument. This may not be necessary because the Contents page already provides instrument links.
  5. Possibly add Browse by Status. This may not be necessary because the Contents page can provide status links.
  6. Separate public menu and developer menu. This is already being done using includes/menu.php and includes/menu-dev.php.

Developer Documentation

  1. Developer Manual. A central place to document the structure and thinking behind the website.
  2. Project philosophy page. The site is a living archive and workshop, not just a polished catalogue.
  3. Development philosophy. The guiding principle is to change one thing, test it, and then move on.
  4. Database development history. Document why tables and fields were added.
  5. Composition status definitions. Document what each status means.
  6. Administration design page. Document how the admin system should grow slowly and practically.
  7. Project progress summary. Record what has already been built.
  8. Handling invalid music-list.php requests. Document why invalid views show a visible error instead of silently defaulting.
  9. Possibly create a site roadmap page. This could list planned features and their status.

CSS and Design Improvements

  1. Use table classes rather than global table styling. For example, use separate classes such as doc-table, admin-table, and detail-table.
  2. Improve admin table styling. This would be useful for feedback lists and other admin pages.
  3. Improve track artwork sizing. Artwork is already working, but could be tuned later for desktop and mobile.
  4. Fix spelling of lable eventually. The correct HTML element is label. This can be corrected later if it appears in the code.
  5. Continue mobile layout improvements. Keep pages readable and easy to use on smaller screens.
  6. Keep the light, readable design. The current white background, dark text, and simple structure suit the project.

Technical Hygiene

  1. Use dynamic CSS and JavaScript cache busting. This is already being done with filemtime().
  2. Canonicalise www and non-www addresses. Choose either davidwhiteuk.com or www.davidwhiteuk.com and redirect the other.
  3. Add redirects for legacy pages. For example, redirect contact.php to feedback.php.
  4. Possibly add a simple site_log table. This could record Information, Warning, Error, and Security events.
  5. Avoid blank screens. The work on music-list.php has already helped with this principle.
  6. Display friendly errors. The “Sorry” page in music-list.php is a good example.
  7. Do not silently default invalid URLs. Invalid URLs should show a visible message rather than pretending to be another valid page.

Bigger Future Possibilities

  1. Create a proper admin area. Manage tracks, feedback, genres, instruments, statuses, artwork, and YouTube links.
  2. Create a track inventory page. An administrative list of all tracks, possibly showing missing information.
  3. Create missing information reports. For example, tracks without lyrics, artwork, status, genres, instruments, or comments.
  4. Create a public / private distinction. Some tracks may eventually be hidden from public view while remaining in the archive.
  5. Add is_visible or is_public to audio files. This would be similar to the visibility field used for feedback.
  6. Add date fields. For example: created_at, updated_at, and published_at.
  7. Add project notes or history per track. Each piece could have its own development log.
  8. Add collaboration notes. Useful where Mary or others give feedback.
  9. Add richer categorisation. For example: mood, tempo, style, purpose, completeness, vocal / instrumental, and similar information.
  10. Add downloadable inventory or export. For example, export the track list as a CSV file.
  11. Add sitemap and SEO improvements. This is not urgent, but may be useful as the public site grows.
  12. Add a better 404 page. A friendly site-wide not-found page would improve the visitor experience.
  13. Keep documenting decisions as the site grows. Documenting why decisions were made is one of the strongest features of the project.

Suggested Next Practical Priorities

The most useful next practical improvements are probably:

  1. Make the music-list.php browser title dynamic.
  2. Hide the “groups of twelve” text on filtered pages.
  3. Add no-results messages for valid filtered pages with no matching tracks.
  4. Add a contact.php redirect to feedback.php.
  5. Begin thinking about admin protection.

These are suggestions rather than requirements. The project should continue to grow slowly, with one change made and tested at a time.