#who run blogs for whom text posts are anathema

[a-dream-seeking-light]

Please do not get rid of the legacy editor until the new editor has been ironed out to be as bug free as possible AND when it delivers a UX that is comparable to the legacy editor. Near as I can tell the new editor is still yet far from there.

As for NPF. I get that you wanted to simplify things down from 7 types, but making all posts 1 type that is treated as text by all things ain’t it. Doing so undercuts the value of the media content that is so essential to the users of the site.

So here’s a compromise suggestion. Instead of smooshing all post into a base text type, could it not have been enough to simplify down to two types: a) text-based type and b) media-based type? This way you have a streamlined content system that leaves media unadulterated while still allowing for versatility and future-proofing for new post types AND it preserves the media content for even better backwards compatibility, especially for older themes. I’d prefer a bug where videos show up as photos than one where they show up as text.

Right now the workarounds I’m seeing to make themes compatible with both legacy and npf is a mess because all posts are being treated as the same type with makeshift solutions to try to suss out the OP’s intended “primary” post type. One buggy example was (is?) npf posts showing up as video because like 5 blocks down a text post a video block was included.

So because text and media I feel are inherently different categories, this is how I’d break them down:

text/non-media types: text, quote, chat, link, poll, contact, coding snippet, dna sequence, menu, recipe, survey, form, screenplay, 3d printable object, asks, etc.

media types: photo (incl. anim gif), photoset (incl. anim gifset), video, audio, rendered 3d object / vr object, video game / interactive environment, live feed, embedded external versions of video and audio and game, rendered smells and tastes and haptic feedback / vr spaces, ai avatars, tele-limb controls, zoom meetings, dreams, memories, etc.

you can still have mixed block types but with this you would have a choice of whether you want a post to have text primacy or media primacy.

Unfortunately I’m probably just screaming into the wind here. When none of the user feedback is heeded and npf goes forward as is, when the legacy post editor finally dies this blog will become a wraith account, a ghost of tumblr’s past, trawling through old archives to find lost gems, but unable to partake in the land of the living.

I’ve had this inevitability in mind for a long time now, even starting an equivalent npf blog @pszombie a while back anticipating this happening.

I sometimes tag stuff as ephemeral, but I guess that’s pretty redundant since in the end that applies to everything.

Hello, Tumblr. 

If you joined us before November 2022 and predominantly post on web, you will be familiar with the two post editors—the legacy editor and the “new” web editor (formerly known as the “Beta editor”).

Beginning May 15, we’ll gradually be working to remove the legacy editor as an option for creating new posts. New posts created on web will be created in the new web editor. We hope to complete this change by July 15. 

This change only affects accounts created before November 2022. Newer accounts already default to the new web editor.

This will not affect posting on the apps because we switched to this new editor on the apps about four years ago. If you use the apps, you’ve been using the new editor all this time!

This will not affect what you can include in a post, only how you get there: You can still include all the different types of media in a post, only now, you’ll do that via the new web editor’s content blocks instead of selecting a post type from the post type bar at the top of your dash. So, if you’re halfway through a text post, and you decide that what this post really needs is your pet reptile, then click on the little red image icon in the post editor, select an image, and voilà. Lizard boy steals our hearts.

If you still prefer to post on web using the legacy editor, please keep reading because the rest of this post is for you.

How can you prepare for this change?

Once we have completed this update, you won’t be able to create posts using the legacy editor. You will be able to edit posts made using the legacy editor, at least for now. 

Start using the new web editor ahead of the switch. This will help you help us troubleshoot any issues you might encounter. It’ll also mean you’ll already know the ropes before the switch is final. 

Talk to us. Send us feedback. Especially if you’re switching from legacy to the new web editor. We want to hear about your experience: Are there any specific workflows or features in legacy that you want to see in the new editor?      

If you use a theme, make sure to check whether it supports posts made using the new web editor, and update it if that’s not the case. 

For those of you trimming reblogs: @rpschtuff has created an incredibly detailed master post that gets into the nitty gritty of that practice in the new web editor.

XKitters: XKit Rewritten was explicitly designed with the new web experience in mind. This means that you will need to use XKit Rewritten when creating posts in the new web editor.

That’s all for now. Remember, you can always get in touch with us. If it’s regarding the new web editor, then Support is the place for you. If it’s about something else, @wip is your guy.