August 31, 2017 — Wszyscy wiemy, że WordPress to najpopularniejszy CMS na tej planecie. Podczas prezentacji Aleksandra cofniemy się w czasie i zobaczymy jak doszło do tego, że projekt rozwijany po godzinach przez Matta Mullenwega stał się zjawiskiem na skalę globalną.
February 3, 2017 — The WP REST API infrastructure was introduced in WordPress 4.4. The introduction of this infrastructure allows WordPress developers to now use WordPress as a headless CMS. A headless CMS has its frontend component (the head) stripped and removed from its backend, and what remains is a backend delivering content via an API. Some common use cases for headless CMS are as follows:
* Serving data to other web applications
* Mobile Apps
Developers can install the WP REST API plugin to expose endpoints for WordPress for posts, pages, media and users. Developers can also extend the WordPress core REST infrastructure to register their own endpoints for custom post types and WordPress options.
Bronson will explain and demonstrate how you can use WordPress and the WP REST API to create a website that uses React on the frontend and WordPress on the backend as a headless CMS.
February 2, 2017 — We have recently developed an online marketing collateral portal for a huge franchise business in Australia. Zambrero hired us to build a complete custom build portal which would generate pdfs for franchisee’s.
The marketing team would create their own marketing material in this portal which is completely code free…
The power of WordPress in conjunction with gravitypdf and gravity forms has made this all possible…
We have built many websites which have broken the conventional use of WordPress and made our clients very happy with the end result and we want to show people to think outside the box when it comes to WordPress and what it actually can do.
December 10, 2016 — As many museums move towards diverse open data policies, one would assume their choice of CMS would follow suit. One would be WRONG.
In this talk I will begin by reviewing the current state of technology in museums, with a focus on their usage of open source Content Management Systems (where Drupal reigns supreme and WordPress is only for blogging). I will discuss why the perceived lack of os software competition in this sector keeps museums trapped in systems they cannot afford to update. I will end by sharing ways the OS community can get involved in the would of Cultural Institutions.
November 6, 2016 — David Jardin erklärt in seinem Vortrag, warum sich ein Blick über die Grenzen des eigenen CMS lohnt.
October 8, 2016 — There’s an old saying that when all you have is a hammer, everything looks like a nail. You can build almost anything with WordPress, but should you? If you build a single landing page or a 5-page brochure site in WordPress, you may be burdening your client with the cost and effort of constant maintenance of a site they might update once in a year. But if you don’t use a CMS when you need one, managing that site is going to be a nightmare for the client. Here’s how to explain to clients what a content management system is, how to tell whether they need one, where to go if they don’t, and why WordPress is worth the higher cost of hosting, the ongoing maintenance, and the time it takes to learn how to use it in the first place.
October 7, 2016 — WordPress、Joomla、Drupal、MovableType というCMS四天王（命名はオレ）で構築したサイトを攻撃してみましょう。本体の脆弱性あり、プラグインの脆弱性あり…。セキュリティ業界では評判の芳しくないWordPressですが、果たして四天王の中で ”最弱” なのでしょうか。その上で、WordPressによって構築したサイトの防御法の基本をたっぷりと解説します。
August 2, 2016 — This one’s for everybody! In this talk, we’ll cover the organizational and technical benefits of running a multi-network, multi-site WordPress as the primary CMS at Boston University. We’ll highlight specific strategies, including organizational policies, development workflows, and team structure that allow us to serve over a million users per month. We’re here to help dispel the notion that a centralized approach to WordPress can’t successfully be implemented in Higher Ed.
July 1, 2016 — Face it, a lot of great content is trapped in pages and an amorphous post content field. Looking at an example project we’ll see how a clean content structure can simplify content management and get your site prepared for future changes. It will make your client happy now as well as for years after the launch.