Upgrade Your Drupal Skills

We trained 1,000+ Drupal Developers over the last decade.

See Advanced Courses NAH, I know Enough
Oct 22 2020
Oct 22

The impact of this years’ shelter-in-place orders and social distancing guidelines, along with every aspect of how we have coped -- or not coped -- with Covid-19 will be analyzed for years to come. Big changes have emerged in the ways that we interact with the world, and the next normal will likely bring with it many differences in the ways that we live, work, and play.  

From a web accessibility perspective, the pandemic is likely to usher in widespread changes. Now that online interactions are the primary means by which all of us are interacting with the world, we tend to be expecting more with a general understanding that the internet needs to be accessible to everyone, as well as compliant with ADA Accessibility guidelines.
 

Web Accessibility Advances

People of every age and with a wide range of disabilities are now working online, learning online, shopping online, connecting to medical care online, socializing online, and a lot more. We have replaced in-person events with virtual conferences, Zoom meetings and remote learning. Many medical facilities are asking patients to go online for information or even complete online visits. So how are we doing in ensuring that online activities are thoroughly accessible to people with disabilities, at a time when fighting isolation and stress can be a huge uphill battle? 

According to the US Department of Labor, in 2019 19.3 percent of individuals with a disability in the United States are employed. Many of these same individuals now need to work remotely, which is serving to shine a spotlight on the kinds of tools and resources that they need. Here are some of the challenges they are facing:

  • Documents and correspondence are often emailed without consideration given to color contrast ratios, fonts, and text size that would make them accessible to people with low vision. 

  • PDFs are being sent that are not created in an accessible manner, causing challenges for screen reader users. 

  • Video recordings of recent meetings or conferences are often sent without captions or a transcript, added. For someone who is deaf or hearing impaired, these videos can be hard to understand without a transcript or close captioning, especially in circumstances where they can not lip read.

                    Free webinar next week!  Web Design for Accessibility  October 27, 2020 11 a.m. Central  

What's Needed Now

In addition to new ways of working, so many basic services have shifted online. Everything from ordering groceries to seeking medical care has gone virtual. How much attention is being paid to the accessibility of these services? 

  • Complex layouts need to be simplified to make navigation accessible for individuals with cognitive disabilities.
  • Animations and videos on sites need to have a pause option built in to reduce seizure risks, and in some cases, avoid interaction issues with screen readers. 
  • Forms need to be fully accessible by including such items as matching visual and programmatic labels, screen reader accessible requirement instructions, and accessible error notifications. 

The Covid-19 pandemic is shining a bright light on the need for full web accessibility. 

In an environment where all aspects of our lives have moved online, we can no longer consider web accessibility to be a “nice to have” or a feature that we can put off until a later point. Creating fully accessible websites, media, and correspondence has always been both good business and the right thing to do. Covid-19 is helping us to understand why. 

Looking for information and insights on creating online experiences that are accessible, inclusive and ADA compliant? Contact us today.

Oct 15 2020
Oct 15

Until recently, content management systems essentially fell into one of two camps:

  • Intuitive, easy-to-create and manage SAAS solutions, such as WIX and Squarespace, or
  • Flexible and scalable solutions, such as Drupal, for websites with complex data models and a depth of content.  

Quantum leaps in functionality that leverage component-based web design systems have broken down the wall between these two camps. This gap can now be bridged within Drupal, allowing for drag and drop content management capabilities. 

Promet’s strategy for achieving this new paradigm incorporates two open-source solutions: Emulsify, a component-driven Drupal theme, and Provus, our Drupal kickstart  that packages commonly used features into reusable components for a drag-and-drop editing experience. 

During Drupal GovCon last month, Aaron Couch and I delivered a presentation on Drag and Drop Content Management Systems for Government Websites. The types of requirements that we addressed during this presentation are, of course, not unique to government agencies. 

Key among them: 

  • Improve digital services across the board, 
  • Push more transactions and interactions online for purposes of reducing costs and ensuring agility,
  • Meet increasingly high expectations among citizens and customers,
  • Communicate changes quickly, and 
  • Enhance efficiencies by leveraging the potential of “Create Once Publish Everywhere” (COPE). 

 

Foundations of Component-Based Theming

This new world of drag-and-drop possibilities is built upon the realization that despite differences in content modeling, the pages of most websites consist of various combinations of the same “things” -- media galleries, lists of content, cards, search, maps, and social media.  We call these things “components.”

With Promet's new approach to component-driven theming, new potential has emerged for customizable content models that are built with easily “themable” and reusable components, that are then stored in a library that serves as an efficient starting point for projects. 
 

Fueled by Emulsify, Layout Builder, and Provus

While there are a number of component-based themes for Drupal, we’ve singled out the Emulsify® design system as a Drupal starter theme that gives us a huge lift in building reusable components. Emulsify functions as an example of Atomic Design, which refers to a methodology for envisioning the site as a collection of components, based on graduated building blocks from Atoms, to Molecules, to Organisms, to Templates, to Pages. 

This capability combines both a starter component library and Storybook, which is a tool for building user interface components and supports both Twig and React. Storybook can be turned on from within the Emulsify theme, resulting in a highly efficient new workflow for projects. For more on Storybook, check out a recent Drupal GovCon presentation entitled, Component Driven Theming with Storybook, that Promet’s Aaron Couch participated in, along with Emulsify contributors Brian Lewis and Evan Willhite.

Drupal Layout Builder is a drag-and-drop page-building tool in Drupal Core that allows content editors to build out sections of the site. Layout Builder can be implemented as a no-code, site-building tool that retains the features of Drupal, such as flexible content model, revisioning, and custom user permissions and workflows. 

Developed by Promet, Provus provides a kickstart to Drupal site building, packaging commonly used features such as calendaring, FAQs, people, news, and blogs with a drag-and-drop content editing experience. Provus also offers a large array of site-building components like galleries, maps, content lists that can be added and arranged by non-technical users, enabling non-technical users to build and edit a site within an inherently flexible content model. Provus is open source and we welcome the Drupal community’s contributions to the project.

Beyond Traditional Drupal Theming

Having identified that component-based theming tools are key to next-level efficiencies in website building, our next step was to single out an optimal approach for delivering reusable components. 

Traditional Drupal theming includes css and javascript selectors that are intertwined with their context, connecting them to the backend implementation. The result of this “theme for the page,” approach is assets that can’t be reused across projects. 

With a component-based approach, however, selectors are isolated and can be reused. 

Let’s take an example of creating front-end assets for a typical carousel component. In the example below, the assets are tied to the Drupal implementation and combined with other elements. They are not only tied to a paragraph, but the specific name of that paragraph. Reusing this is difficult if there are any changes to the data model. We've identified that a flexible data model is what we want to build.

Traditional Drupal Theming

Traditional Drupal Theming

Traditional Drupal Theming

 

Component-Based Solution

With a component-based approach, on the other hand, all of the assets including the js, css, and template are grouped together. As indicated below, the selectors only reference the elements in the template, so they are isolated within a coherent whole.

component based solution

Making component-based theming work in Drupal, can simply be a matter of embedding. We are able to leverage Twig’s ability to embed or include templates to render the component. If the backend implementation changes or we want to move it to another project the component itself is not changed. 

Below is an example of embedding the previous component. In this case, changing the block type or backend implementation simply requires embedding the same component.

Component based solution in Drupal

Drag-and-Drop Content Management Systems represent a new level of advantages and possibilities for development teams, and even more so for clients. At Promet Source, we’re excited about the approach to component-based theming that we’ve developed, and looking forward to the conversations and amazing new solutions that lie ahead for clients. 

Interested in learning more about the potential for drag-and-drop content management systems and what this can mean for you? Contact us today.

Oct 07 2020
Oct 07

Google  has made gigantic leaps in streamlining search results -- to the point that more than 50% of Google searches no longer result in a click-through to a website or other content. More often than not, search queries and question-based searches can now be answered directly from the Search Engine Results Page (SERP). 

This new world of Zero-Click Searches has upended prior approaches to SEO and analytics, and calls for new expertise and new strategies.
 

What are Zero-Click Searches?

Zero Click searches refer to search results that appear on top of the search engine results page (SERP) that answer the search query without the need to click any further. The search can result in a direct answer, a snippet of the content from the webpage that answers the search query, and sometimes a considerable depth of information.. 

The type of zero-click search result depends on the search query. There are currently six types of search results that are displayed in on the SERP.

Types of Zero-Click Search Results

1. Featured Snippets

Featured snippets are search results that appear in the highly-sought-after position zero of the search engine results page.  Featured snippets provide relevant answers to question-based queries. There are typically five types of featured snippets.

  • Paragraph snippet - Paragraph snippets typically appear on question-based queries such as how-tos, as well as "who," "why," and "what" types of queries.
  • List type snippets - List type results can appear as a numbered list or bulleted lists depending on the search query. List type snippets typically appear for search results such as recipes, ingredient lists, or step-by-step tutorial instruction lists.
  • Table snippets - Table snippets are results that display content in table format.
  • Video snippet - video snippets are results that appear in video format together with featured snippets.
Featured snipped on a SERP pageAn example of a featured snippet answer in response to an inquiry concerning the advantages of Drupal Layout Builder. While the above snippet answers the search query, there's a strong likelihood that the search will also result in a click onto the page for further 

The following is another example of a featured snippet that follows sponsored ad content, while providing a considerable view slice of information along with a photo from a Promet blog post on the topic.

Featured snippet on a SERP page
Featured snippet in response to the Search Inquiry of "What is Human-Centered Web Design. This SERP result from a "What is Human-Centered Web Design" query, also includes  a list of related "People Also Ask" results.

2. Instant Answers

Instant answers are search results from vetted resources -- often quick answers to uncomplicated questions.

Here's the top result from Google Search for “How Many Ounces in a Gallon?” 

Zero click analytics SERP pageAsked and answered with additional references to additional “People Also Ask” information

3. Definition

Definition-based results are for search queries that involve word definition, meaning, usage, and spelling. 

SERP results pageThe above search result for a definition within Drupal appears essentially as a featured snippet.

Definition search results can take the form of a featured snippet or more closely resemble a dictionary entry as in the example below.

SERP page The above definition search result functions as an enhanced dictionary entry.

4. Map Results

Map results are for location-based search queries that display a Google map result in the search result. 

SERP for Map resultsMap results also tend to include "People Also Ask" inquiries.

5. Calculator

Google also provides a calculator for mathematical related searches. Users can perform basic or highly complex mathematical operations straight from the search results page. 

Calculator SERP page The search engine result for the above inquiry resulted in the answer, as well as a fully functional calculator for a full range of complex mathematical equations.

6. Knowledge Panel

A knowledge panel is an expanded featured snippet search result with more detailed information such as additional pictures, map results, and content that is relevant to the search answer. Google has two different types of knowledge panels: brand knowledge panels and local knowledge panels.

 
Brand Knowledge Panel
SERP brand knowledge panel A simple search query for a local Austin, Texas sandwich shop resulted in a depth of information on the SERP concerning menus and product information, a map, as well as locations, and other options.
Local Knowledge Panel
Local SERP knowledge panelThe "near me" search option has become a highly popular Google search feature that is very much relied upon among mobile users.  

 

Impact of Zero-Click Searches on Website Traffic

A featured snippet displays information directly to the search engine results page, which can reduce the click-through rate from the SERP to the website, because the search query is answered -- resulting in a “zero-click.” While the impact of zero-click can be net-zero web traffic from a particular search term, there is always the likelihood that of a click to learn more.

Since digital marketing and search engine optimization (SEO) strategies have traditionally focused on generating site traffic from organic searches in the SERP, zero-click search has created a new dimension to SEO and analytics.

Creating a Strategy for Zero-Click Searches

Being featured as a zero-click search result in the SERP is a significant achievement, because it means that Google has selected the content of a particular webpage over thousands of other webpages. For audiences, this means that the webpage contains the most relevant information based on their search query. Appearing in a featured snippet result provides an immediate credibility boost for the brand and the website.

Despite the inherent achievement, appearing as a featured snippet upends traditional SEO and the potential loss of site visits is not always viewed as an advantage. The following five steps for an updated SEO strategy can help overcome perceived drawbacks, while taking full advantage of the new zero-click world.  
 

1. Conduct Thorough Keyword Research

The first step in ranking for zero-click positions is to identify the keywords that display them in the SERP. Once you have identified the keywords that have zero-click search features then you can create a content strategy to help target those features. 

Targeting question based keywords and creating content to answer those queries will help you rank for the featured snippet position.
 

2. Optimize Pages that are Already Ranked for Keywords with SERP Features

After identifying the keywords that have the zero-click feature in SERP, the next step is to identify current web pages that are already ranking for this keyword. Once you have identified the pages, the next step is to optimize them and add more content to the page.

Optimization includes reducing page loading times by using light images, streamlining the CSS of the webpage, and improving the content on the page.

3. Improve Page Navigation

The next step is to help web visitors already in your website find the page by adding internal links to other relevant web pages in your website. 

Another effective strategy for improving page traffic is to generate more referral traffic to the page by conducting a backlinking campaign to generate more incoming links to the webpage.
 

4. Always Add Meta Data to Web Pages

Adding metadata such as alt text for images, graphs, and other digital assets will allow Google and other search engines to properly identify the contents of your pages. This is extremely helpful, especially if you want to rank for images searches.

Meta descriptions or meta tags help search engines identify the content in the webpages by providing a concise snippet of the content. The meta descriptions can also be displayed as a snippet in the SERP.

5. Register Your Business with Google Business

Creating an account in Google Business will help increase the visibility of your website, especially for local searches. A detailed profile about your business, products, and services will maximize  chances of being featured in the SERP. 

 

Optimizing Zero-Click Searches 

Zero-click searches may not directly result in a visit to your website, but they absolutely boost brand visibility and referral traffic. Targeting the featured snippet position for a particular keyword search phrase is an essential SEO strategy in the current climate. 

Interested in optimizing your search strategies or gaining deeper insights into the new world of zero click search results? Contact us today.

 

 

Sep 29 2020
Sep 29

Covid-19 has presented higher education websites with distinct challenges. During a semester when it's iffy  whether students or faculty will be present on campus at all, a cohesive communications platform that offers easy access to all necessary updates, information, and resources is more important than ever before.

Waubonsee Community College was ahead of the pandemic, reaching out to Promet Source for help in redeveloping its mywcc communications platform at the very start of 2020.

The original mywcc site was built as a a homegrown platform, and a system of outdated applets had led to complicated navigation and difficulty finding needed information. The result was an over reliance on administrative staff for the types of questions and functions that mywcc was intended to handle.

Read the case study on Creating a Transformative, College-wide Communications Platform.

The overriding goal for the new mywcc was a the development of a top-of-mind, go-to resource for conducting college business and staying informed with updates and essential information.  

Flexibility, Speed Fuel Fast Adoption

An absolute key to this initiative was a greater understanding of how the community college cohort group used technology, which meant the assurance of mobile responsiveness and seamless integration with both the college website and students' email accounts.  Also helpful in fast-tracking student adoption of mywcc:

  • A Resources page that presents quick access to high-demand information, and
  • An enhanced Search capability that streamlines access to needed information.

Interested in upgrading and integrating higher education online resources to ensure alignment with both the new and the next normal? Contact us today

Sep 19 2020
Sep 19

In the evolving world of web design and development, component-based design systems represent a revolutionary leap -- a previously missing link that replaces an environment of siloed functions and time-consuming complexities with high velocity capabilities that fuel flexibility, consistency, and collaboration.

Component-based design systems produce inherent efficiencies for designers and developers, and solve the challenges associated with duplication and inconsistency in applying themes, while driving the development of better quality, reusable components.  Clients gain the benefit of better brand management resulting from a simplified content editor experience that allows for bending as necessary, without breaking brand guidelines or page structures. 

As a thought leader on how humans interact with technology, Promet Source has enthusiastically pursued component-based design systems from the standpoint of both: 

  • innovative design patterns that optimize UX and spark engagement, and 
  • streamlined and simplified content editor experiences that allow for a wide range of page possibilities.

Powerful Partnership

As dedicated open source advocates, Promet has adopted Emulsify® as a tool to help us better organize, share, and reuse our custom design systems. Promet serves as both a user and contributor to its support and success. 

Emulsify is an open-source tool for creating design systems as a series of components that can be duplicated and easily manipulated within a set of clear guidelines for designers and developers. Promet is currently leveraging Emulsify on complex web development projects for government, healthcare, and higher education clients.
 

Advantages of Emulsify for Web Design Systems:

  • Integration with a starter library of Drupal-ready components with Storybook,
  • Portability across other CMS platforms and applications,
  • Open source, and
  • Compatibility with both WordPress and Drupal.

As Aaron Couch, director of technology solutions for Promet Source, recently pointed out: 


Emulsify has provided Promet with an optimal starting point to incorporate a component-driven approach into both Drupal and WordPress development. It has changed the way we deliver front-end experiences making our work higher quality, more efficient to deliver, and more accessible, while creating a better user experience for our clients.

Join Promet’s Aaron Couch along with Emulsify contributors Brian Lewis and Evan Willhite on Fri., Sept. 25, 2020, at 3:30 p.m. EDT, during this year’s virtual Drupal GovCon, for “Component-Driven Theming with Storybook.” 

During this session, presenters from Promet and Emulsify will explain how a component-based approach offers greater consistency, flexibility, re-usability, and velocity for front-end development. 

AKA "Atomic Design" 

While metaphors for helping to explain component-based design systems abound, “Atomic Design” (and a book with the same title) authored by Brad Frost) is the one that has gained the most traction and has entered into the lexicon of component-based web design. 

Atomic design looks at a website’s user interface as the collection of five factors that roll up into each other:

  • Atoms,
  • Molecules,
  • Organisms,
  • Templates, and 
  • Pages.
     

Exponential Impact

Component-based design makes front-end web development up to four times faster. This translates into happier clients and the freeing up of resources to focus on fine tuning and providing greater functionality. 

For the content creator and editor, component-based web design provides the ability to edit and revise pages to fit evolving needs and new priorities. 

The new world of “drag and drop” content management is soon to set a new standard in which previous limitations will quickly come to be viewed as  unacceptable. Low code/no code web design is the future.

The four key advantages of Promet’s adoption of the open based tool for creating web design systems powered by Emulsify®:

  • Design systems that can flex, bend, and scale within and among complex web designs,
  • Powerful new possibilities resulting from enhanced consistency, flexibility, re-usability and velocity for front-end development,
  • Elimination of painstaking QA processes in favor of proven patterns and high-quality built-ins that get designers, developers on the same page, and
  • Assurance that non-technical content editors can make multiple changes to a web page without breaking layouts or straying from brand guidelines. 

Need help creating a Drupal design system for your complex website? Contact us today.

Sep 18 2020
Sep 18

Often, the most effective means of managing complexity is a laser-sharp focus on simplification -- breaking down a project into its smallest component parts and visualizing incremental  steps toward completion beginning with the smallest building blocks. 
 
That’s exactly what Brad Frost has achieved in coining the concept of Atomic Design, and authoring a book by the same name.  In clarifying the new capabilities of component-based web design systems, the vocabulary of Atomic Design has gained traction, and entered into the working lexicon of web designers and developers.  
 
As Frost explains:

Atomic design is not a linear process, but rather a mental model to help us think of our user interfaces as both a cohesive whole and a collection of parts at the same time. 

From Atoms to Pages

Atomic design considers a website’s user interface as the collection of five factors that roll up into each other:

  • Atoms,
  • Molecules,
  • Organisms,
  • Templates, and 
  • Pages.

1. Atoms

The basic building blocks such as HTML tags, form labels, and buttons, as well as color palettes and fonts -- essentially all of the factors that designers typically define as a reference point for developers when creating a website’s style guide. 
 

2. Molecules

Chemically speaking, molecules consist of atoms bonded together. Within Atomic Design a molecule make up distinct building blocks and refer to design specifications for functional, reusable combinations of atoms, such as a keyword search bar with a search button. 
 

3. Organisms

Combinations of molecular building blocks form organisms that form distinct sections of a user interface. This is where the design begins to take shape with the creation of reusable components such as a footer consisting of a logo, social media icons, a call to action link, and other branding elements.

4.  Templates

Groups of organisms arranged together form a template. The game-changing factor within component-based design is the inherent flexibility of the templated layout, allowing for a wide range of options such as switching out an image for a text block, and previewing responsive layouts for various devices. 

5. Pages

Pages refer to specific representations of templates that take shape beyond a theoretical example and come to life as a real-world view of what the user will see and experience on the site. It is at the page stage where texting and review concerning the totality of the design system tends to occur and adjustments are made.

To learn more about the powerful potential of component-based web design systems, join Promet’s Aaron Couch along with Emulsify’s Brian Lewis and Evan Willhitel on Fri., Sept. 25, 2020, at 3:30 p.m. EDT, during the virtual Drupal GovCon, for “Component-Driven Theming with Storybook.” 

Stay tuned for further announcements concerning Promet and Emulsify® and in the meantime, Contact Us for help or consultation concerning the creation of a complex Drupal website. 

Sep 18 2020
Sep 18

Often, the most effective means of managing complexity is a laser-sharp focus on simplification -- breaking down a project into its smallest component parts and visualizing incremental  steps toward completion beginning with the smallest building blocks. 
 
That’s exactly what Brad Frost has achieved in coining the concept of Atomic Design, and authoring a book by the same name.  In clarifying the new capabilities of component-based web design systems, the vocabulary of Atomic Design has gained traction, and entered into the working lexicon of web designers and developers.  
 
As Frost explains:

Atomic design is not a linear process, but rather a mental model to help us think of our user interfaces as both a cohesive whole and a collection of parts at the same time. 

From Atoms to Pages

Atomic design considers a website’s user interface as the collection of five factors that roll up into each other:

  • Atoms,
  • Molecules,
  • Organisms,
  • Templates, and 
  • Pages.

1. Atoms

The basic building blocks such as HTML tags, form labels, and buttons, as well as color palettes and fonts -- essentially all of the factors that designers typically define as a reference point for developers when creating a website’s style guide. 
 

2. Molecules

Chemically speaking, molecules consist of atoms bonded together. Within Atomic Design a molecule make up distinct building blocks and refer to design specifications for functional, reusable combinations of atoms, such as a keyword search bar with a search button. 
 

3. Organisms

Combinations of molecular building blocks form organisms that form distinct sections of a user interface. This is where the design begins to take shape with the creation of reusable components such as a footer consisting of a logo, social media icons, a call to action link, and other branding elements.

4.  Templates

Groups of organisms arranged together form a template. The game-changing factor within component-based design is the inherent flexibility of the templated layout, allowing for a wide range of options such as switching out an image for a text block, and previewing responsive layouts for various devices. 

5. Pages

Pages refer to specific representations of templates that take shape beyond a theoretical example and come to life as a real-world view of what the user will see and experience on the site. It is at the page stage where texting and review concerning the totality of the design system tends to occur and adjustments are made.

Need help creating an Atomic Design system for your organization’s website that allows for greater flexibility that maintains brand consistency? Get in touch!

Aug 12 2020
Aug 12

Google has launched an important new feature to help bring critical alerts and announcements to the forefront of search. While COVID-19 has highlighted the need to convey a single source of truth and critical updates in a timely manner, alerts can cover a wide range of topics that include weather events, criminal activity, threats of foodborne illness, environmental dangers, street closures, and much more. 

