Turning complexity into clarity.

Improve PageSpeed Insights to above 90 - Upwork

WordPress Work From UpWork - Fri, 11/30/2018 - 01:05
+ Wordpress site
+ 2 different themes
+ Page size about 1.2M
+ Current PageSpeed Insight Score: 58%
+ Need to improve this score to green
+ I already have premium plugin (WP Rocket) to optimize the site (cache, minify JS, CSS...). Below is the "Passed Audit" part:

Passed audits
13 audits
Properly size images
Defer offscreen images
Minify CSS
Minify JavaScript
Efficiently encode images
Serve images in next-gen formats
Enable text compression
Preconnect to required origins
Server response times are low (TTFB)
Root document took 140 ms
Avoid multiple page redirects
Preload key requests
Use video formats for animated content
Avoids enormous network payloads
Total size was 827 KB
+ Need the job done within 1-2 weeks.

Please state your experience and quote your price in the application.

Thank you.

Posted On: December 03, 2018 14:41 UTC
Category: Sales & Marketing > SEM - Search Engine Marketing
Skills: CSS, Page Speed Optimization, PHP, WordPress
Country: Singapore
click to apply

IOS App Landing Page on Wordpress - Upwork

WordPress Work From UpWork - Thu, 11/29/2018 - 22:02
We are looking for a developer that can build a modern and savvy IOS app development landing page website with modern css animations. The website will need to be built on wordpress with SEO keyword content in mind while designing.

Please post 3 most recent projects that is similar to this.

Posted On: December 03, 2018 14:41 UTC
Category: Web, Mobile & Software Dev > Web Development
Skills: CSS, Graphic Design, Web Design, Website Development, WordPress
Country: United States
click to apply

Ipad website project - Upwork

WordPress Work From UpWork - Thu, 11/29/2018 - 21:02
I need to develop a site made for Tablets where our staff can login (3 different tiers = Participant, Coach & Facilitator) and access certain documents or material (videos, images, pdfs).
I have the concept map + design and content.
I need this Dec 25th
willing to pay higher But I need someone to deliver final version by Dec 25th
will send documents for a final quote after you apply.

Posted On: December 03, 2018 14:41 UTC
Category: Web, Mobile & Software Dev > Web Development
Skills: CSS, HTML, HTML5, Illustration, JavaScript, PHP, Web Design, WordPress
Country: Canada
click to apply

Wordpress Developer needed to design interior pages using Elementor - Upwork

WordPress Work From UpWork - Thu, 11/29/2018 - 16:32
Must be available on Skype

We need a developer with experience in Wordpress development, and a keen eye for design.

We have a website-in-development on Wordpress using the Elementor page builder. The homepage has been designed, and the site's theme/aesthetic is pretty much set up - we just need to create some well-designed pages using existing content for About, Contact, Services, etc.

We will provide the content and direction.

Posted On: December 03, 2018 14:41 UTC
Category: Web, Mobile & Software Dev > Web & Mobile Design
Skills: Adobe Photoshop, CSS, HTML, Web Design, Website Development, WordPress
Country: United States
click to apply

Jeff Geerling's Blog: Analyzing a MySQL slow query log with pt-query-digest

News from Planet Drupal - Thu, 11/29/2018 - 16:02

There are times when you may notice your MySQL or MariaDB database server getting very slow. Usually, it's a very stressful time, as it means your site or application is also getting very slow since the underlying database is slow. And then when you dig in, you notice that logs are filling up—and in MySQL's case, the slow query log is often a canary in a coal mine which can indicate potential performance issues (or highlight active performance issues).

But—assuming you have the slow query log enabled—have you ever grabbed a copy of the log and dug into it? It can be extremely daunting. It's literally a list of query metrics (time, how long the query took, how long it locked the table), then the raw slow query itself. How do you know which query takes the longest time? And is there one sort-of slow query that is actually the worst, just because it's being run hundreds of times per minute?

Categories: Drupal

Drupal 8 Content Site - Upwork

