On your local machine the OS may be able to resolve the HTML resource names, but on a live server this could lead to problems. If you must have spaces in file names, encode them with %20
.
href="20171203%20The%20Hub%20Latest.html"
Do you really need the date in the name? Can it not just be a folder by that name, and then point to it.
If the site is called, “The Hub”, won’t that be in the domain name and splashed all over the site? Does it have to be in the resource names?
Remember that while your local machine is not case sensitive when it come to file names, live servers are case sensitive. Avoid errors and mis-typed URL’s by simply never using uppercase.
www.example.com/20171203/index.html
www.example.com/index.html
www.example.com/latest.html
www.example.com/people.html
www.example.com/school.html
www.example.com/events.html
www.example.com/misc.html
www.example.com/contact.html
If you listen to the link text in a screen reader it will sound like,
More dot dot dot
More dot dot dot
More dot dot dot
More dot dot dot
HTML has an entity for that character, the horizontal elliplsis, …
.
One might feel at present that it is not too much work going forward, but you may find yourself in a world of hurt when it comes to maintenance a year or two down the road. This is the time to trim all unnecessities and build a rock solid foundation for your site to grow into.
Remember, search engines are following your site and if you make it too hard for them to access resources it will be ages before you get a top ten placement for your domain. Dated material should be easily identifiable, that much is certain, but not as a file name on the root. A directory, a hash or a query string fits much better with the convention of the web.
If the file name is changing daily then nothing will ever get indexed. Your site will live in a vacuum. Let the permanent pages be permanently named, never moved, and always kept up to date. Especially on the root of the site.