check if modeling posts on events vs. past events is useful

[amandavisconti]

starting work in branch develop-1037

pro: more wieldy folder when adding new posts, editing recent posts (typos, tags)
con: requires updating all site.posts pulls to pull from 2 folders (posts & past-posts)

1. preserve same urls for posts that are moved in /_past-posts
2. pull /_past-posts into /blog list
3. pages pulling posts by tag aren't working, currently (stopped work here 8/19/2024)
4. once fix, need to check same logic applied across any file using "allpost"
5. individual posts in past-posts are keeping their same URL, but aren't applying correct post.html layout?
6. make sure feed.xml pulls in both posts & past-posts (use allposts, not site.posts)
7. add allposts instead of site.posts (assign, call) to docs
8. all other "for posts in site.posts" loops need to also be updated to pull from both collections (posts and past-posts). E.g. homepage recent posts, homepage updates, updates.html, bio pages, project pages, static pages, do a search for .posts to find and edit everything

options for new logic:

• site.documents

• site.collections where (posts or past-posts)

• site array, concat