CUSTOM-CODED WEBSITES

You care about the details and want it done right...so do we!

A custom-coded website is an amazing thing and we know you need to make sure we understand what you want and deliver a site that exceeds your expectations.

WHAT IS "BACK-END" DEVELOPMENT?

Wix is a powerful website building platform that utilizes "visual design" to create professional and beautiful websites, but what you don't see is a powerful back-end system that powers it all.

Wix now offers "Wix Corvid" to provide database and dynamic customization to a site that reaches outside of what Wix's "visual-build" platform.

The “back-end," Wix Code (Corvid) is written to connect the information on your web pages that the site visitors see to the data that is stored in databases; the "back-end" that site visitors do not see or have access to.

Front-End

Back-End

THE PROCESS

With decades of project management experience, we know that the key for a successful project is in accurately defining the who, what, when, where, why, and how of what you’re needing.  This information is captured in detailed “Requirements.” 

We want to prevent project failures and build requirements to prevent: 

Of equal importance, the “Requirements” are the basis for how we quote the project​​.

Missing
Requirements
Ambiguous
Requirements
Incomplete
Requirements
Conflicting
Requirements
Duplicated
Requirements

DEFINE YOUR PROJECT

  • This is generally a paragraph that describes the high-level functionality you’re wanting the dynamic database-driven website to perform

  • This doesn’t have to be in great detail but should be detailed enough to build the project requirements

  • If the project is to include “front-end” work (that’s what site visitors see when they come to your website), that needs to be articulated in the Project Definition

    • The project would be quoted to include the additional work needed to build the website and then apply the backend coding to connect the website to your data

NOTE:

For simple, small projects like adding a “filter” to an already existing list on your website, the following steps are not needed.  We will simply include the details of the work in the invoice as part of Step 3 below.  Payment of the invoice indicates acceptance of the definition of work to be done.  However, if what is being requested is more complex in nature, the following step is needed​​

DEFINE YOUR REQUIREMENTS

This is generally a paragraph that describes the high-level functionality you’re looking for the dynamic database-driven website to perform​.

Project Requirements are a bulleted (or numbered) list of what work needs to be done for both the front-end and back-end parts of your website.

Here is an example of the high-level requirements that will be created and serve as the “punch-list” of all the work that is to be done on a website:​​​​​

  • Home Page

    • A blank website page with a very minimal design will be created that will include:

      • Business name/logo (if any)

      • Information about the site

      • A way for visitors to become “members” of the site

  • Site Membership

    • Any page requiring the site visitor to be a site member will require membership

    • If the site visitor is not a member of the site

      • They will be prompted to “Sign-Up”

    • If the site visitor is a member but not yet logged in

      • They will be prompted to “Log In”

  • Messages

    • Members will be able to send and receive basic messages from one member to another

      • Basic messages include:

        • From

        • To

        • Date Sent

        • Text message

        • Messages should be able to be deleted by sender or receiver of the message​

PROJECT EXECUTION

  • To kick off the project, an invoice will be sent.

  • Please refer to payment terms in our Terms of Service

  • Once the invoice is paid, the work as defined in the Invoice or in the Project Requirements will begin.

  • If the site is developed on the client’s site, “Contributor” access and Admin privileges need to be granted to hello@MelanieEdwardsDesigns.com​

USER ACCEPTANCE TESTING

Once the work is completed (or with more complex projects, certain functionalities are completed), the client will be asked to test what is completed and give their approval if no bugs are found

  • Any bugs found are documented in an email and addressed immediately

  • This will continue until there are no additional bugs found

  • Note: discovery of new requirements at this Step does not constitute a bug, but rather needs to follow the change order process​​

PROJECT CLOSURE

Once all requirements are completed and outstanding bugs are found, the project is considered “closed”

  • If project site work is performed on MelanieEdwardsDesigns.com, ownership of that site will be transferred to the client

  • If project site work is performed on the client’s site, please remove “Contributor” access granted to  hello@MelanieEdwardsDesigns.com as part of Step 3 above​​

CHANGE ORDER PROCESS

It’s important to note that anything NOT explicitly included in the Project Requirements is explicitly not considered to be part of the quoted amount for the project and therefore out-of-scope for the work to be done

For any new requirements that are discovered during the project, a project change order will be created to amend the Project Requirements to include the new requirement for an agreed additional fee

CONTACT US

General questions can be sent to hello@melanieedwardsdesigns.com or via the form below.

 

If you would like a custom-quoted price for your site, please complete the Website Application.

 

Have a straightforward build? 

Purchase a custom site from our online store!  You will be prompted to complete a custom-build form after purchase.

VISITORS & CLIENTS FROM AROUND THE WORLD

As Of 9/27/19

MED LOGO.png
  • Melanie Edwards LinkedIn
  • Melanie Edwards Facebook

Tampa, FL USA

Monday - Friday, 10-4 PM, EST

© Melanie Edwards Designs LLC | All Rights Reserved

MED LOGO.png