I strongly disapprove of graphically rendering “Frontpage” and “Personal Blog” as if they were tags on post pages. They’re not tags! Conflating “Personal” with topic tags on the home page “Latest” controls wasn’t jarring, but this really is.
My current model here is that we should give them some kind of special styling that distinguishes them from the other tags. They obviously have some overlap with tags (in some sense you can model them as an “admin-only” tag as Ray says below, and I expect that is what we will change the underlying architecture towards at some point in the next few months).
Curious whether you think that would help sufficiently.
I am curious if your opinion changes if we actually change Frontpage and Personal Blog to be literally treated as tags in the architecture?
Over the past two years we’ve made a few one-of boolean fields in the posts database, and each time I thought “man, this should really be handled formally by a tag architecture, but making a tag architecture is a bunch of upfront cost we’re not ready to do yet.” With the recent tag overhaul we’d been talking about migrating Frontpage Status to a tag, but we had already built some infrastructure that handled it as a database-boolean, and hadn’t gotten around to it yet. (But meanwhile we started tweaking the UI to reflect that goal)
Obviously there’d be some important distinction between admin-only tags vs general use tags, and maybe the UI could more explicitly reflect that in some way. Curious if that all still feels wrong to you?
I strongly disapprove of graphically rendering “Frontpage” and “Personal Blog” as if they were tags on post pages. They’re not tags! Conflating “Personal” with topic tags on the home page “Latest” controls wasn’t jarring, but this really is.
My current model here is that we should give them some kind of special styling that distinguishes them from the other tags. They obviously have some overlap with tags (in some sense you can model them as an “admin-only” tag as Ray says below, and I expect that is what we will change the underlying architecture towards at some point in the next few months).
Curious whether you think that would help sufficiently.
Thanks for letting us know!
I am curious if your opinion changes if we actually change Frontpage and Personal Blog to be literally treated as tags in the architecture?
Over the past two years we’ve made a few one-of boolean fields in the posts database, and each time I thought “man, this should really be handled formally by a tag architecture, but making a tag architecture is a bunch of upfront cost we’re not ready to do yet.” With the recent tag overhaul we’d been talking about migrating Frontpage Status to a tag, but we had already built some infrastructure that handled it as a database-boolean, and hadn’t gotten around to it yet. (But meanwhile we started tweaking the UI to reflect that goal)
Obviously there’d be some important distinction between admin-only tags vs general use tags, and maybe the UI could more explicitly reflect that in some way. Curious if that all still feels wrong to you?