WordPress Work From UpWork - Thu, 11/29/2018 - 08:13
We are looking for someone to set up a marketing site on Drupal 8. We have a template we'd like to use, however, it currently supports only Drupal 7, so it would have to be ported or an existing Drupal 8 theme modified to match the look and feel (whichever is easier). Link here:


A graphic designer has created the general look and feel based on this, and you can see this in the attached mockups. Pages include:

Home page
Product landing page (almost identical to home page)
Contact form
-    most recent posts
-    category and tag archives
-    individual blog post

Plus some simple text pages:
About Us
Our Mission
Privacy Policy
Terms and conditions

We are developing a web application that is entirely separate from this site, so links such as registration and login go to that site. The only Drupal users will be site administrators.

Other requirements:

-    GDPR cookie usage notification
--        we will have EU customers
-    basic accessibility/ADA compliance (we are U.S. based)
-    SEO best practices
-    Google Tag Manager integration
--        Google Analytics tracker installed

Our previous experience has been with WordPress, but are choosing Drupal because (in a future, separate engagement) we will need some custom Drupal programming to interact with another web application we are building. Therefore, we are treating this as a custom software project from the start and you'll need to follow our development guidelines:

-    We will be hosting the site on AWS. Probably via Elastic Beanstalk, but are open to other options (on AWS).
-    You will commit code to our Bitbucket repo (Git).
--        I understand that Drupal is heavily plugin-based and, for a simple site like this, you may have very little code to commit after initial commit.
-    We track issues via Jira.

When applying, please include:

-    resume or LinkedIn profile of developer(s) who will be performing the work
-    relevant experience with Drupal 8, including links to sites you have completed


Posted On: December 03, 2018 14:41 UTC
Category: Web, Mobile & Software Dev > Web Development
Skills: CSS, Drupal, HTML, PHP, Responsive Web Design
Country: United States
click to apply

Frontend Web Developer - Sengled - Vancouver, BC

NodeJS jobs - Thu, 11/29/2018 - 07:54
Experienced in using NodeJS. Familiarity in other web technologies such as PHP, Ruby on Rails or NodeJS. Sengled Canada is looking for a smart and talented...
From Sengled - Thu, 29 Nov 2018 07:54:11 GMT - View all Vancouver, BC jobs
Categories: NodeJS

Web Programmer - Genome Sciences Centre, BC Cancer - Vancouver, BC

2018 Drupal Jobs from Indeed - Wed, 11/28/2018 - 23:40
BC Cancer’s Michael Smith Genome Sciences Centre has an opening for a Web Developer. Working with other GSC teams, the Web Developer will receive direction and...
From Indeed - Wed, 28 Nov 2018 23:40:26 GMT - View all Vancouver, BC jobs
Categories: Drupal

Graphic design & other web & collateral/document updates for high growth enterprise software company - Upwork

WordPress Work From UpWork - Wed, 11/28/2018 - 23:27
We are a B2B enterprise software company headquartered in Calgary with offices in the San Francisco Bay Area that has created a highly functional General Automation Platform that is used by many of the world's largest corporate and government organizations to automate a very wide range of business processes.

Our current website and other collateral is in great need of updates, both from the content perspective and from design perspective. We need a designer that can take what we have today and create an overall theme that we can use not only on our website, but in many other parts of our organization.  While we are a smaller software company, we compete with the likes of Adobe, Microsoft, SAP, Oracle, etc. and our customers are some of the biggest organiations in the world.  So, simply put - our digital presense needs to look like that of a billion dollar company (but without that budget).

In short, we are looking for a designer that has significant experience doing just that.  Much of the content will be photo-based and while we are generally happy with the stock photography we have used to date, it certainly be significantly improved.  This project will require little to no market research and little to no text writing.  We are quite knowledgeable on that piece, but would welcome input.  Of course, our website renders well in browsers and mobile.   This is primarily a graphics design project, but the output will be used as a theme in many other parts of our marketing.