Here's how you can now ensure that your site's alerts are highlighted as a rich result on a Search Engine Results Page (SERP).

As shown below, the rich result includes the page’s regular snippet description and can contain a structured summary of an announcement that can be expanded directly from SERP.

Google alert SERP result
 

Using the Special Announcement Markup

The special announcement is a type of structured data that is tagged as a Special Announcement Markup that the Google Search Engine can identify and display in the Search Engine Results Page. 

Google special announcement markup

Two Options for Implementing COVID-19 Special Announcement Markups

Google has provided websites with two ways to implement COVID-19 announcements markups to their webpages.
 

1. Add Structured Data to Web pages (Recommended Method)

Google recommends that websites add special announcements as structured data markups, as structured data is a standardized format for providing information about the page and classifying the page content.
 

2. Submit Announcements in Search Console (Alternative Method)

The second method is intended as a short-term solution for websites that have limited technical ability or support. Websites need to manually send a request inside Google Search Console through the special reporting tab to submit a special announcement request for a specific page of their website. This is a more tedious process as it requires pages to be manually updated inside Google Search Console whenever there are updates.
 

Google Search Console

Google is actively developing the COVID-19 Special Announcement Feature and we can expect changes in requirements or guidelines as the COVID-19 pandemic progresses. These special announcements are designed to provide crucial and accurate information from a single source of truth. information and reduce the risk of panic that can be caused by misinformation. 

COVID-related announcements can include:

  • Announcement of a shelter-in-place directive
  • Closure notice (for example, closing a school or public transportation)
  • Announcement of government benefits (for example, unemployment support, paid leave, or one-time payments)
  • Quarantine guidelines
  • Travel restrictions
  • Notification of a new drive-through testing center
  • Announcement of an event transitioning from offline to online, or cancellation
  • Announcement of revised hours and shopping restrictions
  • Disease spread statistics and maps

In an environment characterized by drastically curtailed social engagement and rampant uncertainty about what’s next, websites have never served such a vital role for communications and engagement. At Promet Source, we are actively consulting with clients from every sector to ensure that their websites step up to the challenge of current realities. Let us know what we can do for you. 
 

Aug 05 2020
Aug 05

In the current environment, search engines are an essential audience. 

While it’s widely understood that attracting the attention of the major search engines, is key to a website’s overall effectiveness, too often, Search Engine Optimization is viewed as a task that can be checked off of a list once completed.

SEO needs to be viewed as an ongoing activity, with a consistent monitoring of metrics, along with a focus on learning and adjustments to strategy based on the intelligence hidden in the data.

Sharpening the Focus on SEO

Volumes of readily available information from thousands of different websites is  available online. Thousands of organizations compete for attention, which means that effective Search Engine Optimization (SEO) strategies need to constantly stay ahead of what the competition is doing and aligned with search engines’ most up-to-date methods of crawling websites for relevant information. While the early days of SEO amounted to efforts to game the search engines, the search algorithms have become quite intelligent and now favor relevant content and well structured sites. 

SEO strategies are designed to improve organizations’ rank on the Search Engine Results Pages (SERP), which follow the search for specific keywords or queries. Appearing near the top of a Google or Bing SERP is essential for driving website traffic and conversions. A recent article in Search Engine Journal reported that sites which appear on the first page of a Google search receive, on average, 91.5 percent of the traffic share. 

Great SEO is also aligned with great UX and web accessibility. The search engines favor websites that are streamlined for user accessibility and enabled for mobile.

How to Perform Continuous SEO on a Drupal or WordPress Website

1. Monitor and Collect Data

The first step in the SEO process is to monitor and gather key performance indicators (KPIs).  KPIs indicate how a website is performing relative to specific metrics, and help to gauge a site’s status relative to competitors and past performance. 

Search Engines such as Google and Microsoft Bing provide free and easy-to-use tools to help gather and collect important data and generate reports on the following website KPIs.
 

Key Performance Indicators
  • Number of Users: This metric is defined as the number of visitors who have initiated one session on a website. A session is a group of user interactions within a given timeframe. A single user can generate multiple sessions if they return to the website at a later time and a single session can also involve multiple views on pages and interactions, depending on the behavior of the user.
  • Number of Views: The number of views or page views refers to the total number of times a website is viewed. One user session can generate multiple views and this metric indicates which pages are the most popular. 
  • Organic Sessions: Organic Sessions refer to visits generated by users that are coming from an actual search engine query, vs.visitors that found your site via paid advertisements. This metric helps gauge SEO performance by indicting the amount of traffic is generated by SERP results.
  • Bounce Rate: Bounce Rate refers to the percentage of visitors who exit the site after viewing only one page. Of course, sometimes visitors leave because they find exactly what they need on the one page, but the goal is to maximize interaction and the value of the website, and that’s indicated by a low bounce rate. Bounce rate is an important metric that reflects the quality of your website and individual web pages.
  • Pages Per Session: The pages per session metric indicates the average number of pages a user visits for each session. This metric is a great indicator of the ease of navigation.
  • Average Session Duration: The average session duration is an important indicator of the quality of content. The longer a visitor spends on the website the greater chances of the visit being converted into a lead. 

2.  Keep the Sitemap Updated

A sitemap is an important file that provides critical information about the pages, videos, images, assets, and other files that are on a website. Sitemaps help search engines to crawl the website. They also provides an indication of which web pages and files are most important. This is a key factor in prioritization on the SERP. Having a sitemap that is continuously updated helps search engines quickly detect and crawl new pages. The sooner that search engines can find your webpage the sooner that page can generate more organic traffic.

Free tools such as Google Search Console or Bing Webmaster help to monitor websites for website indexing issues, coverage, or sitemap crawl issues. There are plenty of modules available for Drupal websites to build and automatically update sitemaps that can be submitted to Google Search Console and Bing Webmaster tool. Similarly, WordPress websites also have the option to install plug-ins that can also create and automatically update sitemaps.

3. Design for Web Accessibility

Continuously designing and updating a website for accessibility can also have a significant impact on SEO. Here are three quick  facts concerning the SEO and web accessibility connection:

  • Search engines also scan the alt text designed for the screen readers that visually impaired users rely upon.
  • Both screen readers and search engines scan title tags.
  • Both screen readers and search engines rely on meaningful html header hierarchies. 

Attention to SEO principles and guidelines not only results in higher search engine rankings, it also ensures that your site is accessible to a broader audience of users with disabilities. 

4. Keep Track of Keywords

Identifying and tracking relevant keywords on a website can help to gauge the performance of the content relative to search page rankings. Tracking keywords will also reveal opportunities that can be targeted with new content, as well as help in building content strategy and that is relevant to the target audience.

5. Pay Attention to Site Speed

Site speed is a factor is search page rankings, and continually monitoring for site speed will help detect problems before they can negatively impact rankings.
 

Best Practices for Optimizing Site Speed
  • Reduce Image Size: Reducing Image sizes can help improve page loading times and performance.
  • Minify CSS, JavaScript, and HTML: Optimize page code by removing unnecessary spaces, commas, and other characters.
  • Minimize Redirects: Minimize the number of unnecessary redirects that are needed to reach a page.
  • Enable Compression: GZIP Compression can greatly reduce page loading times.

 

A Constant Focus on SEO

As search engines are becoming increasingly intelligent and the competition for high page rankings intensifies, a sharpened focus on SEO is an essential  exercise for staying in the game, with a competitive edge and meaningful insight into audience behavior.

At Promet Source, SEO is integrated into our multi-faceted approach for developing great websites. Looking for tips and techniques to improve SEO and build in continuous monitoring for optimal impact? Contact us today.

Jul 13 2020
Jul 13

Drupal 9’s big splash in early June sparked a widespread realization that migration needed to move to front burner status in anticipation of a Nov. 2021 decommission date for Drupal 7 and 8. That sense of urgency has been temporarily tabled as the Drupal organization took the widespread uncertainty and upheaval of the global pandemic into account, and moved the end-of-life date for Drupal 7 and Drupal 8 out by one year to November 2022.

So now what?

How does this date extension change how site owners should be approaching migration? What’s in store for Drupal 9? And what else do we need to know right now? 

Subscribing to the Kenneth Blanchard conviction that, “None of us is as smart as all of us,” we reached out this week to some of Promet’s top experts for insights into these and other important issues.

Here’s what they had to say:

Drupal 9 Expert Panelists

Juan Garay, Project Manager, Scrum Master
Luc Bezier, Solutions Architect
Aaron Armstrong, Drupal Developer
John Ross Castano, Web and Support Developer

Q. Now that the Drupal Organization has extended for one year -- from Nov. 2021 to Nov. 2022 -- the decommission date for Drupal 7 and 8, is there a compelling reason to migrate now?

Juan: I wouldn’t suggest migrating to 9 now, as there are many contributed modules that are not available for Drupal 9 yet.

I would tho encourage anyone to migrate from Drupal 7 to 8 ASAP, as the improvements between Drupal 7 and Drupal 8 are far and many.

Also, migrating right now from Drupal 7 to Drupal 8 will make for a much smoother migration path to Drupal 9 in the future, as Drupal 8 to Drupal 9 migrations (content in particular), are meant to be considerably smoother than migrations from previous versions of Drupal.

Aaron: November 2, 2021 is still the date that we need to focus on as the effective end-of-life date for Drupal and 8. Drupal is dependent upon Symfony, and Symfony will no longer be supported after November 2021. Security patches are all that will remain available after that date. My recommendation for any website that’s still on Drupal 7 is to move forward now with a migration to Drupal 8, and then as Drupal 9 matures, build out a Drupal 9 migration timeline. 

Q. What do you view as the primary, overarching benefit of Drupal 8 and 9 over Drupal 7?

Juan: In Drupal 8 and Drupal 9, nearly the entire system uses the Drupal Entity API, which provides a much more robust and flexible framework for building custom solutions.

John Ross: Drupal 8 and 9 have improved over Drupal 7 by leaps in bounds in terms of deployments through Configuration Management (and content). Automatic deployment is a breeze between environments and has become very robust since Drupal 7. This is one of the biggest issues or dilemmas on our multi-environment development workflow when using Drupal 7. Drupal 7 heavily relies on Features and other similar modules, but cannot really provide a “one-size-fits-all” solution for an automatic deployment.

Aaron: The deployment and configuration export/import is the biggest benefit for Drupal 8 and 9. It saves hours upon hours of work, which previously was accomplished with Features. 

Also, there are a multitude of contributed modules in Drupal 7, which are now core modules in Drupal 8. Translations are a huge example. Drupal 8 comes ready, out of the box, for translations. Drupal 7, on the other hand, required loads of contributed modules and configurations to accomplish the same thing. 


Q. Drupal 9 has been described as akin to more of a “point release” from Drupal 8 than the Drupal 7 to Drupal 8 leap forward in features and functionality. So what is new or potentially game-changing about Drupal 9?

Luc: Drupal 9 is not a game changer, in the sense that Drupal 8 was. Drupal depends on Symfony, if you were to very quickly summarize, you could say that Drupal 9 is essentially a new version of Symfony under the hood. Drupal 9.0 has the same features Drupal 8.9, with a clean up of some functions that it was using. The aspect of Drupal 9 that is game changing is the fact that it is the first release for Drupal to be non-breaking. You don’t need to process a major migration to update, it is relatively easy to migrate from Drupal 8 to Drupal 9. 

Aaron: Drupal 9 solidifies some of the features in Drupal 8. As others have mentioned, it also is a very easy upgrade between Drupal 8 and 9. Up to this point, Drupal migrations have been time-consuming process. 


Q. Drupal 7 was released on Jan. 5, 2011, nearly 10 years ago. Can you comment on some of the most significant trends in UI/UX or within Drupal functionality that have emerged since that time?

Juan: Among the most significant developments is the ability to edit content inline, in real-time through the Drupal 8 Layout Builder interface

Luc: During the development of Drupal 8, I remember meeting Alex Pott (Drupal 8 core co-maintainer, and Drupal 8 configuration system co-maintainer). I worked with him on some changes to the configuration system. This system is for me the biggest improvement in the way we build and maintain large websites using Drupal 8 and above.

Aaron: The use of importing and exporting configuration yaml files is the most significant change from Drupal 7. The default back-end theme has improved greatly, along with the number of core modules in Drupal 8 and 9. 


Q. How have businesses and organizations changed in their use of and need for Drupal over the past decade?  

Luc: The complexity of websites have increased, and thanks to Drupal’s level of abstraction, we are also able to build more complex solutions. For example, it is common for large companies or administrations to have more than a dozen of websites now, and using Drupal with tools like Acquia Cloud Site Factory, one company can generate websites on demand.

Aaron: Drupal has always been an enterprise type CMS that works well with larger sites. I think it has continued to work in that space, while allowing for much more complex sites, deployments, and configuration sharing.

There also have been huge leaps ahead with the hosting provided by Acquia and Pantheon. 

Q. What do you view as the most significant Drupal evolutionary developments over the past decade?

Aaron: The possibility of headless Drupal is what first comes to mind, but the configuration management, as well as translations being part of core, are the biggest advancements in my opinion.

Luc: The past decade saw the emergence of static sites generators (Jekyll in Ruby, Hugo in Go). I find it very interesting as it is removing all the overhead of modern websites for performance and maintenance. Nothing will ever be faster than a plain HTML page. A module like Tome (by Samuel Mortenson) bridges the gap between Drupal and the static sites generator solutions, allowing Drupal to be automatically exported as plain HTML. This opens some interesting possibilities for Drupal.


Any other questions on Drupal? Drupal 9? The path to migration? Drupal is in our DNA at Promet Source and we are happy to help. Let us know what we can do for you!  Contact us today


 

Feb 14 2019
Feb 14

A commercial came on the radio recently advertising a software application that would, basically, revolutionize data management and enable employees to be more efficient. My first thought was, “How can they possibly promise that when they don’t know their customers’ data management processes?” Then, it became clear. The business processes would have to be changed in order to accommodate the software.

Is that appropriate? Is it right that an organization should be required to change the way it conducts business in order to implement a software application? 

Sometimes yes. Sometimes no. 

The following four factors can serve as an essential guide for evaluating the need for change and ensuring a successful transition to a new solution. 

  1. Process Analysis
  2. Process Improvement
  3. Process Support
  4. Change Management

1. Process Analysis

Before committing to the latest and greatest software that promises to revolutionize the way you do business, make sure you’ve already documented current processes and have a clear understanding of what’s working well and what can be improved. Over the last few decades, several methodologies have been created and used to analyze and improve processes. Key among them: Six Sigma, Lean Manufacturing, and Total Quality Management (TQM).

How to Streamline Process Analysis

In simple terms, document the way you create, edit, and manage your data. Task-by-task, step-by-step, what does your team do to get the job done? If you see a problem with a process, keep documenting. Improvements, changes, redesigns come in the next step.

Steps to Document Processes

At the core of all process documentation is the process flowchart: an illustration with various boxes and decision diamonds connected with arrows from one step to the next. Collect as much data and as many contingencies as possible to make this flowchart as meaningful and robust as possible.

Diving Deeper

Integrated Definition (IDEF) methods look at more than just the steps taken to complete a task within a process. IDEF takes the following into account:

  • Input - What is needed to complete the steps in the task? Understanding this information can highlight deficiencies and can highlight flaws in effective completion of a particular step. 
  • Output - What does the task produce? Is the outcome what it needs to be?
  • Mechanisms - What tools are needed to perform the steps in the task? Can new technology make a difference?
  • Controls - What ensures that the steps within the task are being performed correctly?

Swimlane or Functional Flowcharts

In addition to the four items from IDEF data, knowing who performs a task is also important. As you draw the boxes and connect them with arrows, place them in a lane that represents the “Who” of process. Knowing who does what can reveal possible over-tasking and/or bottleneck issues in production and efficiency.

Getting Started

Whiteboards and Post-it can be an easy place to start process documentation. With today’s high definition smartphone cameras, you can sketch flowcharts, take a picture, and then share with stakeholders for their review and input. Once you have collected all relevant information, tools such as Visio or Lucidchart can make complicated process flows easier to create and visualize. 

2. Process Improvement

When you know how your current processes are performed, you can start to make improvements--whether incremental or a complete redesign (A.K.A reengineering). 

Low-hanging Fruit

Some needed improvements will likely be obvious. For example, someone on the process team says, “I didn’t know that you were doing that? I do it, too.” Duplication of effort doesn’t require metrics to be collected to determine that steps can be taken to enhance efficiency.

However, most processes require some form of metric collection to determine where improvements can be made. Metrics can include research costs, development time frames, quality assurance oversights, or frequency of downtime.

Knowing What to Change

If the needed improvement isn’t obvious, metrics can help guide the decision-making process. For example, how much time does it take to complete a process today? Could that be improved? Brainstorm ideas on how to shorten the time. Test the change and remeasure. 

Too often, data is collected with the intent of measuring the success of the process, but the data being collected is does not reflect objectives. For example, if the goal of a website or a particular page is to teach, metrics concerning the number of page visits does not indicate the degree to which that goal is being achieved. A more telling metric would be the amount of time a visitor spends on the lesson pages. Even more revealing would be the number of quizzes passed after a visitor engaged with the lessons.  

Before choosing metrics to be collected, understand your goal, determine the level of improvement you want to see, then start measuring that which will actually inform your goal.

3. Process Support

Key to process improvement is an analysis of how technology is can enhance productivity and efficiencies. 

For example: “We can cut three days worth of effort for three employees if we integrate the XYZ software into our process.” This kind of statement sounds like a worthy goal, assuming the cost to transition doesn’t exceed the long-term savings it can help realize. 

Calculating the Cost of Change

Open source software applications start out with a great price tag: Free. However, unless you use the application as is, there is always a cost associated with turning it into what you need. There are many more factors to consider than the upfront cost of the software. 

Costs can include:

  • Training on new processes
  • Training on the new software application acquired to support the new process
  • A drop in productivity and efficiency until the new process/application is adopted and accepted by your staff
  • Technology needed to support the new application
  • Keep in mind: The list of ancillary costs that are involved in the transition are unlikely to appear at the top of the salesperson’s brochure.

Return on Investment

ROI assessments will vary. Two values are needed to make this computation: cost and benefits. 

Once you've computed the short-term and long-term costs, you need to determine the benefits you gain. In a situation where investment directly translates into profit, this calculation can be straightforward.

However, sometimes the benefits are cost savings: “We used to spend this. Now we spend that.” When this is the case, instead of a cost/benefit ratio, a breakdown calculation might be required to determine how long it will take to recoup costs. 

The most complicated analysis will result from benefits such as an increase in customer satisfaction in which the benefit does not have a direct monetary value.

4. Change Management

When a team cannot see the benefit or resists change, new initiatives face an uphill battle. That’s why circling back to the process analysis phase and ensuring the buy-in of those who are being counted on to use the new application is a critical success factor.

Keep in mind that employees may not have access to the big-picture business goals that management sees, but change has the greatest chance of being realized if those who will be required to support it are informed as to why it needs to happen and included, at some level, in the decision-making process. 

Indeed, change management doesn’t start when the new application is ready to be implemented. Change management starts when:

  • All the costs of change are considered;
  • The full scope of process changes are identified;
  • Training is planned and delivered; and 
  • The campaign for change acceptance is designed and initiated.

Conclusion

You might be the boss. You might believe that the software application just discovered is what  your company or your department needs. As much as that matters, you need buy in. You need the support of the people who make your business possible. You also need to engage in a disciplined analysis of the processes that will be impacted, along with anticipated improvements and the level of support that will be deployed.

From ensuring that clients’ entire online presence is compliant with ADA accessibility guidelines to web solutions that optimize impact in the ever-evolving digital environment, we at Promet Source serve as a powerful source of transformative digital possibilities. Contact us today to learn what we can do for you.

Jan 23 2019
Jan 23

Besides Title, the most common field label found on a content type form is Body. Of course, this is where you place the body of your content. It’s your blog post, your how-to instructions, or maybe an event description. You know exactly what needs to be provided in this field because you are the trained author. What happens when the scenario includes many authors with varied skills?

Without clearly visible instructions for the form and the form fields, content authors can make mistakes. There are four default features in Drupal 8 that provide instructions for content authors.

Help

Body field configuration interface

When configuring a field, all fields except Title, you can include help text. The help text appears under the field, just like you see here on the configuration form where the help text for the help text field says, “Instruction to present to the user below this field on the editing form.”

Pros

The label of a field might not communicate the full intent or purpose of the field, so adding instructions in the help field can go a long way to ensuring an author uses the field correctly. 

For example, the Tags field on the Article content type provides default help text: Enter a comma-separated list. For example: Amsterdam, Mexico City, "Cleveland, Ohio" This provides instructions for entering tags correctly. 

However, if you need to add additional instruction regarding the context of the tags, you can include a statement like, “Do not use terms already offered in the Topics field.” 

Cons

The common placement of instructions below a field isn’t always noticeable. For example, the screenshot below shows the body field with help text below. Is it eye catching? Obvious?

Body field on the Add node page.

The size of a field can make providing easy to see instructions a challenge. And, if you need to make an accessible content type, the help text feature needs a little work to make it WCAG compliant. 

Placeholder

Configuration options for Body field on the Manage form display

Using placeholder text inside the field is another option. Although this feature is not available for all field types, it does enable you to include 128 characters of instructions. Located on the Manage Form Display tab for the content type, it’s just one configuration option available.

Pros

As mentioned in the Help section above, the Title field doesn’t have a help text option. However, the placeholder feature is available to provide tips on title strategies. Or, if the instruction is short and simple, such as a date format of MM/DD/YYYY can help users quickly understand the sequence of the date parts.

Cons

It’s only 128 characters and if the field size is less that that, not all of the instructions will be visible. On the topic of visibility, the Placeholder feature is not read by a screen reader. And, unless you do some browser specific CSS overrides, the contrast of Placeholder text might not meet WCAG color contrast criterion.

Lastly, when a user clicks in the field to enter data, the placeholder text disappears.  

Default Values

Body field default content configuration interface

The default value feature for fields is a great way to speed up data entry when the same entry is expected frequently. However, it can also be used to communicate instructions to the content author. You can go as far as providing a content template where the appropriate formatting has already been applied. 

Pros

Uniformity. Clarity. An experienced author will have their own way of conveying their thoughts, but that way isn’t always what’s best for an organization. Or, a newbie writer might need a little help to get started.

Notice the instructions for the often forgotten Summary feature. If you require a summary, include instructions like those shown in the example above and the Summary field will be open and ready when the content author uses the content type.

Also, unlike the Placeholder option, clicking in the field does not make the instructions disappear. 

Cons

The content author needs to remember to delete the instruction text. A small price to pay.

Content Type Explanation/Guidelines

Submission field settings for the content type

According to the Form Instructions tutorial provided by W3C, “Where relevant, provide overall instructions that apply to the entire form.” Each content type has the option to include a form explanation or submission guideline, as the field label suggests. 

Pros

Content add form with submission guidelines sample text.

The form explanation appears just above the Title field and outside the <form> element, which is needed for accessibility. You can also include HTML elements to format your instructions. 

Cons

If you need to format your form instructions, you will need to enter your own HTML as there is no HTML editor bar.

Conclusion

Not all forms are self-explanatory. Not all field purposes can be easily deduced. Drupal provides several options for providing guidance to your content authors, each with their own pros and cons. 

