For text posts, it’s just text, in HTML format. For video posts, this is either a reference to an uploaded video file, or it’s a URL to an external video. For photo posts, this is a set of one or more images. But once you have these discrete “types”, you have to determine how you want to store the content of each “type”. Post content (more on this in a minute)īefore the Neue Post Format, posts had discrete “types”, so that’d be a column here as well.When it was posted (a timestamp of some kind).Parent blog identifier (if it’s a reblog).Parent post identifier (if it’s a reblog).Author blog identifier (an integer pointing to the “blogs” database table).In a standard normalized database table, these columns would look like: In the case of reblogs, they also have the “parent” post and blog it was reblogged from (more on How Reblogs Work over here). Every post has a unique identifier once it’s created. This hellsite we all love is held together by duct tape, good intentions, and luck, and we’re constantly working to make it better!Ī post is seemingly a very simple data model: it has an author, it has content, and it was posted at a certain time. To understand how far we’ve come and the challenges we’ve had to face, you need to know the deep dark secrets of how we store post content on Tumblr. With literally billions (tens of billions!) of posts on Tumblr, how do we move this churning engine of content from one format to another without breaking everything? It took many phases, and releasing the new editor on the web will be one of the final pieces in place. But here on Tumblr, we still want to stay true to our blogging roots, while giving access to a wide creative canvas, and the Neue Post Format reflects that work. Over the years, the landscape of how people make posts on different platforms across the internet has changed dramatically. It’s been a very long time coming – work on the Neue Post Format began in 2015 and was originally codenamed “Poster Child”, and it was borne out of a lot of things we learned dealing with the previous new post editor we released on web around that time. We’re sorry this perhaps isn’t a crowd-pleaser, but we hope it explains things, and we hope it helps.We’re currently rolling out an opt-in beta for a new post editor on web which will leverage the Neue Post Format behind the scenes. But we won’t be able to make it work exactly the same as it used to with ‘legacy posts’ in every case. We are doing some work to improve a bit some of the problems of “old” themes when rendering NPF posts. But even if we can update some popular themes to solve the problem there, we won’t be able to update every theme ever. We have been moving away from post types for a while, which is why some old posts (or posts made on the web legacy editor) can’t be edited in the apps. This means themes that haven’t been updated to work with these types may show some issues displaying certain types of posts (because, as you say, the theme considers those posts as ‘text posts’). For them, all the posts are «NPF posts» (AKA., Neue Post Format-regarding which you can find our public docs here and our announcement about this here, which has a note about a theme option for NPF posts) which can have multiple blocks with different content types each. The thing is, the beta editor and the Android and iOS editors don’t work with post types anymore. We will be honest: this might not be everyone’s favorite answer, but it’s the only one we’ve got.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |