Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Different kinds of posts in the /blog feed: discussion #1032

Open
amandavisconti opened this issue Aug 9, 2024 · 0 comments
Open

Different kinds of posts in the /blog feed: discussion #1032

amandavisconti opened this issue Aug 9, 2024 · 0 comments
Assignees
Labels

Comments

@amandavisconti
Copy link
Collaborator

Ties into #1021 re:the 3 new blog categories, their names, and how we use them

Option #1
"Scholarship">"Research Blog" (links to /research-blog, which only contains research posts)
"News/Events">"News Blog" (links to longstanding /blog URL, which contains all post types)
Pro: way to read only our essay-style posts of enduring interest (use for external audience, and vs. having to skim past stale announcement posts); con: confusing duplication of some posts?

Option #2
"Scholarship">"Blog" (links to /blog, edited to only contain research posts)
"News/Events">"News" (links to /news, which only contains "announcement" posts)
Pro: clear what each page does, can just view the post type you need. Con: people may not notice they need to go to the new /news page to see announcements.

Option #3 = current status on /realignment
Only have "Scholarship">"Blog" (links to existing /blog, which contains all post types)
No "News/Events">"News" in main nav dropdown (bc. "News/Events" only has 1 sub-item: "Newsletter")
Rename "News/Events" to "Events" (given there's no newsletter page at near launch time)
Pro: streamlined, no one misses any posts. Cons: mixes in posts that become non-read as time passes (e.g. old workshop announcements); leaves Menu Item #6 (News/Events) with only one sub-item of uncertain necessity (newsletter signup is on front page, could also be in footer; doesn't necessarily need a nav item?)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Require discussion
Development

No branches or pull requests

2 participants