Deliverables needed:

  - Re-Designed webpage theme (currently uses a modern WordPress template and we likely will keep that, unless there is a compelling reason not to).  This is the most important piece to get right, since many other elements will flow from this theme

- Redesign of primarily home page, and 4 product pages.  All other pages may have minimal content to be changed, but needs to follow the same general design theme

- Multiple graphics to be created in the areas of architecture diagrams, network diagrams, simple but impactful diagrams that relay both simple and complex concepts.   See a few examples attached.  Please note - the attached files are examples pulled from other sites.  I do not own these, but are included as concepts that we find appealing.  They are meant only to provide ideas.  We are not married to these concepts.

- We are writing the text content changes, but are interested in ideas in this area

- We will use some of the existing photographic images, but likely will need more.  So stock photo images, and/or a combination of stock photos with new photos will be needed

- Selection of powerful fonts, colors, sizes, placement is of great importance to us and will be carried over to many other marketing items.

- With the above created theme and other design elements, we would like to have templates created that can be used as the foundation for our datasheet/brochure, templates for other customer-facing documents (probably in .doc) such as Proposals, Order Forms, Whitepapers, Case Studies, etc.  will also be needed

- While this project will not include design of our new datasheet, there is a possibility that once the theme is created that project could be added for the selected designer

Special skills needed for this project:

- This is primarily a design project and we need a very creative designer that can create content with a very modern flair and suitable for our customers, who are large, global organizations

-The software you use is not important except that many of the diagrams will have some elements normally associated with laying out a technical architecture diagram, so Visio on steroids may be needed, but is not required

- We have accounts with Adobe Stock for stock photography, but can consider others

In your proposal, please provide a one- or two-paragraph summary of your design experience and why you'd be a great fit for this work. Also include two relevant samples that show your best design work and creativity.

Posted On: December 03, 2018 14:41 UTC
Category: Design & Creative > Graphic Design
Skills: Graphic Design
Country: United States
click to apply

eCommerce Pro to Guide Setup & Execution of Niche Store - Upwork

WordPress Work From UpWork - Wed, 11/28/2018 - 22:29
I have an existing Wordpress website that needs an ecommerce component built out.  We previously used Woocommerce but it never went anywhere.  Right now the site is simply content with affiliate ads and advertorials.  We are transitioning to Thrive Themes.

The goal is to implement a true store via woocommerce or shopify.  My preference would be for full, automated integration with a drop-shipper(s), but a semi-automated integration might be acceptable as well.

I'm looking for an experienced guru to make recommendations and guide me through this process.  I do have technical staff who can execute, or this could be part of your responsibilities as well.

Central goals include:  recommendation of the platform and identification of the vendors to fulfill orders (drop-shippers).  We do not inventory product and will not entertain that.  

The niche of this site is prepper/survivalist/off-grid products.  

I look forward to discussing this opportunity with you.

Posted On: December 03, 2018 14:41 UTC
Category: Web, Mobile & Software Dev > Ecommerce Development
Skills: Drop Shipping, Ecommerce Platform Development, Shopify, Woocommerce, WordPress, Wordpress Thrive Themes, WordPress e-Commerce
Country: United States
click to apply

UI Engineer - FORESEE - Vancouver, BC

NodeJS jobs - Wed, 11/28/2018 - 21:51
Experience with some of ES6, NodeJS, Express JS, AWS or similar cloud solution. Founded in 2001, ForeSee is the pioneering leader in Voice of Customer (VOC)...
From Glassdoor - Wed, 28 Nov 2018 21:51:53 GMT - View all Vancouver, BC jobs
Categories: NodeJS

Senior Front-end Engineer - MetaOptima - Vancouver, BC

NodeJS jobs - Wed, 11/28/2018 - 21:27
Python/Django, NodeJS, JSON, RESTful APIs, Git, Linux, Gulp, PostgreSQL/MySQL, SocketIO. We are one of Vancouver’s fastest growing startups looking for a highly...
From Glassdoor - Wed, 28 Nov 2018 21:27:45 GMT - View all Vancouver, BC jobs
Categories: NodeJS

