During initial design, I think my thought process was that blog posts don't need a way to be hidden, simply extend the publish date until you want them to be unhidden. In practice while transferring the old database, I'm realizing that might not be practical. There may be times where a draft simply never gets published, but we may want to keep it for archival purposes. The proper solution to this is likely a tag system. This allows multi-level visibility, e.g. "Admin-Only" tagged articles and "Member-Only" articles. This would also allow us to have internal documents directly on the website.
For now, old hidden blog posts have had their publish date set 100 years from now, but we should change that if/when a hidden system is introduced.
During initial design, I think my thought process was that blog posts don't need a way to be hidden, simply extend the publish date until you want them to be unhidden. In practice while transferring the old database, I'm realizing that might not be practical. There may be times where a draft simply never gets published, but we may want to keep it for archival purposes. The proper solution to this is likely a tag system. This allows multi-level visibility, e.g. "Admin-Only" tagged articles and "Member-Only" articles. This would also allow us to have internal documents directly on the website.
For now, old hidden blog posts have had their publish date set 100 years from now, but we should change that if/when a hidden system is introduced.