As you plan the way your finished content will be presented to site visitors, remember to plan your content type forms. Just because a content author receives training when the site is delivered, that doesn’t mean they will remember everything they learned. Form instructions help.
 

Jan 17 2019
Jan 17

Promet and Drupal go way back. We were at some of the first DrupalCons. We were an Acquia partner back when nobody had heard of Acquia. Most of our work today is building large, complex Drupal sites. (We are branching out though. Feel free to talk to us about Wordpress or other web development needs!) We love Drupal, and we’ve used it to build everything from simple to very complex websites.

However, Drupal 8 has changed the Drupal ecosystem. Drupal 8 is designed for engaging digital experiences. What does that mean? Mostly it means complex or mission-critical web applications. You can be a 2-person company working out of a basement, but if your website is everything to the business, there may be a good argument to build that site on Drupal 8. 

Drupal 7 was a swiss army knife. You can effectively do anything from a small blog site to the largest most complex sites online with it. Drupal 8 is more like a finely sharpened carbon steel Chef’s knife. It still does a lot, but you really shouldn’t use it to peel an apple.

Was that analogy too tortured? Anyway, we are still a Drupal first agency. However, there are definitely use cases where Drupal 8 is not the answer. Compare your project to the examples below to get an idea if Drupal 8 may be the right CMS for your website.

A small 5-10 page “brochure” site that may be updated once a quarter, if that.

This should not be a Drupal 8 site. Wordpress is probably the most common recommendation in this situation, however, I would recommend a different route. If you truly won’t be doing more than the occasional quarterly update, I’d recommend a static site generator (SSG) such as Pelican or GatsbyJS. Wordpress still comes with the overhead of keeping a database-backed web application updated and secure. For a few pages updated a few times a year, I would generate that site with the SSG and push the resulting HTML pages to a web server. With just HTML exposed on the server, your only security concern is if somebody compromises your server account. There is no database or CMS to hack. Your hosting costs are minimized this way too.

A small 50-250 page website that is updated frequently.

On the small end of this spectrum, Wordpress is the most common recommendation. As you get to the 250-page end there starts to be an argument for Drupal 8, especially if you are dealing with some more complex content types. Be careful though. A cheaper Wordpress shop will buy a $30 theme and tweak it to fit your needs. This can work fine, as long as the theme they buy was well constructed based on Wordpress best practices. Often those purchased themes are kind of a mess at the code level. 

If the site is small with static content that is highly trafficked, you can do something really interesting by using the GatsyJS SSG as a front end to Drupal. You can manage the content via Drupal, but publish it as static HTML pages via Gatsby to minimize hosting overhead and improve performance.

A large site with hundreds or thousands of pages that are updated rarely.

Drupal 8 will be the normal recommendation here, and it’s a perfectly valid recommendation. Drupal will allow you to publish structured content across the entire site, plus use taxonomy to relate content. If you need to manage user permissions about who can do what with the content, Drupal 8 becomes a great answer.

But what if you are publishing documentation that will almost never change? Do you really need the overhead of an enterprise-grade CMS that will get used rarely once the site launches? I think the static site generators are a really interesting solution to this use case. Pelican, to reference the SSG I’m most familiar with, can implement tags to relate content, and can identify different authors if it is a multi-author scenario, It has no concept of user permissions though. I’m not aware of any major sites that have been done this way, but it seems like a very low overhead answer to the publish a lot of content once and then mostly forget about it scenario. If you have a project like this let’s talk!

You have a large complex site that has a variety of content types that integrate with 3rd party systems, and it’s crucial to your business that the site stays available and performant.

This is the Drupal 8 wheelhouse. This is what Drupal 8 does best. You can think of Drupal 8 as a box of standard Lego bricks. What you build with it is only limited by your imagination, time and resources. (How big is that box of Lego bricks?) A few of the scenarios that Drupal excels at include:

  • Multi-author websites where you need granular control of publishing and editing permissions by either individual users or groups. This extends to workflow issues where you need a publishing workflow for editorial oversight.
  • E-commerce applications where you are generating significant revenue from the website.
  • Integrated solutions where the website needs to share or sync data with other business systems such as a CRM or AMS.
  • Multi-site applications where you need to manage dozens to hundreds of websites that will all share common elements while allowing for localized control of specific content elements on specific websites.
  • Multi-output applications (decoupled Drupal!) where you need to deliver the same content to disparate devices such as web browsers, mobile apps, digital signage,  voice-activated devices such as an Amazon Echo or Google Home device; and future devices we might not have thought of yet. I can see us interacting with websites via voice activation in our cars in the not too distant future, if it's not already being done. 
  • Multi-lingual websites where you need to manage translated content.

Hey Chris, you didn’t mention SquareSpace, Wix and similar services for smaller sites.

That is correct, I didn’t. Promet is an open source consulting firm, and personally, I’m an open source advocate. I avoid proprietary solutions when an open source option exists. That said, if you need to publish a small static website and want to take the path of least resistance with SquareSpace or similar, I don’t think it’s a particularly bad idea.  If your content got locked up in one of those services the site is presumably small enough that starting over won’t be that painful. But I’m not going to recommend those services, at least not in writing ;)

If you have any questions about what to do with your website please get in touch.
 

Dec 19 2018
Dec 19

Imagine if you will, you have an Events link on your main menu. Someone clicks on it and the Events landing page is loaded in their browser. How was this page built? With Drupal, you have several options. 

If you are the kind of person who likes to have a say in the way things are done, be it from a previous bad experience or idle curiosity, the following will help you engage in the planning aspects of your Drupal site. So, let’s look at five recipes for building landing pages in Drupal.

  • Node page
  • Node Plus View Block
  • A View Page Plus a Block
  • Panel Page
  • Custom Theme Page

Node Page

Content pages in Drupal are called nodes. You fill out a form (e.g., a content type) online, save, and you have an article or event or some other kind of page. This page has a URL. That’s important to remember. Every page in a website has to have a URL. 

How

Using Drupal’s default Basic Page content type, you fill out the form. Give the page a title of About Us. Fill in the body field with information about you or your company. Add it to the main navigation menu with a check of a box. Lastly, you create an URL alias. Instead of the default format of /node/3, you want /about-us. Save and you see your new landing page.

Yes, it’s boring, but we’re just getting warmed up. 

Why

Simple page. Simple technique. Easy to create and edit. Easy to translate in a multilingual site. And let’s not forget the other cool things you can do with a node.

Node Plus a View

Building on the previous example, let’s build an Events landing page. Obviously, this kind of page is going to be a little more complicated. Here are the requirements: a title, some introductory text, and a list of Events that you created using an Events content type. You will have many events so using a manual approach to creating and updating a list of events is not a fun idea.

How

With this scenario, you use the Basic Page content type and create a node titled Events. Using the body field, you add some text that describes your events. Like before, check the box to add this node to the main navigation. Give your page the URL alias of /events. Save and the first part of the configuration is complete.

The next step in the configuration process is a little more complicated, but it’s the concepts you need, not the details at this time.

Drupal has a module called Views. It’s an incredible tool that lets you create an SQL query on the database and then create a display for the results of that query. For this landing page, you need events for the future, not the past, so you filter accordingly.

Given we already have a Drupal feature with its own URL (the event node), we don’t need another. That means you will create a block display for the SQL query results. Blocks can be small bits of information or larger, more complicated displays. They can even hold forms. What they don’t have is a URL. They only show up because a page is there to host them.

Without going into all the particulars, you will place the block so it appears under the body field. If you want to know more about how this done, please join us in a Drupal 8 Site Building Best Practice training class.

When you go to the yoursitename.com/events URL, you will see the Events node and the view block that lists the upcoming events. With some styling, you can make the two features (node and view) appear as one, seamless page.

Why

Some will argue that you could have made a View page versus using this two-step process. And, in the next example, you will. In this scenario, you looked ahead and saw that the introduction text would not be a fixed blurb. You will change it from one season to another and your staff will not have the skills to edit a View.

So, this scenario worked nicely for your business process and staff.

A View Page Plus a Block

Let’s change up the requirements as a means of introducing another build option. You need a list of events, but instead of some introduction text, you need an image banner. There are several ways to accommodate this new image requirement, including adding to the previous scenario. In this example, we will use a View page and a block.

How

Create an SQL query, grabbing all the events scheduled for the future. Instead of displaying the list of events in a block, you create a page with a URL of /events and place it on the main navigation menu.

Next, create the block that will display your image banner. Like with most requirements, Drupal provides several alternatives to meeting them. For this scenario, assuming you are using Drupal 8, create a new block type called Image Banner. Add an image field to the new block form and set the field display to show only the image.

Create a block, using your new block type. Upload the image you need for the Events landing page. This process is very similar to creating a node. The input form looks similar as well. 

Place the banner image block either above or below the page title block to match your design. This is a quick and easy way to insert an image above the title of the page if that is your choice. 

Why

A View page isn’t like a node. It doesn’t have fields. You can add a header and footer text, but it’s not the same as adding a field to a node. Bottom line, a View show the results of a query - typically that of nodes. So, if you need to display information other than the query results, you might need to use methods like described above, by adding blocks or combining a node with a view.

Another reason for mixing and matching features to create a landing page is display. By default, a Drupal page - node or view - is broken into two parts: Title block and Main Page Content block. If we had chosen to add an image to the available header text box in the view, the image would appear below the page title. Yes, you can do some template coding and rearrange things a bit, but why would you if you could simply place a block and accomplish the same goal.

The point of all this is, remember that content comes in parts in the Drupal world, and quite often, a simple mix and match strategy is all that needed.

Taxonomy View Page

A technique that can be overlooked is the use of the default taxonomy term page. A term is a word or phrase used to describe the content in the node. By default, a term page displays when someone clicks on a term link shown on a node. The page provides a list of nodes tagged with that term. 

Let’s see how this default feature might be used to create landing pages by changing our focus from Events to types of content.

How

Imagine that you have three types of content that will be placed in a body field: How-to Lessons, News, and Blogs. Instead of creating three separate content type forms, you add a field that assigns terms to the content, declaring it a How-to Lesson, for instance.

By default, the How-to Lesson term has its own landing page. In Drupal 8, the term page is a View page and can be modified to meet your display layout needs.

Let’s take this scenario one step further. It’s come to your attention that you need a banner image and introduction text to appear above the list of nodes tagged as How-to Lesson. In this scenario, you can add an image field to the term and use the description field for your introduction text.

The results are very similar to what we have created in the previous scenarios: a page title, and image, some text, and a list of nodes. Place the page URL on the main menu and you have a landing page. 

Hopefully, this demonstrates the need to think about your processes before choosing a configuration strategy. There are several steps involved but it’s actually quite easy to learn how to do in a Drupal training class.

Why

Websites can be complex and that might mean multiple content types. However, imagine that one of your staff is blogging the latest insight on gardening strategies and it morphs into a how-to lesson. If they created the blog post in the Blog content type, they would need to move that content to the How-to Lesson content type instead. 

If this is something that might happen, create one content type for narrative content and use terms to distinguish between them. If you do, you can then take advantage of the term’s default pages, as demonstrated in this example.

Panel Page

So far, our examples assumed simple displays. What if you want to create a landing page whose content is built solely from blocks. Basic text blocks. View blocks. Blocks from other modules. Again, there are several ways to make this happen, especially if your theme (that bundle of code that controls the look and layout of your site) has the appropriate regions to organize your blocks in the way you need.

For now, let’s assume you need something unique.

How

Panels is a module that you can add to Drupal. It provides a graphic user interface (GUI) and allows you to create a page with its own URL that can be assigned to the main menu. Remember, if you need a page in Drupal, it has to come from something that can have its own URL. You can also create a custom layout to display blocks.

The process to complete this task is too complicated to step through here, but it can be learned in a Drupal training class.

Why

Some will say that you should create the theme regions you need versus using Panels, and they would have a valid point. However, if by now you are intrigued with the build process and are wondering if you might be able to do it yourself, then a tool such as Panels doesn’t require you to know how to customize a theme. 

Of course, with training, a custom theme is something you can manage. In fact, let’s consider one way of using a custom theme to create a page on your site.

Custom Theme Page

Let’s take a moment to consider the Drupal theme. Without going into all the details of theme development, at a minimum, you need to know that the theme defines the regions (header, navigation, sidebars, content, footer, and more) used to organize and display blocks. It also manages the templates used to say what gets rendered in the region.

For example, there is a page template. This renders the region if there is a block assigned to show in said region. You can add as many regions you want in order to accommodate the various block layouts you need.

You can also create a template for a single page. Let’s consider this strategy for a moment. 

How

Assume that you created a node using the Basic Page content type and titled it Resources. In the theme, you create a template specific to this node. At this point, it’s all about hand coding. You create a template that renders all the blocks you have created to display on this page. Then, with some CSS, you style the blocks in a layout of your choosing.

With the Resources node assigned to the main navigation menu,  you have the page you need because its custom template is hard coded.

Why

To be honest, although this blogger has seen this approach used, it is not conducive to making quick changes to the page. Why is it listed as an option? Because, depending on who you hire to create your site, you might end up with a vendor that uses this technique. Be it on purpose to gain maintenance business from you or just from lack of Drupal building experience, you could end up with a site that does not take advantage of Drupal’s flexibility.

Make sure you are specific in your requirements regarding the use of custom code if this is a concern.

Planning and Promet

The five options conveyed here are not the only options you have available. Moving forward, consider taking an active role in the development strategies chosen to create your site to ensure you receive a solution you can manage. 

Remember to build in time in your schedule to have development strategies discussed before they are implemented. If your developer is reluctant to let you in on their plans for meeting your requirements, they might not be the vendor for you. 

If you still have questions, check out Drupal 8 Makes it Easier and The Path to Migration to learn more about your options and considerations for your project.

Promet offers a unique planning engagement that we call our Architecture Workshop. This workshop is a customized engagement that engages all of your stakeholders in the Discovery Process. We do a 3-5 days of intensive onsite exercises with stakeholders (for your busy C-level folks we customize the agenda to bring them in where they are needed during this onsite). Then the team goes away and produces a set of deliverables that includes a full-field level Architecture Blueprint of the website(s). Whether you choose to use a waterfall or agile development methodologies - you have everything you need to build the website everyone has agreed upon. 

Not building your site and stressed out about getting an accurate quote? Investing in this kind of Workshop will make sure that you get the right Partner, and the best price.

For more planning information email [email protected].

Dec 19 2018
Dec 19

Have you ever tried logging in or registering to a website and you were asked to identify some distorted numbers and letters and type it into the provided box? That is the CAPTCHA system.

The CAPTCHA helps to verify whether your site's visitor is an actual human being or a robot. Not a robot like you see in the Terminator movie but an automated software to generate undesired electronic messages (or content). In short, CAPTCHA protects you from SPAM.
 

Distorted texts and numbers, for example, could not be recognized by bots so by providing this we are sure that only a human can log in or register.


This works! But there are some downfalls to this. For one, it's not user-friendly to visitors who are visually impaired. Reading distorted numbers and letters can be annoying to regular users, how much more to a user with a visual disability. The last thing we want from our visitors' is form abandonment, that is, leaving without even the chance to enter.
 

The solution? reCAPTCHA!
 

Drupal's reCAPTCHA module uses the Google reCAPTCHA to improve the CAPTCHA system. The reCAPTCHA module is a very efficient addon to the original CAPTCHA module.

With reCAPTCHA, we have the choice to provide a simple checkbox that asks our users if they are a robot or not. this is so much easier than asking our users to read distorted characters. We can also provide several random images and ask our users to check a specific image. This kind of test could not be passed by a robot, but we humans can!

Why trouble with bots? You may ask. The CAPTCHA system provides security, including but not limited to:

                -  Preventing Comment Spam in Blogs.
                -  Protecting Website Registration.
                -  Protecting Email Addresses From Scrapers.
                -  Online Polls.
                -  Preventing Dictionary Attacks.
                -  Search Engine Bots
                -  Worms (malware computer program) and SPAMs (undesired messages/content).

So how do we set up reCAPTCHA for our forms? Read along for an easy and detailed guide in setting up reCAPTCHA for your forms. this tutorial provides screenshots of every of every step of the way.
 

Install
 

Download and install CAPTCHA and reCAPTCHA module.

Using your favorite installation mode the Drupal UI, copy/paste from drupal.org, Drush, or Composer. Just remember that to use reCAPTCHA, you need the CAPTCHA module.

If your site is set using the PHP dependency manager called composer (like we do at Promet Source), add reCAPTCHA and the CAPTCHA module will be added automatically as dependencies:

$ composer require drupal/recaptcha


 

Enable
 

With Drush, you can enable the reCAPTCHA module by running the command in your terminal.

$ drush en recaptcha

Drush is fantastic to interact with Drupal and work faster. Learn more: Drush Made Simple).

You can also enable the module in the UI at "/admin/modules".

Search for Recaptcha, Click the checkbox and click 'install'.
 

Enabled reCAPTCHA module


Configure
 

Go to "admin/config" and choose CAPTCHA module settings.
 

CAPTCHA module settings


In the form protection default challenge type drop-down, choose reCAPTCHA from module reCAPTCHA. Don't forget to click 'Save configuration'.
 

CAPTCHA settings


After saving, click the reCAPTCHA tab.
You will be asked for the 'Site key' and 'Secret key'.
Click on the link Register for the reCAPTCHA, you will then be automatically redirected to Google.

Register your website for reCAPTCHA

Write your domain name in 'domains'.
 

A screenshot of the form where the site has to be registered for reCAPTCHA


You will be provided with the site key and secret key. Go back to "admin/config/people/captcha/recaptcha" and fill up the "Site key" in the general settings.

Click save.
 

CAPTCHA keys

Then go to CAPTCHA Points.

Choose which form you would like to use your reCAPTCHA.

TEST!!

To test, simply open your website and try visiting the form where you enabled the reCAPTCHA.

In this tutorial, the form that I choose to use reCAPTCHA is the login form.

reCAPTCHA displayed in a login page

Additional step: For local testing ONLY

If you want to do the above steps in your local environment, you have to disable the domain name validation in your reCAPTCHA configuration in google.com

Click the Advance settings and disable the domain name validation.
 

CAPTCHA for local testing


Don't forget to test by accessing your form in an incognito browser.

And there you have it, reCAPTCHA configured! Your Drupal 8 project is now protected by Google's reCAPTCHA system.

Say no to bots, yes to human...

Questions?
Drop them in the comments section below this article :)

Special thanks to Luc Bezier for contributing to this post before publication.

 

Nov 15 2018
Nov 15

Did someone test your website for accessibility conformance without your knowledge and then inform you that your organization is prime for an accessibility lawsuit? Are they offering to help you fix the issues found on your website? 

That notification and offer might be valid, but it also might not be the entire picture. One free test grade might not reflect how your site is doing in all its accessibility subjects because automated testing tools can't find all the problems. We believe in assessing all topics of accessibility before recommending a sit down to discuss your options on how to proceed.

How do we do it? 

We don't rely on automated testing to reveal the true nature of a website's issues. We manually test it as well. We look at what makes your website unique and try to understand its mission before creating a scorecard you can use in your decision-making process.

This card reflects several perspectives including the issues anyone with an automated testing tool can see, including you. Many are free to use and quite robust in their feedback. Give one a try. For example, Code Sniffer.

But don't stop there. Our scorecard also reflects a sample of other accessibility issues not seen by the tool.

Last but not least, we look at how you are delivering your website. This part of the review is critical to understanding whether fixing or rebuilding the site is going to be your most cost-effective solution.

Website Grade

Just like the report card you got as a kid, we use grades to convey the accuracy and quality of your work, or in this case, your website. As you can see below, there are degrees of quality: A through D. No F, for failure. We assume no site is that bad.

A – Accessible & modern platform, main issues residing solely in the content
B – Accessible & modern platform, but issues with template items such as menus, sidebars, and in-line styling
C – Accessible & modern platform, but many features need to be replaced or reworked to achieve compliance
D – Antiquated platform, non-responsive, easier to rebuild vs. fix

The Scorecard is not intended to act as a thorough report or formal recommendation, simply a high-level overview. It's our tool to facilitate a conversation with you and help you choose the best path to remediation.

For example, we might find that you are using a content management system tuned to meet the accessibility criterion, but your content developers aren't using appropriate techniques when posting. Fixing existing content issues without “fixing” the reason the issues exist just means your site will continue to have problems.

Or, the example could be far worse. We hate to say it in this day of accessibility lawsuits, but there are still platforms out there that don't follow the rules. If your site was created using an antiquated approach, it might be more cost effective to rebuild rather than create workarounds in your current system.

Our Passion

Here at Promet Source, we are passionate about accessibility. We offer an array of services and remediation options that can be shaped to fit your needs. But, be warned, we are not a quick fix/band-aid company. We believe in enabling you to move forward knowing that you have a fully accessible site and the means to keep it accessible.
 
The decision process associated with such an undertaking can feel overwhelming. That's why we offer the scorecard as part of your remediation process. It's your tool to use in helping others in your organization to understand the level of effort you are facing by moving forward. 

We find that when all stakeholders have an understanding and are vested in doing the right thing, the future of a website is easier to envision. 

We look forward to talking to you about that phone call you got by surprise or that unsolicited email full of ill tidings. Don't worry, we can help you understand and make informed decisions.
 

Nov 15 2018
Nov 15

Did someone test your website for accessibility conformance without your knowledge and then inform you that your organization is prime for an accessibility lawsuit? Are they offering to help you fix the issues found on your website? 

That notification and offer might be valid, but it also might not be the entire picture. One free test grade might not reflect how your site is doing in all its accessibility subjects because automated testing tools can't find all the problems. We believe in assessing all topics of accessibility before recommending a sit down to discuss your options on how to proceed.

How do we do it? 

We don't rely on automated testing to reveal the true nature of a website's issues. We manually test it as well. We look at what makes your website unique and try to understand its mission before creating a scorecard you can use in your decision-making process.

This card reflects several perspectives including the issues anyone with an automated testing tool can see, including you. Many are free to use and quite robust in their feedback. Give one a try. For example, Code Sniffer.

But don't stop there. Our scorecard also reflects a sample of other accessibility issues not seen by the tool.

Last but not least, we look at how you are delivering your website. This part of the review is critical to understanding whether fixing or rebuilding the site is going to be your most cost-effective solution.

Website Grade

Just like the report card you got as a kid, we use grades to convey the accuracy and quality of your work, or in this case, your website. As you can see below, there are degrees of quality: A through D. No F, for failure. We assume no site is that bad.

A – Responsive & modern platform, main issues residing solely in the content
B – Responsive & modern platform, but issues with template items such as menus, sidebars, and in-line styling
C – Responsive & modern platform, but many features need to be replaced or reworked to achieve compliance
D – Antiquated platform, non-responsive, easier to rebuild vs. fix

The Scorecard is not intended to act as a thorough report or formal recommendation, simply a high-level overview. It's our tool to facilitate a conversation with you and help you choose the best path to remediation.

For example, we might find that you are using a content management system tuned to meet the accessibility criterion, but your content developers aren't using appropriate techniques when posting. Fixing existing content issues without “fixing” the reason the issues exist just means your site will continue to have problems.

Or, the example could be far worse. We hate to say it in this day of accessibility lawsuits, but there are still platforms out there that don't follow the rules. If your site was created using an antiquated approach, it might be more cost effective to rebuild rather than create workarounds in your current system.