Full Stack Senior Web Developer - Real Estate WEbmasters - Nanaimo, BC

NodeJS jobs - Wed, 11/28/2018 - 21:13
JavaScript (ES5, ES6+), NodeJS, Vue.js, webpack. Real Estate Webmasters is a state-of-the-art website vendor, specializing in luxury sites for the world’s top...
From Glassdoor - Wed, 28 Nov 2018 21:13:49 GMT - View all Nanaimo, BC jobs
Categories: NodeJS

Marketing Growth Engineer - Invoice Simple - Vancouver, BC

NodeJS jobs - Wed, 11/28/2018 - 21:09
NodeJS backend in Typescript. Invoice Simple's mission is to build the world's simplest way to run and grow a small business....
From Glassdoor - Wed, 28 Nov 2018 21:09:49 GMT - View all Vancouver, BC jobs
Categories: NodeJS

Lullabot: Lullabot at DrupalCon Seattle

News from Planet Drupal - Wed, 11/28/2018 - 20:54

We're excited to announce that 14 Lullabots will be speaking at DrupalCon Seattle! From presentations to panel discussions, we're looking forward to sharing insights and good conversation with our fellow Drupalers. Get ready for mass Starbucks consumption and the following Lullabot sessions. And yes, we will be hosting a party in case you're wondering. Stay tuned for more details!

AMP (Accelerated Mobile Pages) Re-Imagined

Karen Stevenson, Director of Technology

Karen will talk about the challenges of the original Drupal AMP architecture, changes in the new branch, and some big goals for the future of the project.

Autopsy of Vulnerabilities

Zequi Vázquez, Developer

Zequi will explore Drupal Core vulnerabilities, SA-CORE-2014-005 and SA-CORE-2018-7600, by discussing the logic behind them, why they present a big risk to a Drupal site, and how the patches work to prevent a successful exploitation.

Design a Decoupled Application - An Architecture Guide Based Upon the Drupal Admin UI

Sally Young, Senior Technical Architect (with Matthew Grill, Senior JavaScript Engineer at Acquia & Daniel Wehner, Senior Drupal Developer at Chapter Three)

Discussing common problems and best practices of decoupled Drupal has surpassed the question of whether or not to decouple. Sally, Matthew, and Daniel will talk about why the Drupal Admin UI team went with a fully decoupled approach as well as common approaches to routing, fetching data, managing state with autosave and some level of extensibility.

Drupal Admin UI

Sally Young, Senior Technical Architect (with Lauri Eskola, Software Engineer in OCTO at Acquia; Matthew Grill, Senior JavaScript Engineer at Acquia; & Daniel Wehner, Senior Drupal Developer at Chapter Three)

The Admin UI & JavaScript Modernisation initiative is planning a re-imagined content authoring and site administration experience in Drupal built on modern JavaScript foundations. This session will provide the latest updates and a discussion on what is currently in the works in hopes of getting your valuable feedback.

Enterprise Content Inventories

Greg Dunlap, Senior Digital Strategist

Greg will take you on a tour of the set of tools we use at Lullabot to create predictable and repeatable content inventories and audits for large-scale enterprise websites. You will leave with a powerful toolkit and a deeper understanding of how you use them and why.

Front-end Web Performance Clinic 2019

Mike Herchel, Senior Front-end Developer

If you're annoyed by slow websites, Mike will take you on a deep dive into modern web performance. During this 90 minute session, you will get hands-on experience on how to identify and fix performance bottlenecks in your website and web app.

How DevOps Strengthens Team Building

Matt Westgate, CEO & Co-founder

Your DevOps practice is not sustainable if you haven't implemented its culture first. Matt will take you through research conducted on highly effective teams to better understand the importance of culture and give you three steps you can take to create a cultural shift in your DevOps practice. 

How to Hire and Fire Your Employer

April Sides, Developer

