This repo provides a ton of great resources, but we should try to provide a few good first steps to getting started with using this collection of information to get started.

For example, I would suggest starting with "How to start" and then moving on to free learning in the "challenges section"

Description:

• Add colors to the UIColor extension, go through codebase and make sure all colors reference the style guide.
• Same things for fonts, using a UIFont extension
• Fonts and colors should be on Figma, ask designers if needed

An user should be able to get an archive of:

• All original track files
• Tracks artworks
• User avatar
• user.json with profile
• tracks.json with tracks infos

Possible issue : the archive will be more-or-less the same size of all the user tracks, disk space should be checked before generating it through celery.

We will introduce the celery beat to periodically remove the archive after

At the moment you can't just run make database unless you already have golang-migrate installed.

The Makefile should allow someone to just run that command and have all the migrate tools installed for them, but it doesn't at the moment.

We currently support Twitter urls in the supporters config so that people can link to their accounts; we should make this more generic so that people could choose to link to other social services or even a personal site.

So we can ask event organizers to link back to our site either with a text link or by using our logo.
We should also be able to set it as a favicon.

The current template issue has irrelevant information and bad formatting.
We should just keep it simple.

https://github.com/stevemao/github-issue-templates

1. Pick an episode of a Changelog podcast from changelog.com/podcasts and find the corresponding markdown file in this repository: github.com/thechangelog/show-notes
2. Listen to the podcast and improve the show notes by:
   • Fixing broken links
   • Adding links to referenced URLs, projects, etc.
   • Fixing typos

This is part enhancement, part bug-fix really. Some feeds use a generic filename for the download file, such as media.mp3. One example is the Adam Buxton podcast. The RSS feed is here: https://rss.acast.com/adambuxton

So for example the URL is https://media.acast.com/adambuxton/ep.41-marcmaron/media.mp3 and the file is saved as media.mp3. This is obviously not very useful or helpful to the user

The project is just in the initial stage. I have my own ideas to have better structuring than the current format. Although it's a good format for the beginning, there is definitely room for improvements.

All suggestions are welcome from keeping it like as it is to create a table with user feedback and more. I will write a detailed document with my thoughts about organizing it but I am open to a