Web Accessibility is about ensuring that everyone will be able to understand your site quickly and easily — and that includes people with visual and cognitive impairments. It is a humane endeavor that you should undertake, not to mention the fact that you will risk legal liabilities if you don’t.
We look at a recent client implementation for showing their office locations nearest to a website visitor. We cover topics such as location tracking and integrating with APIs that return JSON data.
We articulate some devops best practices around managing and upgrading an enterprise website on an ongoing basis. We are focused more on what it takes to add new features rather than aspects such as managing performance, security or uptime. Also, for purposes of simplicity, we will illustrate these concepts on a WordPress setup that runs on the WPEngine hosting platform. You will find that these can be extrapolated quite naturally to other CMS and hosting environments as well.
Many websites have dynamic data entities (offices, employees, experts) that need to be location-aware. When a user in a certain physical location comes to the site we need to show only the data is closest to them (the closest office, the nearest employee, experts within a 25-mile radius). We discuss generic approaches to accomplish this.
We consider a typical setup where ads on Google, Facebook and Linkedin drive traffic to a landing page. This page has a lead acquisition form that is powered by Hubspot. The overall site uses Google Analytics and Google Tag Manager. In this setup, we consider different ways to hook up the tooling to track ad performance.
Sometimes a client will want to do a “lift-shift” project. This usually happens when they decide to move from CMS to another. In such projects, the look-feel of the site will remain exactly the same but the entire underlying tech infrastructure is swapped out completely. In this post, we will explore how to do this in the quickest, least intrusive and most effective manner.
In an earlier post, we had introduced component-based front-end design for websites. We discussed how essential it is, to ensure coherence, consistency and productivity when building large websites. In this post, we discuss component-based design approaches in Drupal.
We introduce the three pillars of site personalization : Site components, Incoming state of a visitor and Behavior in the active session. We then formulate a usecase to illustrate these ideas and implement them in multiple CMS platforms such as WordPress, Drupal, AEM, Kentico and others.
We explore three big trends: Headless CMS, Reactive Frameworks and Component-Based Design. We build the page in Gatsby, the component in React and do content modeling in Prismic.
With so many choices, how do you select the right CMS? We identify three criteria.
We discuss essential steps while relaunching a website to ensure that SEO is not impacted adversely.
We discuss a useful tool – Query Monitor – that helps with debugging slow WordPress database queries. Why Query Optimization? WordPress is usually very efficient at executing its internal database queries. So generally speaking, you shouldn’t have to work on optimizing them. Most of the time when a page is slow, the culprits lie elsewhere.
Images comprise 70% of an average page size. Optimizing them for mobile, tablet and desktop can have a significant impact on site performance. We discuss ways to do this.
We compare the DevOps features of two WordPress hosting products: SiteGround and WPEngine.