Our Passion

Here at Promet Source, we are passionate about accessibility. We offer an array of services and remediation options that can be shaped to fit your needs. But, be warned, we are not a quick fix/band-aid company. We believe in enabling you to move forward knowing that you have a fully accessible site and the means to keep it accessible.
 
The decision process associated with such an undertaking can feel overwhelming. That's why we offer the scorecard as part of your remediation process. It's your tool to use in helping others in your organization to understand the level of effort you are facing by moving forward. 

We find that when all stakeholders have an understanding and are vested in doing the right thing, the future of a website is easier to envision. 

We look forward to talking to you about that phone call you got by surprise or that unsolicited email full of ill tidings. Don't worry, we can help you understand and make informed decisions.

Email us for help!
 

Nov 13 2018
Nov 13

Partnership combines comprehensive UI design, UX, and digital strategy, with web development proficiency, to produce a holistic experience for clients.

Chicago, Illinois — November 13, 2018 — In September 2018, Promet Source acquired DAHU Agency, a strategy-focused, user experience and design agency that enhances the services offered to its clients. By expanding their services in UX and UI, and bringing new offerings in-house for digital strategy, WordPress development, messaging, and branding –  Promet aims to better serve their clients evolving needs as marketing and web technologies continue to converge and the need to provide functional, dynamic websites increases.

 

In his vision for Promet to be a strong digital agency focused on creating great user experiences through meaningful web applications, Andy Kurcharski, President of Promet, seeks to accelerate growth and innovation by providing comprehensive digital services to his clients.  Andy has more than 20 years of technical leadership experience from startups to Fortune 50 firms with industry experience in banking, telecommunications, government, and association technology management. Andy’s e-commerce experience dates to 1998 with the implementation of highly scalable enterprise solutions.

 

“In today’s technology landscape, we are seeing that our clients and their customers expect more from their websites” Kurcharski expressed. “Our addition of a new team to our existing core of web developers will help us to proactively approach new websites with a holistic mindset combining our technology expertise with great design and function to ultimately increase client success online.”

 

DAHU Agency, based in Dallas, Texas, not only provides Promet with an office central to service their clients in the Southwest region but also brings expertise in design and digital strategy to help optimize user experience within an organization’s website.

 

Mindy League, CEO, and founder of DAHU Agency offers a highly thoughtful and adaptive approach to constantly evolving technologies and user behaviors. Her experience in building solutions for clients such as HP, Emerson, IBM, and Home Depot, contribute to a depth of perspective into the challenges and opportunities faced by top global brands. Mindy will join Promet as the Director of User Experience and Design.

 

DAHU’s distinct approach to engaging with clients has been described as “radical empathy” and it is this philosophy and mindset that complements Promet’s dedication to delivering groundbreaking results to their clients. Whether examining the impact of corporate strategies on customers and the broader enterprise or developing products, Promet aims to step into their clients’ businesses with a fervent dedication to excellent experiences and high-impact results.

 

Click here for full press release. 


 

Nov 01 2018
Nov 01

Your company brand encompasses the entire perception of your organization through the eyes of your customers, clients, and employees. Branding consists of more than just your logo and typeface selections; it is how the public (usually users and/or customers) experiences your business. How you position your brand can certainly define the customers’ experience of your organization. However, consider first planning great experiences for your users and customers in order to develop a more customer-centric brand identity. Changing to this strategy requires a solid understanding of your users and customers as well as a thoroughly considered mission statement prior to developing your brand.

UNDERSTAND YOUR USERS AND CUSTOMERS

Knowing who your business is intended to cater to will help you to plan all the touchpoints your customers and clients will have with you, from the in-person experience to the web and social media experience to even the look and feel of business cards you hand out. For example, if your target audience consists of Millennials, your language and messaging would be different than if it consisted of top-level executives and managers. User experience research techniques can be used to help define different customer/client personas. These personas can be used essentially as avatars for your customer base. As new services or features are developed, keep these personas in mind to ensure that these new offerings align with their needs and desires. At times, new personas might replace or get added to the list.

RELY ON YOUR MISSION STATEMENT

Your mission statement defines the core purpose of your business. There’s a delicate balance required between keeping it broad enough to encompass your long term vision, yet narrow enough to define your identity for both your employees and your customers. A good mission statement represents what you stand for in specific, actionable ways. It paves the way for how your employees interact with your customers. The length of your mission statement may range from a sentence or two to several paragraphs, a good rule of thumb would be to keep it as succinct as possible in order to avoid providing too narrow a focus and thus reducing strategic flexibility. Also, keep in mind that your mission statement can evolve over time to adjust for the market, your competitors, and your customer’s needs and desires.

DESIGN YOUR USER AND CUSTOMER EXPERIENCES

The broad definition of User and Customer Experience includes how your customers interact with all facets of your business. Rely on your mission statement and understanding of your customers to help define how you want those interactions to occur instead of leaving it to chance and risking a negative experience. For instance, if you wish to present your organization as caring and supportive to your user base, friendlier language and a welcoming user interface on your website or software would communicate your caring and empathic intent.

User and Customer Experience is about setting and meeting the users’ expectations through clarity of messaging and purpose. Keeping the customer experiences in mind at all times when developing your business processes will help ensure that your customers stay positively engaged with your organization.

By tailoring your business strategies around your customers’ expectations and the driving force behind your mission statement, you can create specific user and customer experiences.  These experiences reinforce their expectations and your mission statement, creating a sustainable, healthy feedback loop. For example, McDonalds recently responded to customer requests by running focus groups to test the viability of providing all-day breakfast service to their fans. Before simply agreeing to these requests (the first of which were posted in 2007!), McDonalds tested the viability of the service through focus group and user testing in small markets in order to ensure that the service could be provided within customer expectations. This is a great example of using feedback and relying on thorough user and customer research to improve brand perception through ensuring consistent customer experience, even for new offerings.1

By leveraging this valuable feedback loop to guide the underlying framework of your business decisions, you can ensure that your organization adjusts to changing expectations and trends, keeping your brand fresh and relevant for as long as possible – while keeping your customers engaged.

1The Story of How McDonald’s All-Day Breakfast Came to Be

 

 

Oct 20 2018
Oct 20

The most common way to post content on a web page is via HTML text, images, audio, and video. No matter your approach to content delivery, you probably know that your approach needs to be accessible. Did you know that non-web content such as Adobe PDF documents needs to be accessible as well?

Is your restaurant menu downloadable? Do you post your meeting agendas? What about event brochures or product catalogs? PDF files are great for such purposes and need to be accessible.

Did you know that the rules you follow to create accessible HTML content, also apply to non-web content such as Word and PDF files? You might be wondering how one makes non-web files like PDFs accessible. That’s where the Web Content Accessibility Guidelines (WCAG) comes into play. Of course, not all will apply such as Bypass Blocks and Captions for video but the WCAG criterion will be your guide. 

Let’s consider some of the guidelines that will apply to non-web documents.

Applicable WCAG Criterion

When creating documents, you need to cover the basics. 

  • Declare the document’s language.
  • Include a title for your document
  • Use Header styles instead of manually bolding a header or changing its font size
  • Ensure that said headers are orderly, that you don’t jump from header 2 to header 4, for instance
  • Include a brief description of your images via alternative text 
  • Ensure color contrast ratios are met
  • Identify the meaning of shapes and icons that you might use
  • Declare header row in any data tables you create
  • Resist the urge to use tables to manage your content layout
  • Ensure that embedded links have a clear purpose (no “Click here” links)
  • Remember not to leave inline bookmarks hanging without its partner link

The more complicated the PDF, such as those with forms, you will need to meet another criterion.  However, for your basic content document, hopefully, you are thinking that this list doesn’t sound too bad. If not, you have help. If you miss something while creating your PDF, Adobe Acrobat has an accessibility testing tool that will remind you to check things it can’t, tell you if it sees something wrong, and will give you help to fix the issues.

But, let’s not get ahead of ourselves. The first step in the process of creating the accessible PDFs.

Create a Source File

Microsoft Office, Corel, Google, and Adobe are just a sampling of product vendors whose applications can create PDF files after its user has created a source file. Perhaps you are using one of these or some other application. As long as your source file can be made to accommodate the requirements listed above before you export a PDF, then you are well on your way to creating an accessible document.

Save As or Export a PDF

If you create an MS Word document, for example, the process is to save as a PDF. If you create an InDesign document, the process is to export. Whatever the vernacular, convert your source file into a PDF.  

Convert does not mean print to PDF, nor does it mean scan to PDF. Both of these options create an image of the text. That means assistive technology cannot see the text. 

Sadly, not all conversion processes work perfectly. That means testing and repair is required.

Test and Touch up the PDF

Even if you have a simple Word document with sections and subsections divided by headers, you can still run into issues once the file has been converted to PDF. Use the accessibility testing tool in Adobe Acrobat to check for hidden issues. 

For instance, by default, the Acrobat accessibility test result will likely tell you to check your color contrast - assuming you are using color in your document. It might also say you don’t have a title when you do. FYI, the title being requested is part of the document’s metadata. Lastly, it will likely ask you to check the logical reading order of your content. 

You might think that checking the logical reading order can be ignored. You created a document whose content is presented in a logical order. How could it have possibly changed? Just to be sure, you scroll through the PDF and see that all is well. 

Logical reading order isn’t about what you see, it’s about the order assistive technology will read the content. So, be sure to click on Reading Order in the Accessibility options in Acrobat. Make sure that the numbers assigned to each item on the page convey the actual order. You would be surprised how often the reading order differs from what you see.

There could be other issues the test reveals. Don’t worry about not knowing how to fix all the issues it finds. Acrobat provides links to short tutorials that explain how to remedy an accessibility problem it has found. 

However, before you fix something in the PDF, make sure it was formatted correctly in the source of the source file. It if is not, fix it there and convert again.

Conclusion

If you have a choice between placing content on your site via a PDF versus HTML text, consider the HTML text first. HTML text is more accessible than a file that has to be downloaded. Plus it is easier to format HTML text and images to be accessible.

If faced with a multi-page source file that can’t easily be ported into HTML text, then plan ahead. Allow time to inspect your PDF’s reading order and remedy any accessibility issues before you put it online.

Not sure you have a problem? Email our Accessibility Experts - they can evaluate your site, and provide you with an Accessibility Scorecard. If you know your documents are a problem, we can estimate the cost of remediating those documents. 

Oct 18 2018
Oct 18

A web page in Drupal is made up of several parts. For instance, you have the header and navigation that appears on each page. You have the main content region that holds your articles or the details associated with your events. On either side of the content, you might have sidebars with blocks suggesting related content or a call to action. 

Typically, each part of the page is created or managed by different members of your website team. The developers that originally created your site will have set up your header and menu, for example. You might have a trained IT member of your team tasked to create and place blocks in the sidebars as needed. Then, when a content author publishes an article, those blocks appear as planned on the article.

A setup like this taxes your IT team and limits your content authors. Let’s explore how content types, fields, and views can empower your authors to influence the block that appears in the sidebars from article to article.

Planning Your Blocks

A simple exercise in the planning process is to ask the question, when X-type of content is published, what blocks should also appear? Traditionally, this would mean a fixed set of blocks configured to be visible on that content type or based on the URL alias.

But, what if you need a more granular approach to creating and enabling blocks? What if you wanted your content author to create and enable blocks without having to train them to be a Drupal builder?

Let’s explore an example scenario where you list all the blocks you might need from one article post to another:

  • More like this
  • Related training
  • Call to action
  • Archive
  • Guest speakers

A few of these blocks can be set up during development to activate automatically. For example, if the article is tagged as a container garden, then other articles tagged as such will appear in a "More Like This" block. But what about Calls to Action? Let’s take a closer look at those blocks that can’t be predicted with ease.

Related Training

You could design a Related Training block much like the More Like This block where training events would be listed in the block just because they have been tagged with the same term. 

What if the content is a how-to piece giving a sneak preview to one of the more simpler tasks that will be taught in a series of training events? In this scenario, the author wants to control which event to advertise, but she doesn’t want to include that advertisement in her narrative.

So, in the narrative content type, you add a field that allows the author to reference the training event nodes that are directly associated with the content of the how-to lesson. Following the same concept as in the previous example, you hide the event reference field and print it via a Views block. The block appears in a predestined spot on the page.

With this approach, with some planning, the block can be configured to include a thumbnail image taken from the events in question along with date and time information, making it more than a list of the titles that appear in the reference field.

Call to Action

Your content author has created an article about a new technology that will be presented at the conference. You are not presenting a session, but you will be hosting a networking event for attendees who want to extend their conference experience and meeting others in the field. The article is not the event. There’s an event node in another section of the site.

You want a Call to Action block to appear with this article, giving site visitors a link to sign up for the networking session. The common practice would be to create an advertising block and then place that block to be visible for this specific article.

Another strategy would be to add a field set to the content type you use for your narratives such as blogs, news, and how-to lessons. You would add an image field, a text field, a link field, and an on/off field. They would not be set to show. Instead, a contextual view block would be created, one on the lookout for someone to fill in the call-to-action fields and turn it on.

The Call to Action block will show up at the author’s discretion in a place on the page decided by the User Experience designer during the planning phase of your website development project.

Archive

Drupal 8 ships with a predefined View called Archive. It provides a block that lists months and includes a number representing how many nodes were published in that month. By default, all nodes are included but that doesn’t mean you can’t add filters to limit what gets included in the count.

Not all narrative content will be enhanced by including an Archive block, therefore having it enabled by default, could take up screen space needed for other more useful blocks. So, how does a content author turn this block on and off as needed? 

First, identify the scenarios where your users would benefit from being able to find previous narratives in common with the one they are viewing.  Then, using the same strategy applied for the Call to Action block, add an on/off field for the Archive block. Edit the Archive View to look for this field to be set to on.

This scenario and the previous one will depend on your trust in the author to know when to turn on Call to Action and/or Archive. That’s where business rules come into play and ensuring all know how to follow them. 

Guest Speakers

This time, your content author is creating an event with multiple guest speakers. You have decided that creating a speaker page for every guest could amount to many nodes that aren’t worth maintaining. Instead, you want to link to the speaker’s own website.

Of course, you could make this information available is a list of links as part of the event, but given all the data you are already including, it’s been decided that highlighting the speakers in their own blocks is a better option.

Using the same strategy enabled in the Call to Action scenario, you create a set of fields: image, text, link, on/off. This time, however, you need the ability to have multiple speakers so you need this set of fields to repeat. There is a module called Paragraphs that will be your friend in this example.

Paragraphs allow you to create a set of fields that can be repeated on the page. Instead of including them in the display, you use a View to show the information in a block.

Performance

You might be starting to wonder about the performance of your site with all these queries on the database. And, you would be right to be concerned if you had no caching plan in place. Outside of Drupal, you have caching tools such as Varnish that can help deliver your pages quickly.

Have a Plan

When it comes to Drupal, using your imagination is key to empowering your content authors. Start by mapping your processes. Ask yourself what has to be available in order to execute the process differently.

Remember, you don’t have to teach your content authors how to create and place blocks. You can plan ahead and give them simple options within the environment they will already be working. Assuming default processes are your only option can frustrate your users.

Need Help?

Promet offers best practice Training to help give your team the know-how to be prepared for these scenarios. Want to run scenarios like this by our experts to get advice on pages, or even plan a new website from the ground up? Promet is happy to create small and large planning exercises for you and your team to get the most out of your Drupal site.

Oct 15 2018
Oct 15

If someone sues you because your website has accessibility issues, it usually means they need you to fix said issues. Sadly, there will be those lawsuits where the complaint is trigger more by the desire of monetary compensation from a settlement than the present accessibility issues, but in either scenario, there has to be grounds for the complaint which means something needs remediation on your site. 

Why are we stating the obvious? Because it's not obvious to all who find themselves with a letter or lawsuit claiming that their website is inaccessible and therefore discriminates against individuals with vision, hearing, and/or physical disabilities under ADA Title III.

Defenses against inaccessibility claims that have been seen in the news include:

  • Websites aren’t included under ADA Title III
  • Even if they are, it’s moot in this case

ADA Title III Defense?

On October 31, 2017, a letter was sent to The Honorable Jeff Sessions, Attorney General, United States Department of Justice, and signed by sixty-one Members of Congress, urging the DOJ “to restart the process of issuing regulatory guidance regarding the Internet under Title III of the ADA.”1

Restart? Yes. 

In this same letter, the sixty-one Members of Congress reminds the Attorney General that the DOJ, in their 2010 ANPR, states “Although [DOJ] has been clear that the ADA applies to websites of private entities that meet the definition of ‘public accommodations,’ inconsistent court decisions, differing standards for determining Web accessibility, and repeated calls for [DOJ] action indicate remaining uncertainty regarding the applicability of the ADA to websites of entities” included in Title III. 

Unfortunately, the 2010 Advance Notice of Proposed Rulemaking2 where “the Department encourages small entities to provide cost data on the potential economic impact of adopting a specific requirement for website accessibility and recommendations on less burdensome alternatives, with cost information,” has been given a status of inactive under Trump’s Unified Regulatory Agenda released in July 2017.3 

On July 19, 2018, another letter was sent to the The Honorable Jefferson B. Sessions, III by the Attorneys General of 18 states and the District of Columbia on the same topic sent by the Members of Congress.4

If the DOJ recognizes that Title III is unclear, is it no wonder that site owners still try to claim that websites aren't included in Title III? No. 

However, as you read about website accessibility cases in the news, it’s clear that the courts have decided that it does. Whether it was the Winn Dixie case in June of 20175 that set the precedence or that the plaintiff in this case has brought other similar suits since then, it doesn’t matter. Compliance with the World Wide Web Consortium’s Web Content Accessibility Guidelines (WCAG), level AA is here to stay. Whether its WCAG version 2.0 or the recent 2.1, courts are ruling that these guidelines must be met.

So, what other defense can a business make to stop a website accessibility lawsuit? Other than remediating the problem?

Moot Defense?

If you aren’t a lawyer, you might be scratching your head right now. Moot? Don’t worry, you’re not the only one. Let’s start with a simple example.

Carroll v. New People's Bank, Inc.6

Filed in November, 2017 and terminated in April, 2018. First, please note the length of time required to adjudicate this case, only to have it dismissed. Here is a brief look at what transpired.

  • “NPB's website contains accessibility barriers, which Carroll alleges prevent him from using screen reading software to freely navigate the site.”
  • “NPB informed Carroll of its intent to develop a new website by letter in November 2017, prior to the filing of his lawsuit. In this letter, NPB stated that they had "voluntarily made a number of improvements" to the website and had "retained a third-party to develop a new website for the bank which [would] further improve [the website's] accessibility and client service feature-set."”
  • “Carroll argues that this new website does not render his claim moot because there is no guarantee that NPB will not revert to its former inaccessible website in the future.” 
  • “NPB has moved to dismiss the Complaint for lack of standing.”
  • “NPB contends that, in any event, Carroll's claim is now moot based on its voluntary upgrades made to the website after this action was filed, which upgrades Carroll does not dispute.”

Obviously, there’s more to this case than the snippets provided here. In fact, the case is interesting reading. Bottomline, NPB responded to Carrol’s letter, fixed the site, and the case was dismissed.

Haynes v. Hooters of America, LLC7

This next case isn’t as straightforward as Carroll’s claim being moot. This one is about getting sued twice for the same issue. Here is brief look at the ruling.

  • “On April 4, 2017, Haynes sued Hooters in the United States District Court for the Southern District of Florida …” In short, Haynes wanted Hooters to fix the accessibility issues on their site.
  • “Prior to the initiation of Haynes’ suit, on August 22, 2016, a different plaintiff filed a separate and nearly identical website-inaccessibility lawsuit against Hooters. Less than three weeks after the filing of that suit, the parties reached an agreement and settled their dispute (“Gomez Settlement Agreement”) ...”
  • “Hooters moved to dismiss Haynes’ suit, arguing that, because Hooters was in the process of actively implementing a remediation plan for its website, pursuant to the Gomez Settlement Agreement, there was no live case or controversy and Haynes’ claim must be dismissed on the mootness grounds.” They had until September 2018 to fix their site.
  • The district court agreed with Hooters and dismissed the case.
  • But, Haynes didn’t agree, and neither did the Eleventh Circuit in their June, 2018 ruling that “the case is not moot.” 

Again, there is more to this case that is briefly summarized here. In short, Haynes had no way to know or to ensure that the remedies being planned would resolve the issues he was having with the site. Therefore, his claim was valid. Yes, you can get sued twice for the same thing if the issue is still present on your site. 

Lessons Learned

There are four lessons worth mentioning. 

Audit Your Site Before You Get Sued

There is no argument that it’s going to cost you money to have your site audited appropriately for accessibility issues and ultimately remediated if problems exist. You could wait to see if you get caught but at that point, your costs include legal fees plus the audit and remediation.

Other costs include the negative publicity that can ensue. Web accessibility cases are hot topics and will remain so due to the lack of specific ADA regulations from the DOJ. People want to know how courts are ruling and that means numerous blog posts and speculation where your business’ name is spattered over the Internet.

Website Accessibility Insurance

Insure your site. You heard right. Insurance. You have a site right now. You think all is well. You have processes in place that audit content as it goes live to ensure there aren’t any issues. You have run an automated tool on sample pages and everything looks okay.

However, as a person that drives a car or owns a home knows, you can never predict when something is going to go wrong. That’s why you have insurance.

Don’t believe that such insurance exists? Think again. Beazley Insurance is working with Promet Source to offer insurance against ADA website compliance claims. Said policy includes up to $25,000 coverage for an accessibility audit and remediation if someone files a claim against you.

“In 2017, 7,663 ADA Title III lawsuits were filed in federal court — 1,062 more than in 2016.”8 “If ADA Title III federal lawsuit numbers continue to be filed at the current pace, 2018’s total will exceed 2017 by 30%, fueled largely by website accessibility lawsuit continued growth.”9 Add to these numbers the cases brought in state courts and it’s not hard to believe that you could get sued in the near future.

Move Quickly

If you get a letter, move quickly to remediate those items specifically noted. In the case of Carroll v. New People’s Bank, even if Carroll could prove standing, in the long run, NPB responded quickly and fixed the issues in the letter. 

Has Hooters moved quickly? How much money do you think Hooters could have saved in legal fees by taking down their inaccessible website and quickly replacing it with a simple, accessible website until their new site could be designed, developed, and launched? You decide.

Quick Might Not Be Fast Enough

It’s clear that people with disabilities are no longer hesitating to file suit for an inaccessible website. Whether they have standing or not, you could be faced with one lawsuit after another until you can audit your site and remediate it accordingly. And, given the findings in Haynes v. Hooters of America, LLC, the courts might let each lawsuit stand. So, circling back to the first lesson, have your site audited using automated and manual testing, get it fixed if issues are found.

Conclusion

Until the DOJ responds to the pleas of lawmakers across the nation to create specific regulations regarding website accessibility, courts will continue to review other cases to determine what’s moot or not. Don’t wait to find out. Get audited. Fix the issues.

If you don’t know what to do, Promet’s Accessibility Audit, Remediation, and Training Roadmap will help you end a current lawsuit and prevent any future lawsuits.
 

Footnotes

1. https://www.cuna.org/uploadedFiles/Advocacy/Priorities/Removing_Barriers_Blog/ADA%20DOJ%20ES-RD%20Letter%20-%20FINAL.pdf
2. https://www.ada.gov/anprm2010/equipment_anprm_2010.htm
3. https://www.reginfo.gov/public/do/eAgendaMain
4. https://www.cuna.org/uploadedFiles/Advocacy/ADAAGLetter71918.pdf
5. https://www.adatitleiii.com/tag/winn-dixie/
6. https://casetext.com/case/carroll-v-new-peoples-bank-inc
7. https://law.justia.com/cases/federal/appellate-courts/ca11/17-13170/17-13170-2018-06-19.html
8. https://www.adatitleiii.com/2018/02/ada-title-iii-lawsuits-increase-by-14-percent-in-2017-due-largely-to-website-access-lawsuits-physical-accessibility-legislative-reform-efforts-continue/
9. https://www.adatitleiii.com/2018/07/website-access-and-other-ada-title-iii-lawsuits-hit-record-numbers/
Sep 19 2018
Sep 19

You can’t build a website without a plan. A plan derived from requirements collected and a design created. You also need a development and testing plan that reflects the appropriate strategies for meeting said requirements and design. After you launch your website, you need a maintenance plan to ensure that your code remains secure, your content remains accessible, and your future features are integrated correctly.

Of all the development methodologies, past and present, there is not one that supports the development of software without requirements and design. When choosing a methodology, be it one based on the 12 principles listed in the Agile Manifesto, or not, you will not be able to avoid the effort of creating plans.

Agile Misunderstandings

Among the many misunderstandings regarding Agile methodologies is the aspect of planning. The belief that upfront planning isn’t needed and therefore time can be saved on a project is a misunderstanding of the iterative and incremental approach to software development. Think about it that for a moment. Can you create or build anything without some kind of plan? Be it simple or extensive?

It’s also a misunderstanding that said plans, if any, don’t need to be documented. If you choose an Agile methodology, you will quickly learn about Epics and the Backlog. Epics are large user stories while the backlog is a list of requirements derived from said user stories.

So, Agile isn’t about skipping the planning aspects of the project. It’s about changing the way the planning and development are conducted. And, the first step in the process of planning your site is gathering the appropriate players together.

The Right People

If you are going to put out a request for proposal, you need to include some of the requirements. Perhaps not all the details, but enough that a vendor who wishes to bid on your project can anticipate potential costs. Later, these initial requirements will fleshed out with the vendor whose bid you choose.

So, who needs to be in the room when you start brainstorming what you need? Who will ensure all requirements are identified? 

  • The money person would be good. They will know the budget and can remind you of the fact as the ideas start to mount.
  • The content manager is important. You will need to understand the tasks involved in creating and posting your content. For instance, how will you manage the publication of your content once it is uploaded to your site?
  • Let’s not forget the person who is in charge of your current site. This is the stakeholder who knows where the bodies are buried. They know why the current site is what it is and if certain aspects of the site can't change.
  • Other process owners. Depending on the tasks that your site will support, such as e-commerce or document download, who knows the most about how these tasks should be performed?
  • The naysayer. The squeaky wheel. Who is your Eeyore. “It will never work.” Get them in the room because you want the devil’s advocate. You want to hear what might not work and why.

Bottomline, anyone responsible for an aspect of the site, be it backend support or frontend interactions, get them in the room. You want to cover all your bases.

Agile Upfront Planning

“In 1998, Alistair Cockburn visited the Chrysler C3 project in Detroit and coined the phrase ‘A user story is a promise for a conversation.’”1 Then, in 2001, Ron Jeffries, one of the original signatories of the Agile Manifesto, proposed a ‘Three Cs’ formula for user story creation: card, conversation, confirmation, making user's stories part of the world of Agile methodologies. Coupled with use cases, Agile planning seeks to identify requirements and design before development begins.

However, as you will see, the level of requirements detail depends on several factors such that not every minute decision is made at the start. Let’s look at this idea more closely.

User Stories

User stories are typically brief statements written from the user’s perspective. For example, “As the content author, I need to be able to edit a page so that I can add a header image.” The documentation of such statements can be facilitated with index cards, Post-it notes, wireframe sketches on printer paper, or anything that meets your team’s needs.

A collection of such user stories helps to confirm the scope of the project and can reveal foundational requirements such as which framework or platform to use. Such stories also reveal relationships and thus where shared code will be used, for instance. 

At this point in the planning process, the team might decide to start developing. Such a decision is made possible by today's systems and platforms with plugin and play capabilities. They provide a way to support the user story tasks so that said tasks needn't be reinvented via a use case.

If user stories are unique and more detail is needed, creating use cases is the next step.

Use Cases

If system default tasks are not what is envisioned or additional tasks need to be supported, the team may choose to clarify the user stories via use cases - details of actions and events that define how a user interacts with the system. 

Deeper investigation into the requirements can help define a development path that supports both the overall system architecture required but also the specific tasks required of the system.

Once the stakeholders and development team have gained a common understanding of what is required, the user stories and use cases are converted into epics and the necessary backlog of development tasking.

So, Agile methodologies support the requirement and design phases listed in the Waterfall methodology, it just does it by engaging methods that have proven easier for end users to envision as they communicate what it is they want from the product being created. 

Of course, this isn’t the only time during the iterative and incremental development approach where planning takes place.

Agile Planning in Development

With epics and a backlog populated, the development team plans a series of iterative and/or incremental development efforts, commonly referred to a Sprints. The way the Sprints are defined depends on the overall development strategy required to build out the product, in this case, a website.

Before each Sprint, the existing requirements (based on user stories and use cases) are reviewed and specific strategies are chosen for meeting said requirements. This might include a conversation where details are clarified or added to use cases.

After each Sprint is complete, the product owner is asked to confirm that expectations have been met. If not, requirements and design aspects can be changed to correct misunderstandings or to acknowledge a new idea or need. In other words, additional planning is interjected into the development cycle and the project is adjusted.

In addition, lessons learned are collected and decisions are made regarding how-to strategies for the next Sprint. You might be thinking that enabling changes to the original plan might introduce scope creep. And, you would be right. It can.

Planning and Scope Creep

Scope creep is similar to what happens when you think you are buying the base model of a new car and you leave the lot having spent 20% more than planned because you decided on several add-on features. 

Several factors can influence the possibility of scope creep on a website. Let’s consider two related to planning.

  • Insufficient upfront planning. We aren’t talking about getting into the details of how features on your site are developed in this instance. Instead, it’s about ensuring that all user stories have been identified along with supporting decisions. For instance, if the user needs to be able to categorize an article, has the supporting requirements such as the information architecture been defined? 
  • Incorrect stakeholders at the planning table. The budget folks will have a different take on requirements than say an end user. Content manager will be able to enlighten decision makers on processes that are required to ensure a specific level of content quality. Without the appropriate people involved in the planning process, you might find that a Sprint doesn’t meet expectations.

Conclusion

An Agile approach to website development relies on planning to be successful, however, not all planning is required before development starts. Of course, there are risks associated with moving quickly into development, one being scope creep. 

The power of Agile methodologies isn’t about being able to skip steps that a waterfall methodology is criticized for enforcing. It’s about being flexible. It’s about being able to adjust as forgotten requirements are remembered. And, it’s about continuous feedback, ensuring what was originally thought to be a good idea, still works. 

Promet and Planning

Promet offers a unique planning engagement that we call our Architecture Workshop. This workshop is a customized engagement that engages all of your stakeholders in the Discovery Process.We do a 3-5 days of intensive onsite exercises with stakeholders (for your busy C-level folks we customize the agenda to bring them in where they are needed during this onsite). Then the team goes away and produces a set of deliverables that  includes a full-field level Architecture Blueprint of the website(s). Whether you choose to use a waterfall or agile development methodologies - you have everything you need to build the website everyone has agreed upon. 

Not building your site and stressed out about getting an accurate quote? Investing in this kind of Workshop will make sure that you get the right Partner, and the best price.

Footnotes

1 
https://en.wikipedia.org/wiki/User_story
Aug 30 2018
Aug 30

Perhaps you’ve heard that the W3C (World Wide Web Consortium) has updated their Web Content Accessibility Guidelines (WCAG) 2.0. 

  • On April 24th, 2018, W3C posted a proposed extension of Web Content Accessibility Guidelines (WCAG) 2.0, referred to as WCAG 2.1.
  • On June 5th, 2018, WCAG 2.1 was no longer considered a proposal. WCAG 2.1 includes 2.0 and 17 new criterion.

When will I need to update my website?

Is there a law someplace that answers this? An official interpretation? A lawsuit that references the new criterion?

To date, in the United States, there is an understanding that WCAG 2.0, levels A and AA, is the required version and levels of accessibility required to create an ADA compliant website. Court case summaries posted by the legal community say this is so.

But, as of August 2018, this reviewer can’t find a court case that references WCAG 2.1. 

Should you sigh in relief? No. Right now, the courts are interpreting Titles II and III and hearing complaints. Will a judge bring his or her hammer down on one of the new criterion if you aren’t compliant with it? Quite possible. One would hope for a reasonable ruling: no penalties and perhaps a date allowing you time to fix the issue given the newness of the additional criterion.

As soon as this happens, you have your precedence. You have your clock. Of course, until Section 508 is updated, federal site owners are protected, but that doesn’t mean said site owners should ignore the new criterion as they update or rebuild their sites.

What kind of changes will we see?

WCAG 2.1, according to https://www.w3.org/TR/WCAG21/, “was initiated with the goal to improve accessibility guidance for three major groups: users with cognitive or learning disabilities, users with low vision, and users with disabilities on mobile devices.”

The fact that these new criterion were added with mobile devices and users in mind should not come as a surprise. In 2015, the W3C released Mobile Accessibility: How WCAG 2.0 and Other W3C/WAI Guidelines Apply to Mobile. They’ve been working accessibility for mobile devices for some time. 

Are we talking about a lot of change?

Depends on what you are doing on your site. It’s possible you have nothing to do or change in order to meet one or more of the 17 additional criterion. Perhaps you are hoping that most of the 17 criterion are level AAA and you won’t be held accountable. Let’s clear this one up right now. Twelve of the 17 are A or AA.

At this point, we could simply list the new criterion by the principles of POUR (Perceivable, Operable, Understandable, Robust) or by level, leaving you to mentally map the criterion to how you think about your site and its functionality.

Instead, the following is offered in hopes to provide a unique and helpful perspective on the new criterion.

  1. Interactions and Orientation
  2. Content Structure
  3. Visibility
  4. Cognitive

Each criterion will be briefly explained. You will benefit from reviewing the criterion’s Understanding pages as that is where you will find a more precise set of instructions.

Interactions and Orientation

Your site is “touched” and “viewed” using multiple methods.

The oldest method being via mouse or touchpad and the pointer they control on a computer monitor. Next up is the keyboard and monitor. WCAG 2.0 included criterion 2.1.1 Keyboard, for example, to address keyboard tabbing on websites. 

Given the fact that mobile devices and touchscreens are pervasive in the world today, it’s no surprise that several of the new criterion are focused on “touching” and “viewing” said technology.

  • 1.3.4 Orientation (A)
  • 1.3.5 Identify Input Purpose (AA)
  • 2.2.6 Timeouts (AAA)
  • 2.1.4 Character Key Shortcuts (A)
  • 2.5.1 Pointer Gestures (A)
  • 2.5.2 Pointer Cancellation (A)
  • 2.5.4 Motion Actuation (A)
  • 2.5.5 Target Size
  • 2.5.6 Concurrent Input Mechanisms (AAA)

Success Criterion 1.3.4 Orientation (AA)

Bottom line, don’t prevent someone from viewing your content in the display orientation of their choosing. Of course, there are exceptions, but if you don’t have to lock your content in portrait or landscape display, then don’t. This isn’t a feature you would accidently enable, especially if your site is responsive.

Success Criterion 1.3.5 Identify Input Purpose (AA)

You know when you fill out a form online that includes your name and maybe your address and all you have to do is start typing and you are given the option to autocomplete the form? Autocomplete is a feature in HTML5.2. This works because there is a defined purpose to the field.

Criterion 1.3.5 is about ensuring the purpose of the field is clear. They reference the autocomplete technology as a means of satisfying this criterion. However, the intent is “to help people recognize and understand the purpose of form input fields. … form input fields require programmatically determinable information about their purpose.”

If you have forms on your website, you might want to look into whether you are already using HTML5.2 and providing input purposes.

Success Criterion 2.2.6 Timeouts (AAA)

Not everyone can interact with your site forms quickly. It can take time to fill in a field thus creating lengthy interactions.

So, are you collecting job applications online via a form? Are your visitors entering data for anything that might take more than a minute or two? This one's for you. 

It’s likely that you are already advising your visitors that there is a time limit for interacting with your site, if indeed there is one. If not and there is a chance that their efforts will be in vain if the session times out, you need to warn them. If you are storing their data as they go along and thus there are no concerns if they walk away and return the next day, providing a timeout notice is not required.

Success Criterion 2.1.4 Character Key Shortcuts (A) 

Are you adding keyboard functions to your pages? No? Then you are good to go. If yes, then you have a new criterion to review. You don’t want to override an existing keyboard shortcut implemented by assistive technology. This criterion give you guidance in the changes you might need to make.

Success Criterion 2.5.1 Pointer Gestures (A)

What are pointer gestures? Have you ever used two fingers to zoom in or out on your mobile device screen? If you are providing an interface, such as a map, where the user would want to zoom in or out, you might need to add a single input option. According to W3C, including [+] or [-] buttons will accommodate this criterion. For other examples, visit 2.5.1’s Understanding page.

Success Criterion 2.5.2 Pointer Cancellation (A)

Have you ever clicked on a link and upon pressing down you wish you hadn’t? Perhaps you know that moving away from the link as you release your click will cancel your request. Well, in this criterion, they are focusing on actions you might have added to your page via Javascript, for example. Actions that would prevent a click or touch from being cancelled.

If you have, you need to edit your code to not include a down event such as touchstart or mousedown. W3C includes other alternatives to tweaking your code. Instead of repeating the official details here, please visit 2.5.2's Understanding page.

Success Criterion 2.5.4 Motion Actuation (A)

Do you have an app? Is your site presented via an app? If yes, this one might apply to you. This criterion is focused on interfaces that respond to device movements. Not a common feature on websites presented via a browser but definitely a possibility in apps you might be using to present your content.

If you have added functionality to your app that, for example, advances a user to the next page when they tilt their devise, then you need to pay attention to this one. Users need the option to advance to the next page via the user interface and not when their hand accidently moves, mimicking a tilt.

To prevent your application from behaving as such in a mobile device,  you need to add a setting that disables the response to movement.

Success Criterion 2.5.5 Target Size

On a full screen display, it’s easy to imagine large buttons, for example, being acceptable from a design perspective. Shrink that web page down into a small mobile device and that button can become a tiny dot that someone has to hit with a finger or other handheld pointer.

If you have buttons or links or other features that require interaction, they need to be big enough to be touchable - even on the small mobile screens. The Understanding page for 2.5.5 presents a couple scenarios that you should review if you have such interactive links on your pages.

Success Criterion 2.5.6 Concurrent Input Mechanisms (AAA)

To say this is a level AAA criterion seems odd to this reviewer. Why would you prevent someone from using an external keyboard to enter data or interact with your site versus the in-device touchscreen? If you aren’t doing this on purpose and your site doesn’t care what a user uses (mouse, keyboard, touch), then you can check off a level AAA criterion.

If you have an essential reason for such a restriction, then, okay. Although the criterion doesn’t say you have to explain yourself, the instructions for such interactions might be a place to make this clear.

Content Structure

It’s not just words that convey meaning. It’s the style and shape of the content. You might recall two criterion introduced in WCAG 2.0 that focused on ensuring that a user of a website would not miss out on what the content is saying or implying.

  • Criterion 1.3.1’s intent is “to ensure that information and relationships that are implied by visual or auditory formatting are preserved when the presentation format changes.”
  • Criterion 1.3.2’s intent is “to enable a user agent to provide an alternative presentation of content while preserving the reading order needed to understand the meaning.”

Two new criterion have been added on this note. 

  • 1.4.10 Reflow
  • 1.4.13 Content on Hover or Focus

Success Criterion 1.4.10 Reflow 

If your site or app is already responsive, you are well on your way with this one. As long as your content fits in a user’s screen such that only one form of scrolling is required, then you are set.

Your goal is to accommodate a 320 CSS pixel vertical width. Or, 256 CSS pixel height. 

Criterion 1.4.10 is extending the efforts made by criterion 1.3.1 Info and Relationships and 1.3.2 Meaningful Sequence in hopes of ensuring content and functionality are not lost. This time, it’s about resizing versus removing visual and layout styles. If your responsive breakpoints are such that a user need to scroll in two directions to experience your content, then you need to update your code.

Success Criterion 1.4.13 Content on Hover or Focus

Do you provide popup content such as tooltips? You know when you hover over an image or text and you get additional information clarifying the image or text?

If you need to use this type of content delivery, WCAG 2.1 is recommending guidelines that will make such content easier to “see.” For example, when the popup tip appears, ensure that it remains until the user moves away from it. Also, don’t let the users pointer block the content in the popup. 

Of course, more details and explanation can be found on the criterion’s Understanding page.

Visibility

Not everyone can see small text. Not everyone can easily distinguish text from its colored background. WCAG 2.0 gave us three criterion to follow in an effort to accommodate such users of web content.

  • 1.4.4 Text Resize
  • 1.4.3 Contrast (Minimum)
  • 1.4.6 Contrast (Enhanced)

In WCAG 2.1, the following are added to this list.

  • 1.4.11 Non-text Contrast (AA)
  • 1.4.12 Text Spacing (AA)
  • 2.5.3 Label in Name (A)

Success Criterion 1.4.11 Non-text Contrast (AA)

You are already abiding by the contrast criterion for text and images of text if you are meeting WCAG 2.0. 1.4.11 makes some addition to contrasts.

First, you know when you hover over a button or link and it changes? That is a state change. You are going to need to ensure the change meets a 3:1 contrast ratio. Next, it’s not just about color on color but now there is a need to consider color next to color.

The Understanding page for 1.4.11 gives examples such as pie charts and icons lined up next to each other. The potential design impacts discussed on this resource page are definitely worth a read. Too many considerations to list here.

Success Criterion 1.4.12 Text Spacing (AA)

Similar to 1.4.4 Resize text, 1.4.12 wants to ensure that changes in the spacing between lines, paragraphs, letters, or words, they won’t lose content of functionality. So, you might need to check your CSS to ensure the following are possible:

  • Line height (line spacing) to at least 1.5 times the font size;
  • Spacing following paragraphs to at least 2 times the font size;
  • Letter spacing (tracking) to at least 0.12 times the font size;
  • Word spacing to at least 0.16 times the font size.

Success Criterion 2.5.3 Label in Name (A)

This next criterion isn’t as direct as the last two when it comes to visibility of content, but reminds us of the fact that there is more than one way to “see.”

Depending on how your pages were made, you might have both visible and invisible labels on your site. Visible for those who can see the label, such a sign-up button, and invisible, a version of the label that assistive technology reads. Similar to when you create a link to a page and ensured the link and the page title were the same, visible and invisible labels need to match.

What happens when they don’t? A user speaks the label they see and their assistive technology looks for the same words. When visible and invisible labels differ, the technology can’t find what the user needs. 

Cognitive

You don’t have to have cognitive impairment to not understand something. In WCAG 2.0, three criterion are worth noting when it comes to understandable writing.

  • 3.1.3 Unusual Words (AAA)
  • 3.1.4 Abbreviations (AAA)
  • 3.1.5 Reading Level (AAA)

Just because they are AAA level criterion, that doesn’t mean they should be dismissed. They are three of the easiest AAA criterion one can strive towards.

WCAG 2.1 has added criterion that this reviewer feels fits with enabling users of your content to gain a better understanding of what it is your are conveying.

  • 1.3.6 Identify Purpose (AAA)
  • 4.1.3 Status Messages (AA)
  • 2.3.3 Animation from Interactions (AAA)

Success Criterion 1.3.6 Identify Purpose (AAA)

It’s likely that you have at least one of the following on your site: user interface components (e.g., buttons, link, fields), icons, or regions. And, if you are following the requirements of 4.1.2 Name, Role, Value, you are defining most if not all of these.

However, what you might not being doing is providing information about what the component represents, such as an image link represents a link to the homepage. This criterion wants you to convey more than a name, even if the name seems to convey the applicable meaning. Remember, assistive technology is not Artificial Intelligence. It’s needs you to tell it what it can’t surmise on its own.

Success Criterion 4.1.3 Status Messages (AA)

If you are using a content management system designed for accessibility, like Drupal 8 for example, then you should be okay. If not, you will need to update your code to declare your system messages via a role or other appropriate properties that can be understood by assistive technology.

Success Criterion 2.3.3 Animation from Interactions (AAA)

Does this criterion address an interaction or is a cognitive distraction? Perhaps both.

Do you have things that move on your pages? Do objects fly in from the side as someone scrolls? Criterion 2.2.2 Pause, Stop, Hide from WCAG 2.0 applies when the page initiates an animated object. You might have heard of this one. 2.3.3 is intended to prevent animation from being displayed on the pages in the first place.

If you have a dynamic page with moving parts, you need to look into this one. You might need to add to existing animation controls and allow users to keep them from appearing. Of course, this is level AAA, but it’s worth considering as sudden movements can trigger vestibular (inner ear) disorders and cause dizziness, nausea, and headaches.

Conclusions

If you manage a federal site subject to Section 508, that doesn’t mean you shouldn’t take the additional 17 criterion into consideration when updating or building your site. As for everyone else, WCAG 2.1 is the recommended set of criterion. With the chance that someone might claim your site is non-compliant based on 2.1, you need to look into bringing your site up to date.

Remember, some of the new criteria are, by default, not going to be in play on your site. Many of them have to do with added bits of code that override default browser behavior that at one time were deemed acceptable. So, WCAG 2.1 doesn’t have to be scary.

Aug 30 2018
Aug 30

Since its launch, many have written about all the great technology that has been added to Drupal 8. You will find articles online talking about such added features as headless and responsive and accessible. You will read about modules that have been added to core, contributed modules once part of the standard recipe for configuring a Drupal site.

And, that's all good news if you are developer assessing building blocks and code. But, what if you are a business owner, marketing executive, or technical decision maker and don't speak Drupal yet? 

You have a laundry list of features and functionality you want supported by your site and you just need to know if, and a little bit of the how, Drupal 8 is going to meet your needs. Although a planning workshop and Drupal builder course could help you gain a strong understanding of Drupal, you aren’t there yet.

Recognizing this might be you, this article:

  • Shares some of the most common and not so common requirements that you might be facing, and
  • Talks about how Drupal can help support your processes and goals.

Common and Uncommon Features Don’t Scare Drupal

Drupal is a content management system, content being the operative word. However, Drupal doesn’t see content as a blog post or an event. It sees content as data. Data comes in all sorts of shapes and sizes. It carries multiple types of meanings, from the spoken word to value that triggers an action.

When it comes to identifying that which Drupal can’t do, this reviewer only has to stretch her imagination and a solution presents itself, often using existing functionality either from Drupal’s core and from millions that call themselves part of the Drupal community.

In order to demonstrate Drupal’s potential without the aid of video, the remainder of this article will address several capabilities - simple and a little more complex - in hopes that it will help you recognize that Drupal can meet your needs.

When working with managers such as yourself, request often start out as, “I want …” and finish with one or more of the following:

A Mobile Friendly Site 

You are likely one of the majority who surf the net using a mobile device like a smartphone and thus you know what it's like to visit sites that don't fit your screen. Perhaps you have decided that you don’t want to be that business that can't be easily experienced from any device.

Screen shot of default Drupal 8 homepage in it's most narrow display.

Drupal 8 makes it easier than ever to make responsive sites. Responsive means your web pages flex and reshapes automatically to fit your screen. Although responsive functionality was available in previous versions of Drupal, Dries Buytaert, the inventor of Drupal, decided that Drupal 8 would bring mobile to the top of his improvement list.

One of the first steps taken to make this possible was making the jump to HTML5 in order to gain such advantages as engaging the applicable input device when a site is viewed on a tablet or smartphone. 

Check out the screenshot showing Drupal 8 default homepage reduced down to fit on a smartphone.

Different Types of Content

This request often goes without saying and when it comes to Drupal, its response is, “Bring it on!” Any type of content you want, it’s yours. Plus, there is more than one way to get it done depending of the type of data you want to use to define said content.

Let’s consider an example. Story telling. This could mean that you have bloggers, new reporters, media reviewers, etc. At the core of this type of content, they are the same. It’s just the words and tone and organization that often makes these different. 

If you want a separate form to collect each type of content, then you can do that. Even if all the data fields you define are the same in each, Drupal doesn’t care. You can also collect this type of content using just one form with an additional field that lets you categorize the type of content.

This is a very simple example, but hopefully it’s already making you think about how your content can be viewed as data collected in fields versus what you might be used to doing with MS Word or other content management systems.

Since Drupal 7, this type of functionality was part of Drupal’s core. In Drupal 8, the coding structure has changed, enabling your developers to tap into the objects that make this possible and invent unique content collection tools that integrate with Drupal’s permissions and other default features.

Accessible Content Formatting

There are two methods associated with formatting worth mentioning: field-based and manual application. When content formatting comes to mind, you likely think of making text bold or creating bulleted lists. That’s cool. Drupal 8 has that covered by default.

Drupal 8’s text formatting is better than ever. Style your content in MS Word and copy/paste it into your Drupal 8 content form. Don’t do this with previous versions of Drupal, you could end up with a mess of code. Also, Drupal continues to offer settings that control which content author can, for example, add images to their blogs, or not. 

When it comes to using fields other than the traditional long text fields, you can apply styling via templates and CSS. Or, you can rely of the fact that Drupal 8 is WCAG 2.0 ready (likely to be 2.1 ready in the future) and much of the formatting you need is already in place.

Collecting Data Other Than Content

Drupal 7 not only added the ability to add fields for content collection forms, but it also added the ability to add fields to user accounts so that additional data can be collected and possibly displayed for your content authors. Drupal 8 continues this functionality but with the same object oriented strategies implemented for content.

Categorize Content

Categorizing content is at the heart of Drupal. Each Drupal site ships with one Taxonomy that can host multiple vocabularies (containers that hold terms). You can have as many terms (words or short phrases that describe or categorize content) as you need.

Drupal 7 included the ability to add fields to terms so, for example, you can associate an image of an orange with the term: orange. Drupal 8’s contribution, besides better backend code, it a new display page. When someone clicks on a term, they land on a page that displays all content tagged with that term. Drupal 8 makes it possible for you to easily modify that display right out of the box. 

Block Content 

Blocks are bits on content or functionality that can be added to a page. They typically appear alongside the main body of content, or below it, above it. Historically, you would create a block, for example that says, “Welcome to my site. Become a member …”. That block could be placed in one location, let’s say the right sidebar. By default, there wasn’t much more your could do without additional modules.

Drupal 8 has changed the block system. When this reviewer learned by how much, she couldn’t stop smiling. Okay, she might have shouted with glee. 

Anyway, not only can one block be placed in multiple regions at the same time, - in a sidebar and in a footer and in the region that displays the main content - it can display something other than the text. You can now display an image via a field. Or, a video. Or, an attached PDF file.

Yes. You heard right. You can add fields to blocks, made possible by the same object oriented strategies put in place for content, users, and terms. You can also have different types of blocks, just like you can have different types of content forms.

But that’s not all! If you have a block intensive website and you ever want to get a list of said blocks and the content they content in one report, you can query the database and get that list by using the feature called Views. The Views module used to be a contributed module, a staple in 99.9% of all Drupal sites - in this reviewer’s opinion.

Multilingual Site

With each major release of Drupal, the ability to develop a multilingual site got easier. Drupal 8 has not disappointed. Where Drupal 7 required up to eight or so contributed modules to create a multilingual site that was 99% correct, Drupal 8 has four in its core to make it happen.

Coding practices that used to prevent text from being translated are a thing of the past if a module contributor wants their module to be accepted by the community.

It was possible in the past and even easier now.

Manage Content Development

It’s one thing to be able to structure your data you see fit, it’s another to manage the development of said content or data. Aside from the creative nature of content development, you have the ever present need for copy editing. And, if you believe that your content authors can easily catch their own typos, think again.

It’s fortune that the Drupal community recognized the need to manage the process from “I have an idea” to a published work. Drupal 8 has jumped on the workflow wagon by including a workflow option you can turn on and configure. 

Whether your authors compose in MS Word or in Drupal’s content form, the first, second, or even the third draft shouldn’t be seen by the public. You can tell Drupal to save as unpublished. You can collect copies of every draft version by default and switch between them until you are ready for editing.

With additional functionality from the community, you will be able to do things like send notices with draft content is ready for review. You wouldn’t be the first to have this requirement and users of Drupal have been making this happen for years.

Reuse Content in Multiple Displays

This is not the first mention of content reuse. Drupal is all about content reuse. Break your content into structured data and you can find and filter until your heart's content. And, you can then share your queries with the whomever you wish.

Views has been around since Drupal 4, but has always been a contributed module. There are good reasons for waiting to integrate Views into Drupal’s core and now that it is here, Drupal out of the box is that much better.

Most notable is the administrative pages. Hard-coded in the past, the pages that list content and blocks and users and more are now made with Views. They are database queries made into page displays and thus allow you to easily customize your admin pages.

ADA Accessible Site

Accessibility has been mentioned already, but if you didn’t notice, it’s worth mentioning again. Taking a mobile first perspective when designing Drupal 8 was only one priority. Accessible web pages was right up there as well.

The developers of Drupal 8 have taken accessibility seriously. They have reviewed WCAG 2.0 and W3C’s WAI-ARIA. The Drupal community wants your site to be easily read by assistive technology and ARIA was a big step in the right direction.

Deep down, you know how important it must be to make web pages that everyone can experience. What you might not have heard about is the fact that the number of lawsuits for non-compliance has increased and continues to do so.

It’s not just about federal government sites anymore. It’s all sites. Drupal 8 provides a strong foundation to creating an accessible site from the start.

One System, Multiple Frontend Interfaces

You don't want two systems: one that will present your information in a web browser and one that will present your content in a mobile app. Data reuse is a key feature in Drupal and Drupal 8 takes the next step.

Drupal is now what some call “headless” and others call “decoupled”. It doesn't matter which word you use as this functionality is a technical thing that your developers can take advantage of when they present your data through multiple interface frameworks. 

What does this mean? It means you can serve up your content to an app who’s interface was created with a framework designed for mobile devices while at the same time, present content in a browser the traditional way. One blog post, two tools to manage said display. 

This simple example does not suggest that you can only have two frontend interfaces to your content. If you are looking for a central repository for your digital content and you want to deliver it to multiple platforms, Drupal 8 makes it easier than ever before.

Wow, talk about content management. Create it and edit it once and use it over and over.

Affordable Upkeep

This might be the last topic, but that doesn’t mean it’s an afterthought. Like many software applications, significant changes occur from one major release to the next. Unlike many software applications, you don’t have to start over to use the next version.

For a time, you could actually upgrade your Drupal site to the next major release. This reviewer went from Drupal 4.5 to 4.7 to 5.0 to 6.0 before migrating to Drupal 7. Drupal’s backend restructuring to keep up with today’s technology introduced some challenges when it came to taking a Drupal site from version 6 to version 7 and the developers listened to the complaints.

So, Drupal 8 has a few features worth noting as they can impact the cost of managing and maintaining your site.

  • Drupal 8 ships with a Migrate modules to help you tap into Drupal 8’s new functionality by making it easier to migrate.
  • Drupal 8 ships with a Configuration Synchronization module that allows you to launch a version of your site and easily add new features as resources allow.
  • Drupal 8’s path to Drupal 9 isn’t going to come in one giant leap like past major releases. Drupal 8’s development is taking semantic path with releases such as 8.1, 8.2, 8.3, and so on until 9.0 is reached.

These three strategies alone make Drupal more cost effective than ever before. Your development team will have a learning curve to come up to speed on the semantic coding process, but otherwise, they will find Drupal 8 to much more conducive to long term commitments. 

Conclusion

If you want a system that can build just about anything, like one can do with LegosTM , then Drupal 8 is where you want to be. If you have a simple blog site or a content rich site viewed by the world, Drupal can handle it.

The advantages discussed above just scratch the surface of what is possible. Other requirements that Drupal can handle include:

  • Advanced permission settings
  • Powerful content development and layout options
  • Integration with other systems
  • Mash ups - pulling content from other sources
  • eCommerce
  • And more

So, if your requirements are anything like what was discussed above, or if you have something truly unique, let us know. We love a challenge.

Jul 31 2018
Jul 31

When it’s time for a new site, the word “migration” is often dropped in conversations. Every organization looking at a migration in the future will have their own reasons for doing so, their own history, their own future goals. In this article, we will present the following topics as a means to empower you to recognize aspects of website migration you might otherwise overlook.

  • What can a new site look like after a migration.
  • Triggers for a migration project.
  • Paths that might be taken.
  • Creating the right team.

The first two topics are going to feel like the chicken and the egg. Which one comes first? Given the linear nature of articles, they will be presented in said order, but that does not mean the order will match the scenario faced by many.

What can a new site look like after a migration?

Amazingly, not everyone has the same vision of what a new site might mean. Managing expectations from the start is critical to a successful migration project. Below are some common scenarios that can constitute a “new site” and/or “migration” that you might face in your project.

You will find that the following three categories can account for most changes.

  • Server environment change
  • Web platform change
  • Design and/or functionality change

After this, the triggers that might cause one or more of these changes is presented.

Server Environment Change

The process of taking an existing site and moving it from one web server to another would be considered a server environment change. It could entail moving your site from your own web servers to an external vendor.

From a new site perspective, this scenario doesn’t seem to fit. Technically, it doesn’t. Same code, same site. However, to your users, it might feel new if the site’s performance has improved. Your site could actually look different, assuming pages weren’t loading fully due to slow performance.

From a migration perspective, this is text book. You physically move - migrate - to a new server. In the process, you will receive upgraded or new web server features that will need to be configured to work with your site. A few examples include:

  • Caching services
  • Security configurations
  • Development, testing, and production processes.

Your website’s code might be the same, but the environment in which it lives has changed and therefore it cannot be assumed that there won’t be some work to make everything fit and function as required.

Web Platform Change

First, let’s assume that web platform refers to some type of content management system (CMS). The process of migrating from one CMS to another can yield a site that looks the same, but is it?

From the new site perspective, at a minimum, the code-base is different. The configuration strategy is different. The opportunities to improve or enhance your current circumstances can be different. Given the expense, your new system should be ready to allow for your growth in order to justify the expense.

From a migration perspective, to move your site structure, content, interactions, etc. from one CMS to another is a migration, by definition. Depending how similar the systems and how complicated the existing website, the effort to make the move can be extensive.

Example migration and level of effort scenarios might include:

  • Blog Site - Migrating a blog site from one CMS to another is likely the least complex scenario. Most CMSs are designed around enabling users to post their stories, articles, and blogs with ease so the leap should not be overwhelming.
  • e-Commerce/Product Site - The level of effort for this type of move will likely be more labor intensive than a blog site. You might be thinking, “A product is a product,” but the way the sale is managed can vary from system to system. Check out processes may differ. The way the product is loaded into the system may be simple in one, but the other CMS might offer more sales options that you need to consider.
  • Multi-function Site - Sites that provide some combination of blogs, products, events, community, manuals, custom integrations, and more will present even more challenges when moving from one system to another.

The pattern should be clear. The more complex the site that is being migrated, the greater the level of effort. This can include new planning effort, where you dig into the metadata level of content and features. Some CMSs are designed for data micromanagement and you will want to take advantage of the data reuse functionality such a system provides.

Design and/or Function Change

This is one place you will want to manage expectations up front. The scope of work implied by the word design can send your migration project into overruns very quickly. And, the idea of functionality (from a site visitor perspective or a content author’s perspective), can be interpreted many ways.

So, from a new site perspective, design and function will create the most obvious new-site feel. Whether it’s the layout of your pages, your branding, the way your information is organized and accessed, or the new online tools you add, a significant change will occur.

From a migration perspective, the move is to go from one site to another. This scenario is often combined with the first two: server change and platform change. Even if it is not, the effort for such a move is not unlike the process of planning, designing, and building a site from scratch. Even if ideas and content and branding are transferred unchanged, a version of the original website’s implementation process will need to be executed.

Triggers for a migration project.

Based on the discussion above, it might seem obvious what the triggers for change might be. That is true, to some extent. However, there are triggers that can cause a server change while others can cause a system change. Or, both.

Performing a trigger review is a good way to explore the potential, “What about …,” comments that can bubble up during development and trigger yet more change and scope creep. In this section, five triggers for change are presented, along with the type of migration that might be required:

  • Analytics
  • Search engine optimization
  • Technology
  • Mobile first
  • Organizational goals

Analytics Triggers

Web analytics are the statistical data collected about website usage. If the site is not being used, can an organization justify the expense of maintaining said site? Not likely, unless the implied triggers for change from said analytics are implemented.

Triggers of this nature can include:

  • Bounce rate - Site visitors are not spending enough time on site pages. They aren’t reading or watching or interacting as desired.
  • Low or no visits - Pages on the site are not being visited at an acceptable rate. They are either not being found, or their topics don’t meet the visitor’s needs.
  • Low or no mobile device visits - Of the visits, users are arriving on the site via a laptop or desktop. This could be justified given the site purpose, or it could be connected to the bounce rate concern, where people leave the page because it is not easily visible in a mobile device.

To remedy these situations, an analysis needs to be completed. Depending on the findings, the following migrations might apply.

  • Server change - If statistics are off due to poor performance - pages not loading in a timely manner, for example - a new server environment might do the trick. Cached pages are easier and faster to send.
  • Platform change - If statistics are off due to inaccessible pages, pages read by accessibility technology, new code is likely needed. Be it the code for the page structure or the code used to present the content, non-accessible pages can be costly in the long run due to lawsuits, for example.
  • Design and/or function change - If statistics are off due to an unfriendly Information Architecture that make site navigation cumbersome, or due to page layouts that don’t fit in the small screens of today’s mobile devices, a new design will be on your list of changes.

Search Engine Optimization Triggers

When a website lands on the first page of Google’s search results, you can claim success. You have made it. Your site will have visitors. You product will sell. You can now lean back and relax. Not really. Vigilant monitoring is needed as search algorithms are constantly changing.

What happens if when you aren’t on the first page or if you slip from your pedestal? Something will need to change. What kind of changes? If only there was an easy answer to this question, you would be rich.

There are some efforts you might need to undertake, however. For example:

  • Platform change - Using a system that can deliver a semantic web solution is one step towards making a website more understandable. If a search engine can interpret the content of the website (e.g, “price” actually means product price), it’s more likely to index the content of its pages such that they can be delivered to users in search results. How do you think Google creates the images display or the shopping display? With page content it can understand.
  • Design and/or function change - In a 2018 blog post, Google stated, “Our advice for publishers continues to be to focus on delivering the best possible user experience on your websites and not to focus too much on what they think are Google’s current ranking algorithms or signals.”

The changes you need to make will come from an analysis which will include analytics and possibly user feedback. At the end, you should know what is wrong with your current site and how you might make it better.

Technology Triggers

Technology issues can trigger a website migration. With the current rate of change in web-related technology, an older website might already be facing issues that are triggering questions like, “Will our site crash in the near future and leave our customers hanging?”

There are several technology triggers that might send you into migration mode. Here are three examples:

  • Non-secure code - Hackers are always looking to see if they can break into your site. Be it a server hack or a site hack, it can happen. And, if you think only open source products are vulnerable, think about the number of security updates you accept from Microsoft on a regular basis.
  • Too much success - Your CMS was meant for blog posts, not community forums or product sales. You are growing. Your system needs to grow with you.
  • Accessibility problems - Yes. This has been mentioned before but given the increased number of accessibility related lawsuits against website owners, it’s worth repeating. Accessibility is just about page hits, it’s the law.
  • Lack of mobility - “Mobile first” is the phrase of the day and rightly so. Most web users today are using mobile devices to surf the net. Are they surfing you?

The type of changes that might be triggered from the list above can span all three: server change, platform change, and/or design and functionality change.

Mobile First

This drum has already been thumped, but it’s worth mentioning again. We have seen it. “Hey, I was on my phone the other day and saw this cool site. It fit great on my little screen. Can we do that for our site?”

The answer is yes. Given the trend for users to use a mobile device before they reach for their desktop computer, you need join the party. Several technology changes will need to be made to your site.

  • Layout plans - Where do the sidebars go when the page is in a narrow display?
  • Responsive breakpoints - When does the layout of your page change?
  • Menus - That horizontal menu bar will need to change shape in order to be viewable.
  • Media adjustments - Are you still offering up media that doesn’t run on a mobile device? Videos, Flash animations, not all formats work. And, don’t forget images. Those 4MG images aren’t going to fly to a mobile device with ease.

What does this mean for migration? Assuming you have the server environment that can manage the increase in your page hits from going mobile, you might need the following:

  • Platform change - If you aren’t working in a CMS that allows for mobile first design, you will need to change your CMS.
  • Design and/or functionality - As hinted above, page layouts,menus, media will need to be redesigned to accommodate the smaller environments.

Organizational Goals Triggers

The last trigger worth mentioning is the need to meet organizational goals. There is some overlap here with goals pertaining to Analytics and SEO. Other goals might include:

  • Additional services - An organization that talks about books might want to add the option to purchase said books versus providing links to external e-commerce service.
  • Additional resources - Instead of just selling products, the organization wants to provide an education focused community and tutorials.
  • Membership services - Some content might be worth selling right from the browser. The addition of a membership to the website and its valued resources might be the next step to reaching organizational goals.

In each of the examples above, all three types of changes might be required. A new system to provide the new functionality hosted on a server environment that can better handle said changes. Plus, when such changes are required, it’s likely that other design aspects will need to change, hitting all three types of migration.

Paths that might be taken

Once the migration requirement is identified, there are basically two paths to be taken:

  • Do it all now
  • Do it in phases

Do it all now

There are two scenarios that easily lend themselves to this approach.

  • Migration projects such as server changes are at the top of this list. Copy the site to the new environment, test it, fix it if necessary, and go live.
  • If the site will undergo minimal changes, getting it all done now is the likely path.

Of course, any scenario discussed above can follow this path to completion. With the right plans, anything is possible.

Do it in phases

There are several scenarios where this approach might be the best approach. Here are three examples.

  • Technology threats - The current site has been hacked and off line. Instead of spending time trying to fix a potentially outdated website, select the most important features of the site and spin up a new site as quickly as possible. Then, bring the remainder of the features online as they are completed.

  • Legal issues - Lawsuits against non-accessible websites can encourage the need to move quickly. While a new site is being created on a platform that supports accessible websites, two things can occur:

  • Budget - The business is growing, but the budget is still tight. Start with the new look and feel on the new platform and server. Get the basics up and running. Then, bring the new features online as resources permit. Two goals to meet in this scenario”

Creating the Right Team

Last, but certainly not least, is the team of managers, user experience experts, designers, developers, and possibly trainers. Who will you need? Without a plan, without an exercise of “What about …?” and “What if …?” scenarios, you aren’t going to know who you will need.
 

Architecture Workshops

From Stakeholder Mapping to the Delivery of Field-Level Blueprints the Architecture Workshop is designed to take your goals and objectives for your website and provide you solid plan. Whether you develop your website in-house or use an outside firm, this workshop will help you get your stakeholders on the same page, and give your website/project manager a blueprint to ensure you get the most out of your developers.

Private Drupal 8 Immersion Training for your team

  • Get your developers trained on the latest technology by the best Drupal trainers
  • Learn what new innovations you can implement with Drupal 8

 

 

May 31 2018
May 31

Does an accessibility issue on my website mean I need to build a brand new one? This might be one of many questions rolling around in your head as you read the email or letter informing you that your site has an accessibility problem.

 

Don’t panic just yet. It could be something simple, but you need to have all the facts. You need a plan of attack and that starts with a site audit.

Site Audit

Unless that letter is the result of a site audit, you need to set that wheel in motion. Conduct both automated and manual testing to confirm the claim and to determine if there are other problems waiting to be discovered.

Once you have a list of issues you need to address, you can decide if a new website would be easier and more cost effective than trying to fix your current site. Even if the list is long, starting from scratch might not be the answer.

Factors to Consider

Two simple factors in the rebuild decision process:

  • The content management system used to create your site pages
  • Content items in those pages.

After these are considered, site functionality and design can raise its ugly head and influence the direction you need to take. Let’s take a quick look at each factor to get you started.

Content Management System

If the issues reported are being generated by the content management system and are not a reflection of how the site was configured by the developer, ask yourself the following questions to see if there is cure.

  1. Is my CMS proprietary or open source?
  2. If proprietary, did the CMS provider promise accessibility when you purchased the system aso you can get the provider to resolve the problem?
  3. If open source, is there a patch or update you can apply to solve the problem on your own?

 

Simplistic questions? Yes, but they are merely a starting point. If you don’t see a solution after asking these questions, then you will likely need a new site on a different CMS. This doesn’t mean that you can’t transfer your current design to a new system, but it might be time to evaluate your site functionality to see if improvements can be made.

Content

If the issues presented in the letter and/or audit point to types of content that you created and inserted into the CMS, then there’s a chance that you won’t need a rebuild. Again, assuming the site has been configured to accommodate accessibility requirements, then it’s a matter of fixing your content and reposting. For example, if the issues focus on the following, then you can create a plan to fix your issues.

  • Content structure
  • Images
  • Downloadable files
  • Video
  • Audio
  • Uploaded animation

You still might need some developer time if configuration changes need to be made. For example, did someone forget to include the option for the alt attribute to be included with an image? If the changes are extensive, again, it might be time for a new site. Sometimes it’s actually easier to create than it is to edit.

Functionality

Are the issues you are facing tied to site interaction or services, i.e. online forms or interactive maps? Circling back to the CMS, could the issue be that the CMS wasn’t designed to do what you need it to do and will never let you meet accessibility requirements?

At this point, you can decide to either remove the functionality that is causing the problem or you can move to a system that can accommodate your needs.

Design

Just because you can, that doesn’t mean you should. Visual, flashy stuff on the page can be enticing to the user who can actually experience it. Are the issues you are facing linked to the that cool slideshow or mega menu? Depending on your CMS, there might be fixes to your cool features or there might not be.

