![\"archived-post-status-dropdown\"](\"https://i2.wp.com/shawfactor.com/wp-content/uploads/sites/60/2015/02/archived-post-status-dropdown.png?ssl=1\")
In 2018 the tradition of “Social touch Football in Melbourne’s heart” continues with PPT’s Winter season.
\nIf you are interested in entering a team please visit the website, where you can find more information and the team entry process.
Ryan Barrett does Bridgy support expanding the url shared to facebook.
\nLike so: https://www.facebook.com/princesparktouch/posts/1261989440544676
\nIve been using briidgy but th url stay in plain format like this:
\nI am a member of the advanced WordPress facebook group and its seems every few days someone posts and article on there waxing lyrical about the latest javacsript only theme they have built using the latest JavaScript framework and the rest api.
\nDont get me wrong, I love javscript, and I think the rest api is one of the best things to happen to WordPress but every time I read about someone usea front end framework to build a theme I shake my head.
\nA wise man once said,
\n\njust because you can doesn’t mean you should
This applies to so many things, especially JavaScript when used to output content.\u00a0 In order to explain we all need to be reminded of the way the web is traditionally designed namely:
\nThis combination might seem old hat but it was created by smart people with good reasons.
\nWhen done properly it has three major strengths
\nHowever it can be slow so today many advocate using JavaScript to interract with apis to replace this traditional paradigm. This has\u00a0 major advantage in that can be substantially faster as the client side javascript can request only the information that it needs. However it also means that javascript is now the creating the content as well as the providing the functionality
\nHowever lets just compare how this compares to the traditional approach. Namely:
\nConveying meaning.\u00a0 Yes javascript can convey an experience that may be indistunguishable to the eye BUT the web is not just a visual medium for humans. Machine like search engines, and screen readers are important and in most cases a javascript front end is invisible to these agents
\nBeing robust. Javascript is a not a fully standardized lanaguage and is notorious for conflicts and errors, and being browser depe3ndent. So an error on a javascript front end usually means the whole site falls over. In contrast a traditional semantic html front end degrades gracefully
\nSeparating concerns. In a JavaScript front end you are tightly coupling functionality with content and potentially presentation as well. This actually if you change the api or you change your javascript the whole thing falls over. In contrast html is html and if the JavaScript stops working you still have the html.
\nJavascript is important but its not a replacement for html. Its future is in rproviing functionality, both in enhancing the reading experience and in making the eually important area of creating, updating and deleting content on the web.
\nFinally I’d like to urge you that is you need speed work on the basics like http caching, or look to modern technologies like http/2 and service workers.
\n", "date_published": "2017-04-01T14:10:35+00:00", "date_modified": "2017-04-05T16:36:12+00:00", "author": { "name": "Peter Shaw" } }, { "id": "https://shawfactor.com/2017/03/07/test-item/", "url": "https://shawfactor.com/2017/03/07/test-item/", "title": "test item", "content_html": "hopefully this works
\n", "date_published": "2017-03-07T01:28:01+00:00", "date_modified": "2017-03-08T01:28:54+00:00", "author": { "name": "Peter Shaw" } }, { "id": "https://shawfactor.com/2015/02/13/introducing-lh-archived-post-status/", "url": "https://shawfactor.com/2015/02/13/introducing-lh-archived-post-status/", "title": "Introducing LH Archived Post Status", "content_html": "LH Archived Post status is a WordPress extension that creates an additional posts status available for content that may no longer be relevant to most visitors but should be available publicly (perhaps for historical purposes).
\nI built this plugin as UI needed this flexibility whilst using WordPress as a CMS. The plugin adds a new post status that enables posts and pages (and custom post types) to be archived. Archiving in this context means that the content is still publicly available but is not published on the front page of the site or the feed. I was not satisfied with other archiving solutions which hid the content for all non logged in visitors and was not configurable.
\n\n
Posts are available directly for any visitor but can have a custom message added that flags that they may no longer be relevant.
\nWordPress\u2019 default post statuses currently work very much like an on/off switch as far as a finished post is concerned. Of the eight default statuses, Published is the only one that is public, while all the rest remain behind the curtain in various states of unreadiness. None of the statuses, apart from Published, adequately indicate that a post is complete or finished or its relevancy.
\nFortunately, WordPress makes it possible for developers to register their own custom post statuses, which is what I’ve done with this plugin. It allows you to archive posts in the same way that you might archive email.
\nArchived Post Status is compatible with posts, pages, and custom post types, giving you a wide array of possible use cases:
\nWhile custom post types seem to be one of the most likely uses for this plugin, you may not want to have the archived status available to all post types. Thisd can be done by slecting the appropriate posts types in the settings area.
\n![\"archived-posts-list-screen\"](\"http://i2.wp.com/wptavern.com/wp-content/uploads/2015/01/archived-posts-list-screen.png\")
If you need to public archive completed posts, but hide them from the front page, feeds, and flag their state this simple plugin will do the trick. Installation instructions etc are available here:
\nhttp://lhero.org/plugins/lh-archived-post-status/