This repository should use e.g. Heroku review apps in PRs and maybe auto linting

We could reduce the server CPU use if we cached the database results on the front page

Installation on macOS is hard because Apple is making it harder over time unless we pay them.

Users need to install normally by opening the disk image and dragging it to Applications, then go into the Applications folder and try to open the app once, then it shows this:

then they need to right-click on the app and click Open, then this appears:

and they need to click "Open" again.

This is true for a lot of programs, so many users are already aware that this is how to run them, but less experienced users may benefit from this knowledge.

I think the ones in the features section don't work but needs investigation

This seems inconsistent. Sometimes on the forum, certain requests break because they are trying to load them from http despite being on https. I have just noted it on https://universalmediaserver.com/forum/viewtopic.php?p=43161&sid=9b742d6706328c99d796ffea8d4ba94c#p43161

The console shows entries like this:

Mixed Content: The page at '<URL>' was loaded over HTTPS, but requested an insecure stylesheet '<URL>'. This request has been blocked; the content must be served over HTTPS.
/forum/viewtopic.php?f=11&t=13377&e=1&view=unread#unread:1 Mixed Content: The page at 'https://universalmediaserver.com/forum/viewtopic.php?f=11&t=13377&e=1&view=unread#unread' was loaded over HTTPS, but requested an insecure script 'http://www.universalmediaserver.com/assets/vendor/jquery/jquery.min.js'. This request has been blocked; the content must be served over HTTPS.

but the weird thing is in the code it shows:

<script src="/assets/vendor/jquery/jquery.min.js"></script>

so I'm not sure why the browser is choosing to load over http instead of https in that case.

It may be a bug with Chrome/ium (I'm using the Brave browser) but we can maybe work around it by hardcoding the https instead of using a relative URI. Not ideal to have to do that but worth a try

When I try to save things on support website over HTTPS, the page is HTTPS but it tries to do HTTP POST requests. The error in the browser is:

Mixed Content: The page at 'https://support.universalmediaserver.com/books/use/draft/7' was loaded over HTTPS, but requested an insecure resource 'http://support.universalmediaserver.com/ajax/page/7/save-draft'. This request has been blocked; the content must be served over HTTPS.

I'm guessing there is some config at some level that needs to be changed to make HTTPS always happen

Should do a burger menu like the rest of the site

There are no real network requests so no need to have a preloader

All icons use SVG except the Docker one, and that means its colors don't change properly

I haven't had much of a look at the JavaScript functionality in the template but it is possible that some optimizations can be made. I noticed a lot of binding to load and scroll events, which can cause a lot of client-side load, so they could be debounced.
Another thing to look into would be caching elements in jQuery instead of fetching them on each event.
Other things will present themselves when going through that file

Ideally we could use something like dependabot, I guess. Open to suggestions.

We are a few versions behind

e.g. jQuery

One of our old pages was a comparison between popular media servers and it would be good to update that, including the information in it, and maybe add some more servers to the list, and new features
The old one is still up but not linked to from the new site https://www.universalmediaserver.com/comparison/

At the moment when we update PHPBB we need to manually diff our style with their official one so that we get their style updates while retaining our customizations. Switching to a parent/child style setup would make that easier.

website and svn

If I try to invite a user or I use the "forgot password" part of login, I get an error page and no email is sent

The links should have a padding and the hover state should match that padding. Right now it is possible to hover over and change the colour, but it's still not clickable

We started out using a free template and it had a lot of extra code that is unused, so that should all be removed to improve initial load time

The content of the About page is mostly just what was on the old one, and the layout could use revision as well to fit better with the new design.

This includes having optimal compression and resolution - some of the images may be larger than they need to be

This is one for me, to set up continuous deployment to my server