Life is too short to work for an employer with whom you do not share common values or fits your needs. April will give you tips and insights on how to evaluate your employer and know when it's time to fire them. She'll also talk about how to evaluate a potential employer and prepare for an interview in a way that helps you find the right match.

Layout Builder in the Real World

Karen Stevenson, Director of TechnologyMike Herchel, Senior Front-end DeveloperWes Ruvalcaba, Senior Front-end Developer, & Ellie Fanning, Head of Marketing

Karen, Mike, Wes, and team built a soon-to-be-launched Drupal 8 version of Lullabot.com as Layout Builder was rolling out in core. With the goal of giving our non-technical Head of Marketing total control of the site, lessons were learned and successes achieved. Find out what those were and also learn about the new contrib module Views Layout they created.

The Imaginary Band of Drupal Rock Stars

Matthew Tift, Senior Developer

The words "rockstar" and "rock star" show up around 500 times on Drupal.org. Matthew explores how the language we use in the Drupal community affects behavior and how to negotiate these concepts in a skillful and friendly manner.

Using Personas as an Inclusive Design Tool

Helena McCabe, Senior Front-end Developer (with Carie Fisher, Sr. Accessibility Instructor and Dev at Deque)

Helena and Carie will examine how web accessibility affects different personas within the disability community and how you can make your digital efforts more inclusive with these valuable insights.

Diversity & Inclusion: Building a Stronger Drupal Community

Marc Drummond, Senior Front-end Developer Greg Dunlap, Senior Digital Strategist (with Fatima Sarah Khalid, Mentor at Drupal Diversity & Inclusion Contribution Team; Tara King, Project lead at Drupal Diversity & Inclusion Contribution Team; & Alanna Burke, Drupal Engineer at Kanopi Studios)

Open source has the potential to transform society, but Drupal does not currently represent the diversity of the world around us. These members of the Drupal Diversity & Inclusion (DDI) group will discuss the state of Drupal diversity, why it's important, and updates on their efforts.

Why Will JSON:API Go into Core?

Mateu Aguiló Bosch, Senior Developer (with Wim Leers, Principal Software Engineer in OCTO at Acquia & Gabe Sullice, Sr. Software Engineer, Acquia Drupal Acceleration Team at Acquia)

Mateu and his fellow API-first Initiative maintainers will share updates and goals, lessons and challenges, and discuss why they're pushing for inclusion into Drupal core. They give candy to those who participate in the conversation as an added bonus!

Personalization for the Perplexed

Jeff Eaton, Senior Digital Strategist

Personalization has become quite the buzzword, but the reality in the trenches rarely lives up to the promise of well-polished vendor demos. Eaton will help preserve your sanity by guiding you through the steps you should take before launching a personalization initiative or purchasing a shiny new product. 

Also, from our sister company, Drupalize.Me, don't miss this session presented by Joe Shindelar:

Gatsby & Drupal

Joe will discuss how Gatsby and Drupal work together to build decoupled applications, why Gatsby is great for static sites, and how to handle private content, and other personalization within a decoupled application. Find out what possibilities exist and how you can get started.

Photo by Timothy Eberly on Unsplash

Categories: Drupal

iOS Software Engineer - Invoice Simple - Vancouver, BC

NodeJS jobs - Wed, 11/28/2018 - 20:50
NodeJS backend in Typescript. Want to join one of Canada's fastest growing startups?...
From Glassdoor - Wed, 28 Nov 2018 20:50:40 GMT - View all Vancouver, BC jobs
Categories: NodeJS

Lead Data Scientist - Invoice Simple - Vancouver, BC

NodeJS jobs - Wed, 11/28/2018 - 20:14
Written Typecript and/or Javascript on the backend with NodeJS. Invoice Simple's mission is to build the world's simplest way to run and grow a small business....
From Glassdoor - Wed, 28 Nov 2018 20:14:25 GMT - View all Vancouver, BC jobs
Categories: NodeJS

Dries Buytaert: How Paychex replatformed on Drupal and doubled its website traffic

News from Planet Drupal - Wed, 11/28/2018 - 19:59

One trend I've noticed time and time again is that simplicity wins. Today, customers expect every technology they interact with to be both functionally powerful and easy to use.

A great example is Acquia's customer, Paychex. Paychex' digital marketing team recently replatformed Paychex.com using Drupal and Acquia. The driving factor was the need for more simplicity.

They completed the replatforming work in under four months, and beat the original launch goal by a long shot. By levering Drupal 8's improved content authoring capabilities, Paychex also made it a lot simpler for the marketing team to publish content, which resulted in doubled year-over-year growth in site traffic and leads.

To learn more about how Paychex accomplished its ambitious digital and marketing goals, watch my Q&A with Erica Bizzari, digital marketing manager at Paychex.

Categories: Drupal

Web Developer - BC Cancer Agency - Vancouver, BC

2018 Drupal Jobs from Indeed - Wed, 11/28/2018 - 18:39
BC Cancer’s Michael Smith Genome Sciences Centre has an opening for a Web Developer. Working with other GSC teams, the Web Developer will receive direction and...
From BC Cancer Agency - Wed, 28 Nov 2018 18:39:35 GMT - View all Vancouver, BC jobs
Categories: Drupal

Lullabot: Project Management with GitHub: v2

News from Planet Drupal - Wed, 11/28/2018 - 18:02

At Lullabot, we’ve been using GitHub, as well as other project management systems for many years now. We first wrote about managing projects with GitHub back in 2012 when it was still a bit fresh. Many of those guidelines we set forth still apply, but GitHub itself has changed quite a bit since then. One of our favorite additions has been the Projects tab, which gives any repository the ability to organize issues onto boards with columns and provides some basic workflow transitions for tickets. This article will go over one of the ways we’ve been using GitHub Projects for our clients, and set forth some more guidelines that might be useful for your next project.

First, let’s go over a few key components that we’re using for our project organization. Each of these will be explained in more detail below.

  1. Project boards
  2. Epics
  3. Issues
  4. Labels
Project boards

A project board is a collection of issues being worked on during a given time. This time period is typically what is being worked on currently, or coming up in the future. Boards have columns which represent the state of a given issue, such as “To Do”, “Doing”, “Done”, etc.

For our purposes, we’ve created two main project boards:

  1. Epics Board
  2. Development Board
Epics Board

ex: https://github.com/Lullabot/PM-template/projects/1

The purpose of this Project board is to track the Epics, which can be seen as the "parent" issues of a set of related issues. More on Epics below. This gives team members a birds-eye view of high-level features or bodies of work. For example, you might see something like “Menu System” or “Homepage” on this board and can quickly see that “Menu System” is currently in “Development”, while the “Homepage” is currently in “Discovery”.

The “Epics” board has four main columns. (Each column is sorted with highest priority issues at the top and lower priority issues at the bottom.) The four columns:

  • Upcoming - tracks work that is coming up, and not yet defined.
  • Discovery - tracks work that is in the discovery phase being defined.
  • Development - tracks work that is currently in development.
  • Done - tracks work that is complete. An Epic is considered complete when all of its issues are closed.
Development Board

ex: https://github.com/Lullabot/PM-template/projects/2

The purpose of the Development board is to track the issues which are actionable by developers. This is the day-to-day work of the team and the columns here are typically associated with some state of progression through the board. Issues on this board are things like “Install module X”, “Build Recent Posts View”, and “Theme Social Sharing Component”.

This board has six main columns:

  • To do - issues that are ready to be worked on - developers can assign themselves as needed.
  • In progress - indicates that an issue is being worked on.
  • Peer Review - issue has a pull request and is ready for, or under review by a peer.
  • QA - indicates that peer review is passed and is ready for the PM or QA lead for testing.
  • Stakeholder review - stakeholder should review this issue for final approval before closing.
  • Done - work that is complete.

