Development · integration · reverse engineeringOstwald · Alsace · Remote projectscontact@dtouch.fr
03 88 66 14 39
EN
Dtouch · Solutions digitales
Websites · catalogue · continuity

Maintenance WordPress and PrestaShop in Strasbourg

Recapture, maintain and develop a site WordPress or PrestaShop : diagnostic, working copy, catalogue, contents and integrations with Dtouch.

Public example of site and catalog; the controls and the method are defined according to each project.

Public example of site and catalog; the controls and the method are defined according to each project.

Understand the site and its uses

A site lives with its catalogue, forms, contents and the people who update them. Before a development WordPress or PrestaShop, we examine the existing structure, extensions, theme and functions on which the activity depends. A connection problem, a product sheet or an exchange with commercial management requires a suitable diagnosis: the first job is to locate the need.

Preparing for an evolution without losing the existing work

Depending on the perimeter, a working copy can be used to prepare the theme, categories or specific developments by keeping the reference site. Backups and return points are defined prior to intervention. Monitoring of CDM Œnologie documents an organization between developer, content team and graphic designer, with the provision of a clone and reception confirmed by the client in 2024.

Linking content, catalogue and business tools

The site's technique must remain understandable for its contributors. We can work on categories, product imports, documents, forms or integration with an ERP. The connection with a third-party connector is prepared with its editor: the versions, the directions of exchange and the expected controls are specified. Each function is distinguished from developments still under study.

Planned audits and relay

The tests concern the paths actually affected: connection, reading, search, contact request or order preparation depending on the project. The support arrangements are determined according to needs. Cloudlab completes the hosting and data center component; Agedis intervenes when the problem concerns systems, stations or user access. This breakdown helps track an incident beyond the single visible page.

Your questions

Should we redo the site to make it evolve?

Diagnosing the existing situation makes it possible to distinguish between a correction, a targeted development and an overhaul. The solution depends on the uses, technical constraints and possibilities of maintaining the site.

Can you work with our graphic designer or publisher?

Yes, the preparation of the site can involve contributors, the graphic designer, the host and module specialists. Responsibilities are clarified with project stakeholders.

Understand and prepare

A maintenance plan built on the functions of your site.

A shop, a professional catalogue and an institutional site do not maintain themselves in the same way. The diagnosis must link the versions, contents and paths that matter to the activity.

Qualify the request with a reproducible example

We start from the address of the page, the action performed and the expected result. The browser, account used, and when the problem appears give context to the diagnosis. A form that does not complete, a missing image in a language or a file that is impossible to save calls for different checks. This qualification makes it possible to distinguish the content, the theme, a module, an external exchange and the hosting base before choosing the correction.

Develop a copy with contributors

The working copy makes it possible to discuss an evolution while keeping the reference site. The follow-up of CDM Œnologie in 2024 illustrates this organization: provision of a clone, work on a child theme and coordination with the client and the project contributors. In a new file, we define the content to be included, the access and the way to report the validated modifications. The graphic designer keeps her place in the preparation of the presentation and page models.

A recipe adapted to what changes

The controls are chosen based on the correction. For a catalog, this may involve searching for a reference, filtering a category, consulting a document and checking a file in each language concerned. For a store, the tests add the order stages affected, with suitable testing resources. The forms are checked with their recipients. The list of tests and any reservations make it possible to decide whether to put them online and to organize the rest.

Items submitted for follow-up

Depending on the perimeter, the maintenance file includes the diagnosis, the modifications made, the useful versions and the checks performed. It identifies the remaining topics and the expected decisions: module replacement, content contribution, or editor intervention. Accommodation needs are shared with Cloudlab ; problems of post or access are oriented towards Agedis. You can then find the context of an intervention and prepare the next one without starting from scratch.

Your access and documents

Your codes and diagrams are at your disposal.

The access codes to your applications and environments dedicated to you, the working diagrams and the documentation that we establish are at your disposal. You keep the useful elements to understand your tool and organize the rest with the participants of your choice.

Expertise that complements each other

The right skills for the rest of your project.

Let's start from your situation.

Describe the tool, the people involved and what you want to improve.

Exchange on your project

Complementary expertise, the same high standards.