1 - Building a Worship Resource Library

The author's church has used various methods to store music resources, currently using OneDrive with different formats for chords and scattered notes for the brass section. The author proposed a project to improve the process and built a minimum viable product (MVP) using JavaScript, EJS, and MongoDB, which was approved by the music director. The MVP aims to centralize chord and wind note storage with tags and labels for quick song retrieval. The author brainstormed requirements, sketched a low-fidelity wireframe, and switched from the Waterfall Model to Agile Methodology to tackle basic functionality first. The main feature is adding a song with relevant information, including title, key, chords, wind notes, and tags. The second most important feature is the 'tags' system, which allows filtering songs by properties, such as brass endings or ministry themes. The author is still determining how to handle different song instances and is considering admin controls for key transpositions. The next steps include developing authentication and JWT. The author has started building the backend and a basic frontend. The project aims to improve the church's music resource management and will involve incremental improvements and refinement of features.