{"id":61,"date":"2020-06-14T08:24:25","date_gmt":"2020-06-14T07:24:25","guid":{"rendered":"https:\/\/amasan.co.uk\/vandragt\/?p=61"},"modified":"2020-06-14T08:53:44","modified_gmt":"2020-06-14T07:53:44","slug":"time-to-wake-up","status":"publish","type":"post","link":"https:\/\/2022.vandragt.com\/technology\/time-to-wake-up\/","title":{"rendered":"Time to wake up!"},"content":{"rendered":"\n<p>Enjoy the WordPress fun while it lasts folks, I\u2019ve seen the light, and I am worried.<\/p>\n\n\n\n<p>Automattic and the community are spending millions and millions on building a <a href=\"https:\/\/github.com\/WordPress\/gutenberg\/issues\">more useful but buggy JS editing interface for the web<\/a> to make publishing rich documents passable. It can\u2019t get a close button aligned on a modal, or scroll correctly in a mobile device. Basically, Gutenberg is a lesser version of Word 97. It\u2019s not their fault, the browser stack is a brittle way to build apps. We&#8217;ve collectively stretched web technologies past what they&#8217;re best used for &#8211; there are no JavaScript native widgets that can compete with what the OS offers itself. It turns out the web excels to read documents, not write them. I know how it sounds, I&#8217;m writing this in the same editor! But we\u2019re on the wrong path:<\/p>\n\n\n\n<p>Because, while everyone is looking to the left at SquareSpace and Wix, trying to figure out how to improve the publishing workflow, on the right <strong><a href=\"https:\/\/alejandrocrosa.com\/\">Alejandro Crosa<\/a><\/strong>  builds <a href=\"https:\/\/collectednotes.com\/\">an iOS app that publishes notes<\/a> online by simply saving them. It abstracts the whole publishing process. Similarly to how Dropbox abstracted the filesharing site, a native app removes the web editor. <em>In. Three. Weeks.<\/em> Using <a href=\"https:\/\/alejandrocrosa.com\/collected-notes-tech-stack\">Rails and Swift<\/a>!<\/p>\n\n\n\n<p>In 3 weeks he did a (subjectively) better job for this use case than the WP app and the WB mobile experience. Just look at it <a href=\"https:\/\/collectednotes.com\">collectednotes.com<\/a> and <a href=\"https:\/\/collectednotes.com\/blog\">it&#8217;s blog<\/a> \u2014 the latter which is written using the service itself!). Yes it does less, but it&#8217;s about the job to be done. Gutenberg does less than Word 97 and Dreamweaver. The point is, that&#8217;s fine.<\/p>\n\n\n\n<p>WP is currently deciding <a href=\"https:\/\/wptavern.com\/should-wordpress-provide-an-api-for-third-party-editors\">whether the REST API should be open to third party editors<\/a>. It&#8217;s mission is to democratise publishing, but somehow this is up for discussion. However it turns out the best experience is a native one. Should WP forego the admin interface, change Gutenberg&#8217;s full site editing into the theme editor, and restructure itself for what&#8217;s to come? WP has a lot of moving parts, and consensus isn\u2019t easily reached. It seems to me that the web will experience will refocus on reading documents, with content creation in apps. <\/p>\n\n\n\n<p>If Apple ever adds a backend service to Pages to sync with a static site generator, or someone goes 10% further <a href=\"https:\/\/ia.net\/writer\/blog\/new-pdf-preview-better-web-publishing-improved-editing\">than iA Writer\u2019s web-publishing feature<\/a> in a \u2018writing app\u2019 than the whole WP ecosystem is sherlocked.<\/p>\n\n\n\n<p>It\u2019s time to wake up. <\/p>\n<div class=\"syndication-links\"><\/div>","protected":false},"excerpt":{"rendered":"<p>Enjoy the WordPress fun while it lasts folks, I\u2019ve seen the light, and I am worried. Automattic and the community are spending millions and millions on building a more useful but buggy JS editing interface for the web to make publishing rich documents passable. It can\u2019t get a close button aligned on a modal, or [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"mf2_syndication":[],"webmentions_disabled_pings":false,"webmentions_disabled":false,"footnotes":""},"categories":[11],"tags":[13,14,15,12],"class_list":["post-61","post","type-post","status-publish","format-standard","hentry","category-technology","tag-gutenberg","tag-rails","tag-swift","tag-wordpress"],"_links":{"self":[{"href":"https:\/\/amasan.co.uk\/vandragt\/wp-json\/wp\/v2\/posts\/61","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/amasan.co.uk\/vandragt\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/amasan.co.uk\/vandragt\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/amasan.co.uk\/vandragt\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/amasan.co.uk\/vandragt\/wp-json\/wp\/v2\/comments?post=61"}],"version-history":[{"count":11,"href":"https:\/\/amasan.co.uk\/vandragt\/wp-json\/wp\/v2\/posts\/61\/revisions"}],"predecessor-version":[{"id":72,"href":"https:\/\/amasan.co.uk\/vandragt\/wp-json\/wp\/v2\/posts\/61\/revisions\/72"}],"wp:attachment":[{"href":"https:\/\/amasan.co.uk\/vandragt\/wp-json\/wp\/v2\/media?parent=61"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/amasan.co.uk\/vandragt\/wp-json\/wp\/v2\/categories?post=61"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/amasan.co.uk\/vandragt\/wp-json\/wp\/v2\/tags?post=61"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}