To design, build and implement websites and other internet solutions, we use a straight forward project methodology consisting of five stages with clear goals and deliverabless. In the early stages of the project we invest in a transparent description of the project requirements, scope, deliverables and roles & responsibilities. This allows us to adapt flexibly to your needs and to keep additional development costs to an absolute minimum.

Our projects consist of five predefined stages with clear goals and deliverables. We can you with our dedicated expertise at each of these stages. However, parts of the core process, such as the graphic design, project intake or content migration may also be delegated to external service providers. Contactivity can assist you in selecting external service providers from our own network, or manage providers that have been selected by you.

Phase 1: Defining the project
1. Project intake (communication strategy, audience profile, functional requirements);
2. Project plan (objectives, scope and constraints, deliverables, planning, roles, budget);
3. Technical intake (content management system, content class definitions, extensions);

Phase 2: Designing the visual interface
1. ‘Wire framing’ of the homepage, landing/index pages and content pages;
2. Graphic designs for the homepage, landing and content pages and various design elements;
3. Conversion of the graphic designs to HTML.

Phase 3: Developing the site structure
1. System installation and configuration;
2. Content migration / implementation; and
3. Training.

Phase 4: Build and integrate
1. Template development;
2. Backend development;
3. Integration with other applications; and
4. Testing.

Phase 5: Launch & Beyond
1. After-sales support; and
2. Project evaluation.

Phase 1: Defining the project

The project intake
The project intake marks the start of our involvement in the project. During these meeting(s) we discuss relevant issues like objectives, expectations, communication strategy and audience(s), (functional) requirements and project constraints. The outcomes of these meetings help us to define information gaps, required expertise and the project roles and responsibilities. It also enables us to advice on how to proceed with next steps.

The project plan
The project plan provides the actual project setup. It describes the project objectives, scope, constraints, deliverables, roles and responsibilities, communication, timelines and milestones and budget allocation. Formal approval is needed before we are able to continue with the technical intake.

Technical intake
The technical intake serves as a tool to clarify the exact scope of the project. What are the project boundaries from all angles, milestones, technical needs, and overall size (as clearly defined as possible with existing knowledge). The technical intake report contains information about the setup of the server and the content management system, the content structure (sitemap), the content class model, the templates, required extensions, workflows and permissions, etc.

Phase 2: Designing the visual interface

Visual interface design
The design of the visual interface starts with ‘wire frames’, a basic visual guide which displays the layout and position of the various design elements in the interface design. The wire frames for the homepage, index or landing pages and the content pages are then passed on to the graphic designers, together with a design brief. We do not have graphic designers on its staff but can assist our clients in selecting or supervising a design bureau. Once the graphic designers have delivered the design, the files are passed on to the front-end developers, who will code the cross-browser compatible HTML.

Phase 3: Developing the site structure

System installation and configuration
The hardware needed to run websites based on content management systems (CMS) depends on several factors, such as the average number of users, the size of the templates (including graphics), and how caching is used. The system installation and configuration includes the following steps: installing the applications required by the CMS, such as MySQL, PHP and Apache, installing and configuring the content management system, benchmarking of server performance, and setting up server-side caching.

Content migration / implementation
Content migration and implementation can be started in parallel to the web development cycle. Due to the strict separation of content, design and functionality in the eZ publish content management systems, content editors are normally able to work in parallel with the web developers. This approach allows considerable reductions in implementation time. Content editors will be jump started by a short introduction course, and support for the editors will be available during this stage.

Documentation and training
Two types of training are available:
1. A content management training for web editors and other content suppliers. This training provides all skills to manage and implement new content using the content management system. The training takes two days: an initial introduction and a follow-up training after one month.
2. A two day technical training of the IT team is sufficient to cover subjects to be able to perform technical maintenance of the site and making small adjustments to the content management system and the templates.
We make tailor-made user and technical manuals upon request.

Phase 4: Build and integrate

Web development
Web development starts after completion and approval of the project plan and the technical intake. The development cycle has three deliverables:
1. alpha version, all core CMS functionality implemented, default templates set up;
2. beta version, functionality (extensions) and design (templates) completely implemented;
3. final version, complete solution after beta bug fixing , all content included.

Phase 5: Launch & Beyond

After-sales support
Warranty and support: After delivering the final version an agreed warranty period starts which allows for free bug fixing. Based on the client’s needs a custom support contract can be arranged.

Project evaluation
Evaluation: typically there is an evaluation and review meeting three months after delivering the project. In this meeting together with our clients we evaluate the new website and its performance and, if necessary, define next steps for improvement or further development.