Skip to content

Project Standards

In an effort to avoid assumptions by either party on projects we have created Project Standards. This is a list of fallback values we will use should you not specify to us.  This list is reviewed twice annually and maintained in line with common industry practices.

Browser Compatibility

Project Standards

Breakpoints for responsive design

Large Desktop 1405px and above
Standard Desktop between 1100px and 1405px
Laptops and Large Tablets 980px and 1100px
Tablets 768px and 980px
Smartphones and small Tablets 320px and 768px
Smartphones 320px and 480px

Design Methodology

For B2C and D2C:

We employ the Atomic Design Method and focus on a Mobile-First approach.

This means unless specified we will design the mobile experience first and then build the desktop experience second.

For B2B:

We employ the Atomic Design Method and focus on a Desktop-First approach with Mobile for SEO focus

This means unless specified we will design the desktop experience first and then build the mobile experience second whilst ensuring that search engines detect the relevant items required on mobile but the physical user is given lower priority on mobile devices.

Absence of Desktop Designs

In the absence of Desktop Designs or Mockups, the Mobile Designs will be expanded in their natural page order left to right to utilise the screen width.

Rixxo at their discretion and using their experience will utilise columns

Colours, Fonts, and Styles will be drawn from the Mobile Designs

N.b. In the absence of Desktop Designs requests for changes to the Final Version will be considered Out of Scope and may incur additional charges or result in other items being dropped from the sprint.

Absence of Mobile Designs

In the absence of Mobile Designs the content will be entered into the Theme CMS in a logical top to bottom order typically  Image > Title > Text > Button to facilitate easy scrolling of the elements.

A single column approach will be taken.

Colours, Fonts, and Styles will be drawn from the Brand Guidelines

N.b. In the absence of Mobile Designs requests for changes to the Final Version will be considered Out of Scope and may incur additional charges or result in other items being dropped from the sprint.

Absence of Brand Guidelines

In the absence of Brand Guidelines Rixxo in order will:

  1. Ask the client to confirm a colour palette for primary, secondary, tertiary and body colour;
  2. Ask the client to choose a theme colour palette from any pre-configured settings;
  3. Utilise the primary, secondary, tertiary and body colour from an existing website or digital asset of the client;
  4. Apply an appropriate scheme of our choosing

N.b. In the absence of Brand Guidelines requests for changes to the Final Version will be considered Out of Scope and may incur additional charges or result in other items being dropped from the sprint.

Coding Standards

Rixxo uses a defined set of coding standards and these are documented in our engineering space. We’re happy to share them with you if you would like to see a copy but they are pretty boring to most.

A good summary is:

  • We follow DRY principles
  • We follow Magento Coding Standards for eCommerce PHP Projects
  • We follow AirBnB styles for Javascript based packages
  • We use linting tools
  • We follow Googles model for code reviews

Project Management Methodology

Placeholder Content

When content is not provided or provided in time Rixxo shall use placeholder content to demonstrate visual styles. As most designs are responsive they change height and width around the content. It is always advantageous to prepare your content before the build.

Our top tip for content is to do it in a plain document. Say the things you need to say to make the sale, show the pictures you need to make the sale. Let the web designers make it look pretty.

Shoehorning content into a template is difficult and demotivating and encourages website managers to add superfluous content that can be detrimental to conversion.

Pages, Products, Categories and more

In the absence of the complete content before the Demonstration Phase, we will use placeholder text as defined below to create the designs.

In the absence of the complete content before the Production Phase, we shall use the same content as presented in the Demonstration Phase.

Text

Rixxo will generate Lorem Ipsum text.

Images

An image can dramatically change the look of a page. To avoid poor quality images or image preference of individuals skewing feedback;

A grey image placeholder text will be used at the templated appropriate size.

OR

The image used in the initial design mockups or theme will be used.

https://placeholder.com/ is a great way to generate images that meet this criterion as it also lets the new site owner know the correct size of the image to use.

Data Sets

To ensure successful testing Rixxo will have created or will create a small data set to meet the acceptance criteria. If you’re “live” data set has not been provided by the deadline this dataset will be left in place for your review.

Products

In the absence of a final product catalogue, Rixxo shall use a demo data set of simple products.

Links

In the absence of a final destination URL for an item that is indicated as a link including menus, footers and call to action the final destination URL will be entered as “#” thereby activating the element as a clickable link but not fully functioning.

The “#” will be editable by the client within the CMS and the failure or redirection of the link will not be recognised as a bug or test failure.

OR

Where it makes reasonable sense to do so the element intended to be linked shall be omitted in the absence of a destination.

Legal

Rixxo is unable to provide legal advice including that of Privacy Policies, GDPR, Terms & Conditions etc and any templates or documentation provided is made without Guarantee or Warranty.

If we do not have a template available the item will be treated as Text and replaced with Lorem Ipsum.