> One note: you might want to put 'download' in the link to the PDF, so it downloads instead of showing up in a new browser window

I strongly disagree with this suggestion. My browser is my PDF viewer, if I want to actually download the PDF I can do it after the browser renders it.

There are precious few situations where <a download> is appropriate for PDF files. This is certainly not one of them. The user probably wants to view the content, let them handle it however.

The experience of PDFs that insist on triggering a download is sufficiently unpleasant that I use a browser extension <https://addons.mozilla.org/en-GB/firefox/addon/no-pdf-downlo...> that removes any `Content-Disposition: attachment` headers, and inserts `Content-Disposition: inline` headers, which in Firefox (but not Chrome, I believe) overrides even an <a download> attribute.

As the button says 'Download', I expect that result - a download. 'View PDF' would be the appropriate button name in your case... He can put two buttons that distinctly describe the resulting actions.

It’s one of the main reasons I use Notion.so and its extremely flexible “database” pages, I can quickly drop links into them, and expand as-needed with more details.

I use git repos for anything that gets far enough to warrant a folder with files, but only because I tend to swap computers too often to reliably maintain a fixed file directory, but along the way I found that “plain git + files” is a surprisingly effective foundation for a project/knowledge management system.

You mentioned the folder, now please share it! I enjoy these ideas very much.

Nope! Way too big to be shared, and no organization at all. It's embarrassing to show people my messy room!