Remote Developers who support clients using WordPress must consider some very simple rules. Our hosted services support observation of these rules so that end clients, editors, authors and contributors have the simplest and richest, most secure and successful experience of using a great product which has become the industry standard in the publishing industry.
The lastest version of WordPress features also a new Gallery. Out of the box.
ArrivingMidday sun on waterRhodesRhodes Rhodes portVisiting cruiseliner
Or upload a plugin to render a slideshow.
Arriving
Midday sun on water
Rhodes
Rhodes port
The second rule is: avoid multisite unless you fit what it is designed for. It appears ideal for instances where the incorporation of multiple brands marketed to a common user list who may be members of one or more of these brands. It is often used in this manner. But does a massively expanding list of users in one place not expose the organization to more risk? It is an important consideration as it requires continuous management to get it right. In other words, there are pros and cons.
An embedded Jetpack image used as a feature background is easy and intuitive for end users.
The first rule is quite simple: keep WordPress up to date. Why? Why not! It is a nearly 100% safe method to protect your site from gaping holes in security that may have existed in earlier version, to avoid being tripped up by not being GDPR compliant, and to receive the latest features. The latest update incorporates a vastly superior editing experience.
An excellent reason for multisite is multiple publications with the same set of users as authors. They can login once, and choose which publication they are working on, and follow the same rules. If you want to lockdown plugins developers can use, then multisite enables this behaviour.
An obvious con is that if you sell one of the brands you have to remove exclusive users of that brand from your database. Why would anyone do that? Because of GDPR. The value of a huge mailing list may make this counter-intuitive.
An appropriate application is when an academic institute hosts multiple doctorate students preparing individual content, with shared templates – when it is supported by a single person it is easier if you have one backend system instead of many.
For Remote Developers who support WordPress, it pays to spend more time planning the way the site will work, our developers can use a recommended list of plugins and themes we know work.
If you host your WordPress clients or projects with Remote Development we help you move your starter site to a cloud for better performance and provide scaling opportunities, but simple things like updates can be automated. We can advise on a list of plugins, automate updates, provide backups, basically provide you with a set of tools we know work.
WordPress has become a powerful solution to publishing. A Remote Developer for WordPress clients can use our infrastructure for hosting development projects, staging servers, as well as resell our client dedicated cloud solutions, which are scalable. Join our team today.
Logo
Landscape (4:1): 1200×300 (min required: 512×128)
Square: 1200×1200 (min required: 128×128)
Note: Adding only a landscape logo can limit your reach and isn't recommended.
We are adopting a new framework in addition to VueJS and Angular to our frontend app development framework. It is brilliantly engineered using modular javascript and promises to have a UX module to create native mobile aps, in the meantime, Cordova can be used for that. We are in the business of creating web applications for business and it promises to be faster, cleaner and better designed than others.
Aurelia uses ES2015 or Typescript. It can work with Babel or Webpack. Most impressive is that it hides itself behind your ap in such a way that you feel like you are writing modular JS and HTML with a few directives to relate its parts. And it works magically. The now traditional todo ap requires just three files:
todo.js
app.js
app.html
app.js
import {Todo} from './todo.js';
export class App {
constructor() {
this.heading = 'Todo';
this.todos = [];
this.todoDescription = '';
}
addTodo() {
if (this.todoDescription) {
this.todos.push(new Todo(this.todoDescription));
this.todoDescription = '';
}
}
removeTodo(todo) {
let index = this.todos.indexOf(todo);
if (index !== -1) {
this.todos.splice(index, 1);
}
}
}
todo.js
export class Todo {
constructor(description) {
this.description = description;
this.done = false;
}
}
This site is based on a CMS, WordPress. It is not particularly “state of the art” as such. We can take this in one of these two directions:
1. Make a parallax scrolling view (where a background scrolls at a different rate to the foreground) by changing the CSS to render the pages of this site.
2. Create an SPA that uses the content of the CMS site and maintain the CMS as /cms.
The first is relatively easy. But what does it achieve? Nothing much, apart from how the site appears. There are some people who decry parallax views as pointless. I am not sure that I find it a compelling design choice. It is a bit like fins on a car – looks nice, but aerodynamics may be better served by their absence. Depends on the car, depends on the taste of the driver. So I think I will forget that (the theme does it anyway on the home page).
Creating an SPA using VueJS or or Angular Aurelia requires more parts. It is a challenge. What are these parts?
1. Front end design
2. Front end components
3. wp api calls to populate components
4. keep the CMS working to create content.
Each hosting environment has its own software stack and yet the test environment must match the live environment to be an actual test.
The important issue is not if you can maintain a working version so much as build one. Because if you cannot recreate a working environment in seconds, if not minutes, then you are vulnerable to downtime.
