Owner tumblr app pocket casts12/13/2023 ![]() ![]() Want to share your feedback about something? Check out our Work in Progress blog and start a discussion with the community. This would move the tab configuration from Tumblr Labs to this new config view, and also allow reordering the dashboard tabs.Įxperiencing an issue? File a Support Request and we’ll get back to you as soon as we can! We’re currently experimenting with a new Dashboard Tab configuration button in the tab bar in the iOS and Android apps, as well as at the top of the dashboard feed on web.Fixed a bug in the post editor on web which could cause the autosave drafts feature to try to save to the wrong blog, if you switch blogs when writing the post.Fixed a bug in the post editor on web that would prevent files from uploading if they were too close to the file size limit, even though they weren’t technically over our limits.We fixed a bug with our blog recommendation engine that was causing the same blogs to be recommended even though you had been seeing them over and over again for awhile.On web, when using Tumblr via a mobile phone browser, the “Change Palette” button in the navigation drawer is now located in the Settings submenu.You’ll find a “Mark as spam” button in the meatballs menu on the messaging window, which never disappears. On web, it’s now always possible to report conversations as spam (even after you’ve replied).On web we're now showing one decimal place of precision in poll results.We’ve removed the “Let people find your blogs through this address” account setting and the ability to be followed via your account email address on the Following page (if you had that setting enabled, which it was by default).The third party flexible content plugins are just as nice to use because Craft gets field design, selection and re-arrangement right at the system level, so plugin developers don’t feel the need to re-implement admin UI. A few of the third party editors also have better workflows (not many, though.)Ĭraft CMS (no relation to the Craft notes app) has my favorite implementation of flexible content with its Matrix fields and the way it integrates Twig templating. Measured by developer happiness, ACF Pro has better field definition and templating implementation than Gutenberg. The classic editor holds back a lot of sites. Gutenberg’s attempt to make block boundaries appear invisible isn’t a bad approach to this in theory, but in practice, experienced authors and editors would rather see more explicit borders between blocks. The challenge from note-taking of when to interrupt a block with a different type of block (pull quotes, forms, etc.) remains, but if authors accept that varying elements let the page look nicer and perform better, and understand that the blocks’ fields give them good layout for free, they’re usually happy to break up an article. It’s most appropriate for page- or guide-type content and one set of fields that repeats once in its template, and is reused elsewhere in the site, is better for entering almost everything else. In CMSes, block editors are a really useful way to put content in a flexible structure that is pixel-perfect on the front end without requiring authors to worry about HTML or about going back and fixing old pages when the design is tweaked. Hence, other plugins are now available that duplicate that functionality as I think people don’t trust Automattic’s determination of “as long as necessary”. The intent is clearly to force people to use Gutenberg. Disabling it requires a plugin, albeit a plugin provided by Automattic themselves, which is described:Ĭlassic Editor is an official WordPress plugin, and will be fully supported and maintained until at least 2022, or as long as is necessary. Gutenberg wasn’t rolled out as an option within core, it was rolled out as the editor within core. The problem with Gutenberg is that I don’t think it actually even comes close to approaching the functionality of the other available tools.Īnd honestly, there’s a pretty vocal contingent in the WordPress open source community that are user-hostile if those users aren’t on the “progress” train. Kind of like when Apple “sherlocks” things and builds them into the OS. I think the underlying reason was to do what the other editors do, but built-in. I’m not sure what the rationale was given there were already a bunch of block editors available for WP for those who wanted them… their version didn’t add anything to the party.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |