In-depth insights on content, code, and creativity
As developers of websites where content is key, one of the questions we are frequently asked by our clients is "how do we ensure our content ranks well in search?" It's a common concern for digital content creators, whether they're launching a new site or refreshing an existing one.
If you're publishing content online, one of your key considerations should be search engine optimization. In other words, you need to do what you can to make sure that people can find your content when they Google it.
Making your website accessible to people with disabilities - whether you’re launching a brand new site, or remediating an existing one - may seem complex when you consider all the components that require attention (in-page navigation, links, colour contrast, forms, and alt tags, among other things). But the right CMS can make the job a lot easier.
For one of our high-traffic clients, we switched the Content Delivery Network (CDN) from Akamai to Amazon CloudFront. This blog post looks at why we decided to change the CDN and describes the switching process. Plus we share some useful tips about how to configure CloudFront.
A key component of an accessible website, accessible in-page navigation provides a way for website visitors to jump straight into the main content on your site and access different sections of the page quickly, without having to tab through every link to get there.
In our case study FindaTopDoc Prescribes eZ Publish for Healthy Content Management, we briefly covered our integration of PlagScan into the editorial approval workflow. When writing about medical topics, content -- especially medical term definitions -- can end up being duplicated on other sites, even if it was not purposely copied. Therefore, it is important for SEO reasons to ensure that all content on the FindaTopDoc site is as unique as possible. Here we'll take a closer look at how the plagiarism scanner integration works.
Before you embark on a project to make your website accessible to people with disabilities, it’s critical to understand what such a large and varied audience really looks like -- and what they need from your site.
Last year, I switched from developing on a dual-boot Windows and Linux machine to working on a Mac. During the transition, I felt my productivity slump: not only was I missing keyboard shortcuts that I had become very accustomed to (such as Alt+←, for instance), but some native MacOS behaviour drove me crazy (like ⌘+Tab cycling through applications rather than cycling through windows of all applications). I also found the Mac terminal to be lacking, missing important utilities, and running some outdated binaries. So, vowing to prove decisively the superiority of humans over machines, I decided to make my Mac Just Work* ™ * Like my PC used to.