Like with functionality, ask yourself what is required of your site and then what your CMS can do. You might be applying fixes to your design or you might be moving onto another solution.

In closing …

Facing the need to rectify accessibility issues on your site can feel overwhelming. Even the idea of tweaking all those PDF files to be accessible might want to send you to an early happy hour to drown your frustrations. Don’t worry. You don’t have to face this challenge alone. With training and expert help, you can avoid costly problems in the future.

May 17 2018
May 17

Does your website provide a “place of public accommodation”?

I am online.

Just because your site isn’t made up of brick and mortar, that doesn’t mean you don’t have to comply with the Americans with Disabilities Act Title III, or so said District Judge Scola in 2017 when he concluded that Winn Dixie had violated the ADA by having an inaccessible website.

As the Department of Justice considers updating Title III, the courts are moving ahead with hearing plaintiffs and defendants and handing down rulings. According to Seyfarth Shaw LLP, at least 814 federal website accessibility lawsuits were filed in 2017. New York and Florida lead with 335 and 325 respectively.

I will find the money to fix my site if I get caught.

If you believe that the court costs you might incur if caught are less than the cost of fixing your site right now, think again. The check you write for IT services is only part of the cost you will face if you lose. Imagine the cost of negative publicity?

My website’s target audience can see and hear.

If money and reputation isn’t your motivator, imagine what your life would be like if you couldn’t access content on the web. You can see. You can hear. You have use of your fingers. Imagine one day you don’t. Accidents happen. We all age. Who will you curse for preventing you from accessing content, filling out a form, finding directions? Don’t be that company that prevents others from accessing your goods and services.

I wouldn’t know where to begin.

We know that technology and web accessibility can be overwhelming at best and scary at worst. Consider the following important things you can do now to meet your accessibility goals.

  • Statement of Web Accessibility - A statement from your business regarding accessibility objectives for your site. Keep in mind the effort and resources needed to meet that goal.
  • Hire a Third Party Vendor - Just because your development team says your site is ADA compliant, that doesn’t mean it is. Think of it as hiring an editor because you can’t see your own editorial mistakes.
  • Conduct an Audit - Expert eyes is the key to finding the issues. Both automated and manual testing is required.
  • Remediate Issues - Let your development team fix the issues or hire the experts. You need to demonstrate that you are working to rectify issues in the event that someone comes knocking on your virtual door with a lawsuit.
  • Verify and Document Remediation - Now that your site has been fixed, the ADA related changes need to be verified and documented.
  • Get Trained - Your site keeps changing. Do you know how to ensure your site is compliant moving forward? Training management, content authors, and site developers are the key to ensure your site becomes accessible and stays that way.
  • Maintain - Just because you are trained, that doesn’t mean the occasional content issue won’t arise. Stay on top of your ever-changing site with regular accessibility audits and seek help if you need it.
May 17 2018
May 17

Accessibility badges are gaining attention. These little icons on a web page boast that the page is WCAG 2.0 compliant. As such, the site owner is demonstrating that they recognize the need to provide accessible content.

How does one get a badge to put on their web pages? Assume for a moment that the site owner has actually made an effort and that the badge isn’t a hoax, the process is fairly straightforward. The site owner (or their accessibility consultant) audit the site’s web pages and confirms that WCAG’s criterion has been met.

With sophisticated, automated tools available to anyone with a web browser, web pages can be assessed for accessibility compliance quickly and easily. Or so some believe. Before you start celebrating, let’s briefly explore what it takes to ensure that a single page on your site is WCAG 2.0 compliant and thus badge worthy.

Automated Tool Testing

Automated accessibility testing tools have their place in the auditing process. They are quite valuable from a time-saving and educational perspective. How so?

The automated tools read your code. When they see specific HTML elements, they are programmed to look for code that would suggest that the element has been used in an accessible way. When they see the code is broken, they advise the auditor of the issue and can even suggest a way to remedy the situation. Sounds a little like automated copy editing tools that find typos and grammar issues.

Gotta love that, right? Just like with writers of text, writers of code and online content can’t catch every typo or forgotten attribute. And, if an automated tool can catch the obvious issues, that’s definitely helpful. Let’s look at a few examples that many will have on their pages.

Automated Tool Examples

  • Images - If the tool sees the <IMG> element, it wants to see that the ALT attribute has been included and that there is a description within the alt quotes. Easy check.
  • Segmented Content - If you have segmented content on your page, tools can pick up errors such as using the <h3> element when an <h2> is expected.
  • Audio Files - If the tool detects an audio file on your page, it might warn that the presence of a transcript is needed.

Automated tools can find many issues, but not all.

Manual Testing

Although automated tools catch obvious issues, a full audit requires skilled human intervention. Many of the issues a human will address are warnings expressed by the automated tool. Warnings are provided when the tool can’t be sure if there is an issue or not, and it wants a human to review.

Another aspect of manual testing has nothing to do with said warnings. Automated tools can do only so much and quite often, it’s the automated tools’ “failure” that gets a site owner into trouble.

Manual Testing Examples

Using the three examples above, let’s see how a human is needed to ensure accessibility on a page is being met.

  • Images - What the tool can’t do is determine if the description included in the alt attribute is valid. An image of a mountain range might have an alternative description of, “A beautiful day exploring nature.” This description is about the photographer’s experience, not the image itself.
  • Segmented Content - The tool can’t confirm that the <h3> is a typo or if the <h2> is simply missing. For instance, was there a copy/paste issue while transferring the blog from MS Word? By actually reading the content, a human can determine the real issue and correct it.
  • Audio File - Maybe you have a transcript attached to the page as a PDF. What the automated tool can’t tell you is if the PDF is accessible. It might be able to determine that a screen reader can navigate to the PDF and verify its link, but that doesn’t mean the content in the downloadable file can be read.

Earn Bragging Rights

Conduct a complete audit. Don’t assume that just because you created the right code that your page or its content is accessible. The three examples above only scratch the surface of what an automated tool can and cannot do. Take the time to learn what it means to be accessible, how to ensure accessibility on your site, and how to maintain said accessibility.

Beware of Snake Oil

There are a lot of companies out there that sell products that claim they do accessibility. They may sell a bolt-on widget that doesn’t really work, tell you that automated testing will suffice, and even manually test your site without giving solid advice for how to truly be compliant.

 

The Accessibility Team at Promet Source will get you everything you need to be compliant. Our audit will tell you what needs remediation, and the report we produce will even tell you exactly what you need to do to fix it.

Mar 27 2018
Mar 27

We're packing our bags and heading south! Will you be at DrupalCon Nashville? Don't miss Promet's lineup of sessions, training or stop by and see us in the exhibit hall at booth #710.

This year, Promet Source is supporting DrupalCon as a silver sponsor and host of the annual First Time Attendees social. We're also proud to announce our following schedule of events, including hosting the annual First Time Attendees Social, providing professional training and sessions throughout the week.

Monday, April 9th

Training: Drupal 8 Crash Course for Content Managers, Marketers & Project Managers

Are you responsible for project management, content, or vendor selection and preparing to work with Drupal? This one-day training delivers all of the tools you need to get started. Delivered by an Acquia Certified Drupal Developer, this training will answer the questions you didn’t even know to ask. Targeted to the non-developer, this training is perfect for individuals that need to get up and running in Drupal - fast!

- Time: 9:00am-5:00pm

- Location: Music City Center

Training: Advanced Web Accessibility Training for Drupal Developers

This training is designed to help developers shift their thinking to build accessibility compliant digital content.  During this full day training developers will gain hands on experience in using automated evaluation tools, learning how to incorporate Drupal core and contributed modules that assist with accessibility into their sites, identifying accessibility issues at the code level, and finally developing their sites with accessibility always in-mind.

- Time: 9:00am-5:00pm

- Location: Music City Center

Sign Up Today! If you haven't already, be sure to sign up and snag one of the few remaining spots for training

First Time Attendee Social hosted by Promet Source

To help ease newcomers into DrupalCon, we've put together an orientation designed to explain all DrupalCon's many moving parts and introduce you to a new friend or two. We think starting out the week with a buddy makes networking and navigating an unfamiliar event so much easier!

- Time: 3:30pm-5:00pm

- Location: Level 3 Foyer of Music City Center

Tuesday, April 10th

FREE Workshop: What am I getting myself into? A Drupal Crash Course for Content Managers

Are you responsible for project management, content, or vendor selection and preparing to work with Drupal? This session delivers all of the tools you need to get started. Delivered by an Acquia Certified Drupal Developer, this session will answer the questions you didn’t even know to ask! Learn more.

Time: 10:45am-12:00pm

Location: Room 103B - Music City Center

Wednesday, April 11th

Session: D8 Commerce meets Artistic Expression - Online Shopping with Corning Museum of Glass

Join the CMoG development team and Promet Source as we discuss the journey to roll out a newly redesigned e-commerce site for the Museum powered by Drupal 8 and Commerce 2.0 that showcases the works of art available for purchase online as well as signups for classes and events hosted by the Museum.  We’ll talk about its integration with the Museum’s internal ERP systems as well as some of the technical challenges encountered along the way. Learn more.

Time: 2:15pm-3:15pm

Location: Ambitious Digital Experience Stage - Music City Center Exhibit Hall

Session: More Social, Less Media - Harnessing Human Connection to Achieve Marketing Success

In this session, we'll talk about how to cut through the noise that can often be caused by trying to keep up with industry trends, and how to get to the heart of what your organization - large or small - really has to offer to the world. The unique, collective experience of the people around you (or just yourself!) is hands down the most marketable asset that will give your business the edge it's been looking for. Learn more.

Time: 2:50-3:15

Location: 205AB - Music City Center

What is DrupalCon? 

The Drupal community is one of the largest open source communities in the world. We're developers, designers, strategists, coordinators, editors, translators, and more. Each year, we meet at Drupal camps, meet ups, and other events in more than 200 countries. But once a year, our community comes together at the biggest Drupal event in the world: DrupalCon North America. This year, from April 9-13, we'll be in Nashville, TN. 

Whether you’re an existing Drupal user, developer, designer, site builder, or are maybe just a little Drupal-curious, you won’t want to miss out on this unique event.

Let's meet up! 

The Promet Source team will be flying our flag at DrupalCon again this year and would love to meet up with you! Get in touch to set up a time to chat or simply drop by and see us at booth #710. We look forward to seeing you in Nashville and supporting the Drupal community together!

Mar 07 2018
Mar 07

It's that time of year again for our favorite Drupal camp - MidCamp Chicago!   Of all the camps in all the cities, this one is always our favorite - because of all the great Drupalists we get to meet but also because it's our hometown camp. 

This year, Promet Source is supporting the camp by volunteering our very own Promet Training Practice Manager,   Margaret Plett, to provide a Drupal crash course tailored for non-developers. If you haven't already, click here to sign up and snag one of the few remaining spots!

What is MidCamp? 

MidCamp - Midwest Area Drupal Camp is the fifth annual conference held in Chicago that brings together people who use, develop, design, and support one of the web’s leading content management platform, Drupal. This year’s MidCamp will be March 8th - 11th, 2018 at DePaul University Lincoln Park Campus, Chicago.

  • March 8th — Training (get tickets here!) and Sprints (free)
  • March 9th and 10th— Keynote and Sessions
  • March 11th — Sprints (free)

Read more about the event on their site.

Feb 02 2018
Feb 02

Promet Source has been named among the Gold level winners of the 2018 AVA Digital Awards for outstanding work on the Martin County Florida Drupal website development project in the government category.

2018 AVA Digital Award Winner Promet Source

Related: Martin County Case Case - Redesigning Civic Engagement with Drupal

The AVA Digital Awards is an international competition that recognizes outstanding work by creative professionals involved in the concept, direction, design and production of media that is part of the evolution of digital communication. Work ranges from audio and video productions- to websites that present interactive components such as video, animation, blogs, and podcasts- to interactive social media sites- to other forms of user-generated communication.

AVA Digital Awards is administered and judged by the Association of Marketing and Communication Professionals (AMCP). The international organization consists of several thousand production, marketing, communication, advertising, public relations, and free-lance professionals. AMCP administers recognition programs, provides judges and rewards outstanding achievement and service to the profession.

As part of its mission, AMCP fosters and supports the efforts of creative professionals who contribute their unique talents to public service and charitable organizations. AVA Digital entrants are not charged to enter work they produced pro bono. Over the past several years, AMCP’s Advisory Board gave out over $250,000 in grants to support philanthropic efforts. That money was used for marketing materials for homeless shelters; orphanages; day camps; community theaters and art centers; and for programs and equipment for the elderly and disabled; childcare; and educational endeavors for the underprivileged. Entries come from throughout the United States, Canada and dozens of other countries.

Judges are industry professionals who look for companies and individuals whose talent exceeds a high standard of excellence and whose work serves as a benchmark for the industry. The AVA Digital Award was designed to pay tribute to the magnificent history of the audio-visual and web industries.

See the full list of 2018 AVA Digital Award Winners

Jan 29 2018
Jan 29

In this blog, we will walk through how to use the open source tool, pa11y, to setup and run automated accessibility testing. Before you can start the Automated Accessibility Testing, you’ll need to install the prerequisite tools that are required for this type of testing.  Don't worry, we will provide the list of tools needed as well as the setup and configuration instructions for each tool.

Tools Needed:

Step 1: Install Python then setup in Environment Variables

  • Download latest version of Python at https://www.python.org/downloads/
  • Select Python 2.7.xx
  • Install and follow the installation process
  • After successful installation, set the following in your Environment Variables option
  • Go to System directory, then click "Advanced system settings" link

  • Click "Environment Variables..." button

  • Under System variables option, click "Path" then "Edit..." button 
  • Click "New" button, then add "C:\Python27\Scripts" and "C:\Python27\"

Step 2: Install Git Bash


Step 3: Install Pip

  • Download and follow the instruction on how to install pip

    [embedded content]


Step 4: Install WAMPP


Step 5: Install Nodejs

  • Download and install latest version (e.g. v8.2.1 Current)
  • After installation, RESTART your computer


Step 6: Install NPM


Step 7: Install Pa11y

  • Open Git Bash terminal
  • Execute this:
    npm install -g pa11y
    

Step 8: Install xmltodict

  • Open Git Bash terminal
  • Execute this command 
    pip install xmltodict
    

Step 9: Go to https://github.com/promet/pa11y-sitemap then checkout the pa11y-sitemap folder


Step 10: Go to https://github.com/promet/pa11y-reporter

  • Click 'Clone or download' button
  • Click 'Download ZIP' button
  • File will be downloaded and labeled as pa11y-reporter-master.zip


Step 11: Copy or transfer the file (pa11y-reporter-master.zip) to your pa11y-sitemap folder


Step 12: Unzip the file pa11y-reporter-master.zip

How to Generate an html Output for Web Accessibility Errors Only with links to WCAG

  1. Open Git Bash.
  2. Go to your pa11y-sitemap folder location.
  3. Execute this command:  
python pa11y-sitemap-error-only.py -x <client sitemap.xml> -o <output directory> -r promet_reporter

Example:  

python pa11y-sitemap-error-only.py -x poplar-sitemap.xml -o POPLAR/reporter/error_only/ -r promet_reporter

Results:  

It will generate file(s) with html output format and with links to WCAG  

How to Generate an html Output for Web Accessibility errors, warnings, and notices with links to WCAG

  1. Open Git Bash.
  2. Go to your pa11y-sitemap folder location.
  3. Execute this command:  
python pa11y-sitemap.py -x <client sitemap.xml> -o <output directory> -r promet_reporter

Example:  

python pa11y-sitemap.py -x poplar-sitemap.xml -o POPLAR/reporter/errors/ -r promet_reporter


Results:  It will generate file(s) with html output format and with links to WCAG guidelines

How To Generate a Pa11y Summary File of Web Accessibility Errors, Warnings, & Notices

  1. Open Git Bash.
  2. Go to your pa11y-sitemap folder location.
  3. Execute this command:  
python pa11y-sitemap.py -x <client sitemap.xml> -o <output directory> 

Example:  

python pa11y-sitemap.py -x poplar-sitemap.xml -o POPLAR/reporter/summary/ 

Results:  It will generate file(s) with json output format

  1. Copy the file(s) where your json folder is located (Note: This was set in config.php file) 
  2. Launch WAMP Server then select Localhost.
  3. Copy the folder name pa11y-summary-PDF-generator-master, paste it beside localhost url then press ' Enter ' key.
  4. Save as a PDF:
  5. Launch http://localhost/pa11y-summary-PDF-generator-master/ in Chrome browser (recommended browser)
  6. Press ' Ctrl + p ' in the keyboard, then click ' Save ' button
  7. Open the pdf file to view the summary results.
Jan 24 2018
Jan 24


Responsive images are great! If I wanted to quickly introduce what responsive images are to some, I would say: On mobile? Small images. Tablet? Medium images. Desktop? Large images. This article is a complete "how to" in setting up responsive images in Drupal 8. 

If you are using Drupal 7, check out my previous article here: Picture Module: Building Responsive Images in Drupal 7.

So much has changed in Drupal 8 since our last tutorial. With D8, there is no need to download an extra module. The 'Responsive Images' module is now in Drupal's core.

Here is what this post will cover.

  1. Enable the Responsive Image module.
  2. Setup breakpoints.
  3. Setup the image styles for responsive images.
  4. Assign the responsive image style to the image field.

Lets get started!

Step 1: Enable the Responsive Image module

One of the major changes in building responsive images in Drupal 8 from Drupal 7 is the responsive image module being part of Drupal’s core - there is no need to download an extra module. However, this feature is not enabled by default.

  1. To enable the responsive image module, go to "Admin" > "Configuration" (/admin/config).
  2. Click the checkbox next to "responsive Image".
  3. Click "Install".

Enable Drupal Responsive Images module

Step 2: Setup breakpoints

If you are using a default theme like Bartik, there is no need to create breakpoints.yml file. Default themes already have this file.

If you have a custom theme, go to your editor. In the root of your theme directory, create a file called "yourthemename.breakpoints.yml".

Your theme directory is usually found at "/themes/custom/yourthemename".
For this tutorial, I will call my theme "alumni_theme".

alumni_theme.small:
  label: small
  mediaQuery: '(min-width: 0px)'
  weight: 0
  multipliers:
    - 1px
    - 2px

alumni_theme.medium:
  label: medium
  mediaQuery: '(min-width: 740px)'
  weight: 1
  multipliers:
    - 1px
    - 2px

alumni_theme.large:
  label: large
  mediaQuery: '(min-width: 1200px)'
  weight: 2
  multipliers:
    - 1px
    - 2px

Each breakpoint will tell Drupal what image size to load for each of the assigned mediaQuery. For example, we can load an image with a small image size for the breakpoint at min-width: 0px. When the browser is at min-width: 740px we can load another image size.

It is important to take note that the breakpoints weight should be listed from smallest mediaQuery to largest mediaQuery.

The multipliers allow us to display a crisper image for HD and retina display.

Step 3: Setup the image styles for responsive images.

Drupal image styles

We need to create the image sizes for the different breakpoints. Add one image style for each breakpoint you set at your_theme_name.breakpoints.yml. Since we created three breakpoints in our breakpoint.yml file, we will have to create three image styles.

 

One image style for each breakpoint.
 

For this tutorial, I will create:

  1. Image style of 400px by 200px for a minimum breakpoint of 0px up to breakpoint not more than 740px. This image style would be used for mobile devices.
  2. mage style of 1000px by 450px for a minimum breakpoint of 740px up to breakpoint not more than 1200px. This image style would be used for medium devices like Ipads.
  3. Image style of 500px by 400px for a minimum breakpoint of 1200px and above. This image style would be used for large devices like desktops.

 

You can configure your own image styles at ‘Home > administration > Configuration> Media’ (/admin/config/media/image-styles).
Click ‘Add image style’.
Type in the name of your image style. It’s better if your image style name is descriptive.
Click Save.
From the drop-down, choose scale and crop.

Click ‘Save’.
Image style dropdown

Type in the width and height of your Image style.
 

Input width and height of the image style

Click ‘Add effect’.
So that's one image style. Go ahead and create two more image styles. Just follow the steps provided above.

Here are the three image styles I created for this tutorial.
Image style

Step 5: Responsive Image styles

We will now assign the image styles with the breakpoints, to create the Responsive Image styles.

 

Go to ‘Home > Administration > Configuration > Media’ (/admin/config/media/responsive-image-style) and click on ‘Add responsive image’.
For this tutorial, I will call it ‘Header Image’ since this will be used for the header images of my posts.


Type in the name of your responsive image.Responsive Image style

From the drop-down in ‘Breakpoint group’, choose your_theme_name.

 

Click Save.
Assign image styles to every breakpoint defined in “your_theme_name.breakpoints.yml”.

Responsive Image styles assigned to each breakpoints

Step 6: Assign the responsive image style to an image field
 

Go to the content type where you want the responsive image style to be used.
Click ‘Manage fields’.

Responsive image setup in a content type image field


Click the gear icon on the right side.

From the drop-down under ‘Responsive Image style’, choose the responsive image style you created.

Image formatter setup in content type image field

And we are done!

To check, add a new content piece and add an image to the image field (make sure you are in the right content type). Resize your browser to the browser size defined in your your_theme_name.breakpoints.yml.

Right-click on the image and click ‘inspect’. In ‘network > img’ you will see the name of the image style that your image is using based on the browser size.

Responsive image on a small deviceMy image at a minimum width of 0px breakpoint.  responsive image at a medium deviceMy image at a minimum width of 740px breakpoint. responsive image at a large deviceMy image at a minimum width of 1200px breakpoint.

And we are done! Your image should now be resized based on the browser size without losing its quality.

Special thanks go to Raymond Angana, Andrew Kucharski and Luc Bézier for contributing to this post before publication.

Jan 23 2018
Jan 23

The FLGISA is an organization for CIO's, IT Managers, and technology decision makers from the state's local government agencies. The FLGISA Winter 2018 is where technology leaders from Florida local governments attend to learn, share the latest in technology trends, foster new professional relationships and meet current and potential business partners. Conference attendees consist of local government chief information officers, technology managers, and other technology decision-makers.

The Promet Source and Acquia team will be onsite throughout the duration of the conference to speak with attendees about web development, support, hosting, web accessibility and cloud based open source solutions that can help propel their government organizations web presence. 

About Promet Source

Founded in 2003, Promet Source is a web design and development agency that specializes in open source solutions for government, higher education and association/nonprofit clients. They offer web design, custom implementations, private and public instructor lead Drupal training, complex integrations, web accessibility compliance services, digital consulting and full 24x7 support to their clients. 

About Acquia

Acquia is the leading provider of cloud-based, digital experience management solutions. Forward-thinking organizations rely on Acquia to transform the way they can engage with customers -- in a personal and contextual way, across every device and channel. Acquia provides the agility organizations need to embrace new digital business models and speed innovation and time to market. With Acquia, thousands of customers globally including the BBC, Cisco, Stanford University, and the Australian Government are delivering digital experiences with transformational business impact.

Working with Government Organizations in Florida

Together, Promet Source and Acquia have helped a number of organizations in Florida redesign and rethink their websites to create modern, user friendly and accessible digital experiences with Drupal 8. 

South Florida Water Management District:

