Our first step is to clearly define your project’s high level goals and to provide direction for all subsequent phases of development. This information becomes the foundation of your project’s creative brief.
A good creative brief is no more than a few pages, or slides, in length and describes the strategic objectives of your project. It will then go on to address important issues such as the project’s relevant background, audience, desired tone, message, restrictions, milestones, schedule and budget. The final and possibly most important section is how you define and plan to measure the project’s success.
If you are able to provide the information we need to complete your creative brief, the time invoiced for this work can be minimized. If not, we can assist in flushing out the necessary details. Before moving on, all stakeholders will be asked to formally approve the final creative brief.
Using the creative brief as our guide, the next step is to structure your content and/or data models, depending on the nature of your project.
Site maps are essentially hierarchical outlines used to describe the structure of content driven websites. For web applications, ERDs (Entity-Relationship Diagrams) depict the data or information that will later be implemented as a relational database.
Whether your project is simple or complex, thinking though its structure is a critical aspect of success. Documenting structure flushes out details that otherwise might be overlooked and ensures all parties share a common vision before moving forward. In the end, this effort saves a great deal of time and money.
For projects that require new content, this is our typical production process. If all content has been provided, then we move on to the “Construct” phase further below.
Review existing content and outline what needs to be created.
Capture information, facts, quotes and resources that support the primary and secondary messages.
Now we are ready to write copy and structure pages with relevant components, such as subheadings, lists and links.
Because most people only scan over websites until something catches their eye, visually engaging images are critical. Once the copy is ready, we then look for ways to visualize its message.
Feedback is gathered from stakeholders and based on this input, content is refined. Edits are tracked and communicated. Several iterations may take place to sculpt the content into its final form.
The revised content is reviewed and approved by stakeholders cited in the creative brief.
We begin by converting your project’s structure into a visual layout for small devices like smart phones. Then we move up to tablet-size layouts and finally wide desktop displays. This Mobile First design process encourages prioritization and leads to more effective user interfaces on all devices.
Once the layout is established, we turn our attention to the color palette, typography, animations and other styling details. If more advanced interactivity is desired, it is normally done after all other aspects of the prototype have been worked out.
If your project is a site, the next step is to build out production ready code by producing clean, semantic markup and removing unnecessary styles and scripts. We then help your site load faster by minimizing HTTP requests and compressing the final code plus supporting assets.
If your project is a web application, the prototype is built into database models, view templates and application controllers. This is known as an MVC (Model-view-controller) software architectural pattern. Learn more about the web technologies Cascading Media employs.
Look no further than the initial rollout of healthcare.gov for an example of management overlooking, ignoring or misunderstanding the need to test. We do not want this to happen to your website, which is why testing is such an important part of our process.
Because Cascading Media produces prototypes that web browsers understand, we are continuously testing large portions of code very early in the process. For web applications, Test-driven development (TDD) practices are used when appropriate and practical.
Before your new site can be released to the public, the codebase must be deployed to production web server(s). Web applications also require a database, application server and possibly load balancers to function. Cascading Media has the capacity to handle this for you via our Cascading Cloud service.
Search Engine Indices
To ensure no search engine traffic is lost, legacy URLs from your old website will be redirected to the most appropriate URL on your new website. For performance reasons, we recommend configuring these redirects through Nginx and not the web application itself.
The Address records of a domain control where requests are directed across the public DNS (Domain Name System). Updating the Address records will redirect public traffic to the new server and your website is live! Email is controlled by the domain’s MX (Mail Exchanger) records and should be handled by a separate server.
After your new website is live, Cascading Media is still here for you. At a minimum, we schedule time to review security patches that might be required for either your web server or application code. We also maintain a development copy of your website to test new features and improvements before applying them to your pubic website.