An Epic is an issue that can be considered the "parent" issue of a body of work. It will have the "Epic" label on it for identification as an Epic, and a label that corresponds to the name of the Epic (such as "Menu"). Epics list the various issues that comprise the tasks needed to accomplish a body of work. This provides a quick overview of the work in one spot. It's proven very useful when gardening the issue queue or providing stakeholders with an overall status of the body of work.

For instance:

Homepage [Epic]

  • Tasks

    • #4 Build Recent Posts View
    • #5 Theme Social Sharing Component

The Epic should also have any other relevant links. Some typical links you may find in an Epic:

  • Designs
  • Wiki entry
  • Dependencies
  • Architecture documentation
  • Phases

Depending on timelines and the amount of work, some Epics may require multiple Phases. These Phases are split up into their own Epics and labeled with the particular Phase of the project (like “Phase 1” and “Phase 2”). A Phase typically encompasses a releasable state of work, or generally something that is not going to be broken but may not have all of the desired functionality built. You might build out a menu in Phase 1, and translate that menu in Phase 2.

For instance:

  • Menu Phase 1

    • Labels: [Menu] [Epic] [Phase 1]
    • Tasks
    • Labels: [Menu] [Phase 1]
  • Menu Phase 2

    • Labels: [Menu] [Epic] [Phase 2]
    • Tasks
    • Labels: [Menu] [Phase 2]
  • Menu Phase 3

    • Labels: [Menu] [Epic] [Phase 3]
    • Tasks
    • Labels: [Menu] [Phase 3]

Issues within Phase 3 (for example) will have the main epic as a label "Menu" as well as the phase, "Phase 3", for sorting and identification purposes.


Issues are the main objects within GitHub that provide the means of describing work, and communicating around that work. At the lowest level, they provide a description, comments, assignees, labels, projects (a means of placing an issue on a project board) and milestones (or a means of grouping issues by release target date).

Many times these issues are directly linked to from a pull request that addresses the issue. By mentioning the issue with a pound(#) sign, GitHub will automatically create a link out of the text and add a metadata item on the issue deep linking to the pull request. This is relevant as a means of tracking what changes are being made with the original request which then can be used to get to the source of the request.

For our purposes, we have two "types" of issues: Epics or Tasks. As described above, Epics have the "Epic" label, while all others have a label for the Epic to which it belongs. If an issue does not have a value in the "Project" field, then it does not show up on a project board and is considered to be in the Backlog and not ready for work.


Labels are a means of having a taxonomy for issues.

We have 4 main uses for Labels currently:

  1. Epic - this indicates the issue is an Epic and will house information related to the body of work.
  2. [name of epic] (ex: Menu) - indicates that this is a task that is related to the Menu epic. If combined with the Epic label, it is the Menu Epic.
  3. [phase] (ex: Phase 1) - indicates this is part of a particular phase of work. if there is no phase label, it's considered to be a part of Phase 1.
  4. bug - indicates that this task is a defect that was found and separated from the issue in which it was identified.
  5. Blocked - Indicates this issue is blocked by something. The Blocker should be called out in the issue description.
  6. Blocker - indicates that this issue is blocking something.
  7. front-end - indicates that an issue has the underlying back-end work completed and is ready for a front-end developer to begin working on it.

There are other labels that are used sometimes to indicate various meta, such as "enhancement", "design", or "Parking Lot". There are no set rules about how to use these sort of labels, and you can create them as you see fit if you think they are useful to the team. Though be warned, if you include too many labels they will become useless. Teams will generally only use labels if they are frictionless and helpful. The moment they become overwhelming, duplicative, or unclear, the team will generally abandon good label hygiene.

These are just some guidelines we consider when organizing a project with GitHub. The tools themselves are flexible and can take whatever form you choose. This is just one recommendation which is working pretty well for us one of our projects, but the biggest takeaway is that it’s versatile and can be adapted to whatever your situation may require.

How have you been organizing projects in GitHub? We’d love to hear about your experiences in the comments below!

Categories: Drupal