SFWMD needed a platform that was modern and user-friendly. Because they have a lot of content to share with site visitors, they needed a content management system that could comfortably handle large amounts of information. Their previous site had hard-coded pages, which were cumbersome to update, so they also needed a site that could be updated without having to touch code when information changed.

Related: Case Study / SFWMD Launches Modern, Accessible, User Friendly Site with Drupal 8

SFWMD also wanted to minimize the usage of custom modules and code, so a decision was made to utilize existing Drupal 8 modules and code whenever possible, instead of developing or depending upon custom modules. In order to help SFWMD schedule budgeting and management needs for the project, Promet Source took a phased approach to the project, and set phases and milestones so that both parties could keep track of the project progression.

Martin County Florida: 

The state of Florida has a policy of open government which allows Floridians free access to public records and documents. This is a great way to bring transparency to the inner workings of Florida’s government agencies. 

Promet Source was faced with the challenge of building a highly useable and accessible Drupal site that also made thousands of PDF files searchable within the site. Combine a massive volume of data with the particulars of Martin County’s user stories: users need to see accurate search results for specific synonyms within the vast library. Another wrinkle to the equation was introduced by the hosting setup for Martin County, a cloud instance which didn’t allow Javascript. 

Related: Martin County Case Study / Redesigning Civic Engagement with Accessibility for All Users

Promet Source implemented a PDF document parser with Apache Tika. A single instance of Solr on the web head server delivers speedy results, while swapping Solr’s default query configuration for indexed phrases and other stored content to deliver highly accurate results for searches containing phrases. The indexed content is then displayed to the end user on the Drupal site.  

The end result is a comprehensive search functionality that quickly delivers accurate results from three different sources, while providing all users with a flawless experience, no matter their web accessibility challenges.

Dec 19 2017
Dec 19

Another Drupalcamp event had just successfully ended in Cebu! This is one of the largest Drupal Conferences in Asia Pacific Region organized by volunteers and open source enthusiasts. Promet is happy to provide organizing space and event support.
 

The local community is growing!

It was very overwhelming to see Drupalcamp Cebu grow in number year after year since it first started last 2014 with 120 attendees. Drupalcamp Cebu 2015 had 70 attendees while Drupalcamp Cebu 2016 had 100. The monthly meetup in Cebu City helps in keeping in touch with the local community over the years.

This year we had a total of 150 attendees!
 

Graph of Attendance of Drupalcamp Cebu over the years.Attendance of Drupalcamp Cebu over the years.


Last November 1, 2017, Cebu had just successfully concluded its 4th consecutive Drupalcamp (thanks to the collaborative effort of the Drupal Cebu User group led by Luc Bezier), hosted by CIT University.

“CIT University has been one of the most dynamic universities that we worked with. They were very active in the venue preparation. They also sent student volunteers to help us during the event.” - Luc Bezier, Organizer.
 

Drupalcamp Cebu 2017 logoDrupalcamp Cebu 2017 Logo was selected following a logo contest. Congratulations to Ron Corona for his winning entry :)

Sponsors

Of course, the event would not have been made possible without our sponsors. Promet Source has been happily sponsoring Drupal events in Cebu and in the Philippines, and has been a GOLD Sponsor for Drupalcamp Cebu every single year! It’s no surprise, as Promet Source is already the venue for the Drupal meetup, last Wednesday of every month.

Below is the list of Drupalcamp Cebu 2017 sponsors.

GOLD SPONSORS: Promet Source, and Srijan
SILVER SPONSORS: Pantheon, and ANNAI.
BRONZE SPONSOR: Powerstorm.
COFFEE AND SNACKS SPONSOR: SkyRockIT


It is interesting to see that every sponsor had already sponsored this event in the previous years. I think it is a great proof of the success of the camp and that sponsoring the event is successful for both: the event organizers and the companies involved.

Pre-camp: the speaker’s dinner

A night prior to the event, Drupalcamp Cebu 2017 speakers got together over Dinner at the rooftop of Harold’s hotel.

It was fun to see familiar faces again and meet new speakers at Drupalcamp Cebu. It lets the speakers meet each other in a less formal way. Some had a long flight from another country, so they could enjoy a nice dinner and have a good rest before the conference. The dinner was organized and paid by the Drupal Cebu User Group. A few of the speakers were missing but most of them came and really enjoyed the live band.

Drupalcamp Cebu 2017 speakers dinner.Photos from the Speaker’s dinner at Harolds' Cebu rooftop restaurant.   

The sessions

Image of the registrationDuring the registration.

 

The camp this year had 23 sessions (one was canceled), but before the sessions started, we were able to attend the Keynote by John Albin Wilkins (JohnAlbin on drupal.org). It was great having John to visit us in Cebu and be our keynote. He is a very prolific sharer of free code. His Zen theme has been downloaded nearly two million times on drupal.org!

During the Keynote, he talked about future versions of Drupal 8 and Drupal 9, and how modern software evolves to facilitate migration from one version to another. By listening to him, we learned that with Drupal 8 we will slowly depreciate the API when changes are needed. This is to make migration from one version to another way smoother than we had ever experienced with Drupal. Link to the slides

 

Image of the keynote speaker and attendees in the session room

 

“I saw John’s keynote in Drupalcamp Taipei and I asked him to present the same for Drupalcamp Cebu 2017. I really liked his way of demonstrating how Drupal is planning to fix one of the main issue we have when migrating from one major version to another version in drupal. Gradually depreciating the API rather than breaking changes”
- Luc Bezier, Organizer.

Session for everyone

After the keynote, attendees went into their choice of sessions held simultaneously at four different rooms. Each room was labeled after each sponsor. To make it easier for the attendees, the sessions were divided into 8 categories:

frontend,
backend,
QA / accessibility,
business,
devops,
UI/UX,
lifestyle.

There was also 3-hour Drupal training for beginners attended mostly by students.

Cedric Chaux, from Taiwan, talked about the mistakes he made as a developer (Link to slides). He discussed some of the common issues we come across at work like task mismanagement, wrong estimates, procrastination, and unreliable clients.

The session was easy to relate to. I think it was a good reminder of the things that we should not do and the things that we should do as a developer.

Image of speakerCedric Chaux presents "Mistakes I Made as a Developer".

Donnabel Carato gave an overview of Web Accessibility. It was a very interesting session and helped me understand the process behind QA for Web Accessibility. Donna is the QA lead at Promet Source so the personal experience on QA was very interesting. She is involved in the ADA Website Accessibility services that Promet is providing.

Image of speakerDonnabel Carato on 'Web Accessibility Overview'.

Aman Kanoria, from India, discussed the improvements that came with Drupal 8 when it comes to managing media. He did a good showcase of some possibilities using cool modules like Dropzone or Entity Embed  (Link to the slides). Some of them I will definitely try to re-use in the future.

Image of speakerAman Kanoria: Managing Media assets in Drupal 8

The session of Luc Bézier "Guide to Freedom and Travels for developers" was not technical, but on lifestyle as a remote developer. Luc gave some highlights of the remote lifestyle and some tips on how to keep in budget while traveling. He traveled to many countries this year like Australia, Thailand, Morocco, Italy or Taiwan, and his session included exotic photos and a bunch of useful advices (Link to the slides).

Image of Luc Bezier session Luc Bézier during the opening session

From the 23 sessions, I was not able to attend them all. Other sessions included for example: "Ionic and Drupal Headless" by Leolando Tan, "Atomic Design" by Justine Win Canete, "Manage Docker Host or Swarm Cluster with Portainer" by Ashwini Kumar, "How to make your site on D8 Fly with Redis" by Paul de Paula, "Master of Mailgun" by Ranny Navarro, "Skill up! Learning, relearning and unlearning" by Joan Maris Rosos and "Automated Accessibility testing via PA11Y" by Raymond Angana.

The complete lists of sessions and more slide presentations have been posted on the camp's website https://2017.drupalcebu.org/schedule/.

“I like the session from Annai about ‘Open Portal Data Using Drupal. It's interesting to note that drupal is able to bring positive change to the community (like Japan), and the number of things you can do with drupal’s technology.”
- Mike Vallescas, third time attendee.

The Drupalcamp Training

Aside from the ~20 sessions offered, every year, we organize a training for beginners. Donnabel Carato and I usually present the “Drupal Introduction”. It is a one-hour presentation. The main purpose is for the first-time attendees to get acquainted with what Drupal is, it’s history, when to use Drupal, and who uses Drupal.

This is always followed by 2 or 3 hours training for beginners.
This year Dennis Abasa and Keith Roi Francis Sasan did an amazing job. Their training was focused on site-building and theming with Drupal 8.

 

Drupal trainersDennis Abasa and Keith Sasan: Training: Site building and theming with Drupal 8

 

Image of attendees in a session room.

 

We had around 60 people in the room, that’s a big jump from 35 last year. A majority of the beginners were students, but among the crowd, we had two IT Directors and an IT instructor from Eastern Samar (a neighboring island of Cebu) - all three were first-time attendees.

We also had a Wordpress developer all the way from New Zealand. During the registration, I happened to have a quick chat with him. He mentioned traveling to Asia and happened to see ‘Drupalcamp Cebu 2017’ event on Drupical’s website (link to https://www.drupical.com). He had always wanted to learn Drupal and decided to stop by and join the event.

 

“Always browse Drupical, you might be surprised where it takes you.”

Luc Bezier gave his closing session at 6 p.m. And just as the camp started with a live band at the speakers' dinner, it also ended with a live band at ‘IAMIKS Chicken and Beer’ for the yearly after-camp party. The trivia was organized by Raymond Angana.

Beer and games!

 

Organizer of Drupal triviasRaymond Angana: Organizer of the Drupal trivia at the Drupalcamp Cebu 2017 party.

Wait ... Where is Cebu?
Cebu City is the second largest city in the Philippines and is one of the most popular tourist destination in the country. Known as the ‘Queen City of the South’ this island is surrounded by more than 150 islets, you can just imagine the number of beautiful beaches waiting to be visited.
Aside from the beaches, there is still a lot to love about Cebu. 
Here you will find diving spots, snorkeling areas, mountains to climb, waterfalls, caves, and historic places to explore.

For Drupal lovers, one good reason to visit is the yearly Drupalcamp. Now that’s tempting.

Image of Cebu's tourist destinationsClockwise: Kawasan Falls, Moalboal, Bantayan island, Taoist Temple


Testimonials


This year we decided to throw questions to our attendees to get to know what they think and how they feel about the camp.

Q: What are the main improvements made in Drupalcamp Cebu 2017?

“One of the improvements of this year’s camp was the use of online payment. It was quite successful. We had the better estimate of how many people we would have ahead of the event" - Luc Bezier, Solutions Architect.

Luc has been the main organizer of Drupalcamp Cebu since 2014. Kudos to you!

Q: What session did you like the most?
“I honestly liked Mark Koh’s session “Drupal Beginner’s Essentials”. The topic on GIT was the most interesting part for me because of its power and capabilities on file management. And the fact that the speaker was not boring. He has the ability to capture our attention and he has that guts in the delivery of this topic.” - Gil Dialogo, IT Instructor.

Q: What do you think about Drupal?

“Drupal, though I have not used it yet in the development of websites, I guess it's good and user-friendly. Plus, there are experts whom we can lend a hand during development because of its a supportive community.” - Gil Dialogo.

Gil is a first-time attendee and an IT instructor at Eastern Samar State University - Salcedo. Eastern Samar is a neighboring island of Cebu and one of the biggest islands in the Visayas.

Q: What interested you most about Drupalcamp Cebu 2017?

“Drupalcamp Cebu 2017, has an interesting line up of talk and sessions.” - Donnabel Carato, QA lead.

Donnabel is the QA lead of Promet Source Cebu, one of the organizers of the Drupalcamp and presented during the Training for beginners.

Q: What do you think about Drupal?

“I am a pro-open source advocate and I see Drupal be an evolving CMF platform that's flexible, extendable, scalable, and secure. There's so much you can do with Drupal and hope to see more platform development and growing modules in the future”. - Michael Mark Vallescas.


Michael Mark Vallescas had been attending every Drupalcamp Cebu, since the first one in 2014. When asked about why he finds Drupalcamp interesting he said: “I like meeting like-minded people and learning new things about Drupal.”

In conclusion, Here is Drupalcamp Cebu 2017 in numbers:

  • 2 gold sponsors
  • 2 silver sponsors
  • 1 bronze sponsor
  • 1 coffee and snacks sponsor
  • 23 sessions
  • 3-hour Drupal training for beginners
  • 150 attendees
     

Thanks to all the organizers of the camp for doing extra hours after work. Kudos to Luc Bezier for taking the lead, well done!
We greatly appreciate the support from all the sponsors, the speakers for sharing your expertise, and to all the attendees.
We would also like to thank our foreign attendees and speakers for flying all the way to Cebu to be a part of Drupalcamp Cebu 2017.

Saving the best for last ….

Q: What session did you like the most?

“I like the training session most since it was the first time I was introduced to Drupal. I also like  the ‘Guide to Freedom and Travels, for Developers’ a great session where Luc give us some pieces of advice on traveling tips
Too bad He didn't give us some free plane tickets.” - Mikko Olmillo.

Miko is a student and a first-time attendee of Drupalcamp Cebu. He is very interested in learning Drupal and hopes to participate again in Drupalcamp Cebu 2018.

See you guys next year!!

 

Special thanks go to Luc Bézier for his significant contributions to this post.

Dec 18 2017
Dec 18

Promet Source is proud to announce that we have teamed up with OpenYMCA.org, an open-source digital platform for marketing and e-commerce, as a Drupal development partner. Through this partnership, we are committed to the Open Y philosophy, community, and platform. Promet has worked with several YMCA organizations across the country to build and maintain their Drupal websites. Through this new partnership, we are eager to utilize our Drupal expertise to not only assist YMCA organizations with their Open Y platform implementations, but to also build new modules, customize and extend the platform to meet the needs of their community.

About Open Y

The Open Y platform is a content management system that uses Drupal 8 functionality and useful modules from YMCAs and digital partners. It’s easy and free to use—everyone is welcome to implement Open Y and run Open Y projects.

In 2016 a group of YMCA digital, marketing, and technology experts recognized the digital opportunities that exist if we work together as a community and established Open Y.

A core team led by a small group of YMCAs including the Greater Twin CitiesGreater Seattle and Greater Houston:

  • Maintains the Open Y content management system and OpenYMCA.org site
  • Ensures all basic functionality accessible from the content management system is available free of charge—those who contribute cannot charge others for what is shared
  • Strives to be aware of issues found within the Open Y content management system
  • Is not liable for bugs, crashes or performance issues of the content management system
  • Invites and approves digital partners to join
  • Distributes communication about Open Y
  • Organizes events for the Open Y community—including 2 annual meetings

About Promet Source

Founded in 2003, Promet Source is a web design and development company that specializes in open source solutions for government, higher education and association/nonprofit clients. Promet Source’s founder, Andrew Kucharski, started the company as a custom .net solutions firm that focused on eCommerce projects for national brands.

After getting exposure to the Drupal community of open source developers, Kucharski realized that Drupal would become the go-to solution for clients that need to solve complex problems in content creation, membership management, donations and fundraising, and responsive design. Promet realigned its core services and solutions to meet the needs of clients faced with these issues and set about solving problems with Drupal.

Promet Source is a comprehensive Drupal development agency that offers custom design, custom implementations, private and public instructor lead Drupal training, web accessibility compliance, consulting and full 24x7 support to its clients.

Dec 14 2017
Dec 14

My name is Katherine Shaw and I am a front end web developer at Promet Source. I'd like to start by sharing a little bit of my background, as it has helped me to understand why accessibility, on the web and in the world around us, is such an important issue. I am an advocate for web accessibility and in today's blog, I'll be sharing how I became so passionate about implementing ADA Section 508 best practices into my work as a developer, which all began when I was working for local government.

I was born in Waco, Texas into a military family. I was the first born in my family, and my brother followed close behind. I travelled the country and to Japan throughout my childhood, giving me a great sense of other cultures and environments at an early age. With this constant travel, I didn’t grow roots anywhere helping me to feel out-of-place for much of my life. This unintentionally helped me with accessibility because:

  • I learned many points-of-view: Being around so many different types of people in various cultures helped me to understand that there are many points-of-view in the world.
  • I didn’t feel understood: Always being the new kid was difficult at times, making it so that you don’t always feel understood.
  • I had communication issues: Whether it was moving to a new school or a new country, I know how it feels when you have issues communicating with others.

Web Accessibility - My "Aha" Moment

In March of 2012, I met Dan, who works for the CIO’s office of the GSA’s Section 508 and Accessibility. He presented on accessibility from the point-of-view of a blind user. This presentation completely changed my perspective from that point on.

Hearing the JAWS screen reader
He showed us how a site sounds with the screen reader JAWS, which really blew my mind! I got just a glimpse of what it’s like for non-sighted user to use a site.

Section 508 testing methods
Dan discussed Section 508 testing methods, and shared various tools that are available on the web.

What I took from it
I was intrigued by his entire presentation, and my eyes were opened to a new world. I’ve never turned back, and I’ve now become an advocate for accessibility.

Implementing Web Accessibility in Local Government

After getting inspired by Dan’s presentation, I immediately brainstormed ideas on how I could implement some of these ADA Section 508 and WCAG standards at the county I worked for at the time.

Implementing basic web accessibility standards
Since I was the sole Webmaster, I was able to implement a lot of those changes without any issue on the existing site. When building new county sites in Drupal 7, I made sure to develop with accessibility standards in-mind.

Educating the staff on Web Accessibility
My next step was to try to educate the staff on why scanned PDF’s and images weren’t accessible, why images needed distinguishing alt tags, why writing in plain language matters to all of our users, and why a service-based approach is better than a department-based approach

“Spring Cleaning” of content
I was able to come up with a “Spring Cleaning” concept for the big redesign which worked well at accomplishing a lot of these goals. I also built-in a lot of these standards into the site, including:

  • Required alt tags for all images
  • Skip navigation on all pages
  • Page titles on all pages, with home page’s hidden for sighted users only
  • Automatically added titles from content to links, which creates tooltips on hover
  • Created a uniform top site navigation that didn’t change across the site
  • Created linked headings to text blocks on all content pages
  • Created templates for every content type, resulting in a uniform design

Old habits are hard to break
Some employees had a difficult time with these changes, and continued with their old practices including scanning documents and images and writing text that was too long for users to read through and understand.

Employees think department-based
Some employees asked for their department to have a button prominently displayed on the top navigation or wanted their own custom layout that was different than the rest of the site.

They didn’t understand that these updates don’t follow accessibility standards and also confuse users.

Support for web accessibility is needed from the top
When you work with elected officials, you’re limited in what you can do if you don’t have support from the top down.

Getting buy-in from administration is the key to success. Otherwise you will be fighting a lost-cause a lot of the time.

An Inspiring Moment from my work in Web Accessibility

Not long after I began to implement accessibility best practices into my development work at the county, I received a call from a blind citizen who was trying to access our website. There was a form he was attempting to use that was causing problems for him, specifically with a select menu with a list of states in the US. He stated that the select menus weren't helpful for him because he could only read abbreviations for the states. I could immediately identify that the keys were abbreviations while the values were the full names of the states.

Identifying and fixing the issue in real time

Sighted users see the values as they see the full names, while blind users see only the abbreviations. This is an unfair setup. Because of his feedback, I matched the keys to the values for all select menus throughout the site. You can view the example code below:

Old:

<select value=”KS”>Kansas</select>

New:

<select value=”Kansas”>Kansas</select>

After we were finished troubleshooting through the issue, he was not only extremely happy that this issue was resolved for him and other users, but he expressed that he was thrilled that I took the time to work through the issue with him on the phone.

Getting Involved with Web Accessibility

As a member of Promet's web accessibility team and an IAAP Certified Professional in Accessibility Core Competencies (CPACC), I now get to work with clients to ensure their websites are accessible to all users. I work on several remediation projects for Promet clients from start to finish. Consulting with clients, as well as performing the actual remediation work, has been very rewarding for me here at Promet.

Knowledge Sharing and Documentation

In addition to my client work, I share my knowledge and contribute to accessibility at Promet on a regular basis. I have also created a new Menu Attributes a11y sandbox project, which will hopefully be committed to the main Menu Attributes module to assist with accessibility.

I’ve also created documentation on Web Accessibility Standards and other accessibility information for the Promet team, as well as other documentation at previous positions.

I believe it's that it's time for us to develop with an accessibility-first approach at all times, and I hope my work can inspire you to do the same!

Need help getting started with web accessibility for your organization? Contact us today.

Nov 28 2017
Nov 28
Drupal Commerce: Powering ALA.org on Giving Tuesday | Promet Source

Drupal Commerce ALA giving tuesday

Drupal Commerce: Powering ALA.org on Giving Tuesday

Promet Source is proud to partner with the American Library Association (ALA) to deliver a flawless user experience with Drupal Commerce on Giving Tuesday, and every day of the year.

Related: ALA | Empowering Association Fundraising with Drupal Commerce

Promet Source worked with the key decision-makers at ALA to build a powerful website that integrates with iMIS, the system of record for all membership activities such as recruiting new members, renewing memberships and managing donations from all sources. 

ALA giving Tuesday match promotion

On this #GivingTuesday, ALA has set a goal to raise $50,000 and is even matching every donation, dollar for dollar, up to $1,000. Visit ala.org/donate to make your contribution.

You’re ready, we’re ready. Let’s get started.

Get started

Nov 22 2017
Nov 22

Ready to level up your skills before the New Year? You're in luck! Promet Training has confirmed Drupal 7 and Drupal 8 courses for developers, project managers and content editors coming up. Each month, Promet Training offers classes in AustinLas VegasWashington, D.C., Chicago & Live Online. Visit PrometTraining.com for the full course schedule and sign up today.

This four-day course provides a comprehensive understanding of Drupal 8 Site Building and Front End development. The procedures throughout the week are introduced step-by-step and then reinforced with practice and challenges. You'll build multiple sites and themes to meet the needs of a client and reflect on your own experience to take the procedures you learn back into your own work and any new situations you encounter.

November 27-30 / Washington, D.C. (Confirmed Course)

This five-day course provides a comprehensive understanding of Drupal 8 for developers responsible for full stack development. The procedures throughout the week are introduced step-by-step and then reinforced with practice and challenges. You'll build multiple sites, a custom theme and a few custom modules to meet the needs of a client and reflect on your own experience to take the procedures you learn back into your own work and any new situations you encounter.

This course allows developers to walk through the process of building multiple custom modules and provides techniques and best practices for developing custom functionality to extend the capabilities of Drupal.

Quickly get developers running full speed ahead in Drupal 8, and convey a full understanding of how Drupal sites are constructed and how the system works. 

December 11-15 / Las Vegas, NV

December 18-22 / Live Online (Confirmed Course)

This 4 day class provides a broad introduction to the essential skills necessary for editing content, building websites, managing the theme layout and working with the extremely popular Panels module.

December 11-14 / Austin, TX

Pages

About Drupal Sun

Drupal Sun is an Evolving Web project. It allows you to:

  • Do full-text search on all the articles in Drupal Planet (thanks to Apache Solr)
  • Facet based on tags, author, or feed
  • Flip through articles quickly (with j/k or arrow keys) to find what you're interested in
  • View the entire article text inline, or in the context of the site where it was created

See the blog post at Evolving Web

Evolving Web