# Editorial mission for the boldcode website

## Objective of the mission

The goal of this mission is to help us finalize the website of boldcode. For this, the priority is to write the missing content.

We do not want to change the structure of the site or the pages for the moment. The text will have to respect the proposed structure.

## Context of the mission

For a year we have been working on the new version of the boldcode website.

For budgetary reasons the development has been very slow, and the initial design also limited.

We chose to focus first on the architecture of the pages and content typologies (the wireframe), which allowed us to move forward on the production of the code without having the complete design (the mock-up).

So we developed the code that corresponds to the information architecture, and that allows us to display the different pages, categories, etc.

This part is ready. The real content is missing now.

The graphic style & fonts currently visible on the test site was improvised by the developer and should not be taken into account.

Once we have the content, we will do a "cleaning" pass with a graphic designer to finalize the site.

The development version of the website is avalable on : <https://boldcode.gitlab.io/boldcode-internal/boldcode-site/>

## Scope of work required

### What to write

* Texts for case studies
* Texts for the blog posts
* Annexes content for each service and product

### What needs to be improved

* Texts for the company presentation
* Texts for the company's services
* Texts for the company's products

### And also

* Propose a selection of annexes on each page.

## Content logic: main + annexes

The idea is to facilitate navigation between the different contents of the site and especially to highlight the different products and services that we could sell to the visitor on a given subject.

For this we use a system of "reminders" between the theme of the page or article and related themes.

Thus, each content (presentation page, blog post, use case, etc.) is organized in two parts:

* A main content
* A annex content

The main content is everything that constitutes the information of the presentation, the article, the use case: that is to say the text, the titles, the headings, the illustrations, etc. This main content speaks about a given subject, product, service or theme.

The annex content is the list of information or action most useful to the visitor of the page, and which are related to the main topic.

This annex content is displayed either below the main content (for the mobile version of the site) or to the right of the main content (for the desktop version of the site).

### Example 1: Development of an application

Main content:

* A blog post about the development of an application

Annex content:

* « Have you thought about backing up your data? Regular data backup is the first way to protect your application and your business [:arrow_right: read more] »
* « Will you resist to hackers? New vulnerabilities are discovered every day in existing software and languages. A regular security audit helps you to be prepared for these risks [:arrow_right: read more] »
* « I have an application development project [:arrow_right: contact boldcode] »

### Example 2: Functional and technical scoping

Main content:

* Presentation of the "functional and technical scoping" service

Annex content:

* « Is your project in compliance with the RGPD? If your project collects, transforms or transfers personal data, there are regulatory elements to take into account [:arrow_right: read more] »
* « User experience is the key to building visitor engagement [:arrow_right: read more] »
* « I have an application development project [:arrow_right: contact boldcode] »

## Case study texts

The aim is to present case studies.

Each case-study must include:

* A brief presentation of the client
* The client's context and issues: i.e. the reason, the needs or the problems that led to the project
* The mission: a description of the actions we had to take
* The result of the realization: on the short term, medium term, long term

Each of these parts must be between 450 and 650 characters long, or about 70 to 100 words.

In the future, we will also add a customer testimonial.

### Deliverables

* A case study for each of the projects in the company's portfolio, following the defined structure.

### Exemples

List of case studies: https://boldcode.gitlab.io/boldcode-internal/boldcode-site/use-cases/

Sample case study: https://boldcode.gitlab.io/boldcode-internal/boldcode-site/use-cases/en/use-case-example-1%20copy%202/

## Texts for blog posts

The structure of blog articles content is free.

Themes:

* Any topic related to boldcode services and products
* Ethical issues on the digital
* Critical analysis of various tech topics or products
* Economic and territorial development issues via digital in Nepal and in France

### Deliverables

* Ten blog posts to fill the site at the beginning.
* Length : 5.000 to 15.000 characters each, or about 500 to 2.500 words.
* A calendar of article themes for the next 6 months, at the rate of one article per month.

## Annex content for each service and product

The annex content allows you to link to our services and products. It will appear next to the main content of the articles, at the bottom of the page or in the right margin.

The structure of the annex content for a given service or product is the following:

* A question
* A one or two sentence summary
* One or more calls to action

### Deliverables

* The annex content for each service and product, following the defined structure.

### Example 1: The "RGPD scoping" service

* Question: « Is your project in compliance with the RGPD? »
* Summary: « If your project collects, transforms or transfers personal data, there are regulatory elements to take into account»
* Calls to action:
* « :arrow_right: verify my compliance »
* « :arrow_right: vead more »

### Exemple 2: The "Data Backup" service

* Question: « Have you thought about backing up your data? »
* Summary: « Regular data backup is the first way to protect your application and your business »
* Calls to action:
* « :arrow_right: protect my data »
* « :arrow_right: read more »

List of articles: https://boldcode.gitlab.io/boldcode-internal/boldcode-site/blog/

Sample article: https://boldcode.gitlab.io/boldcode-internal/boldcode-site/blog/en/2022-04-01-post-example-9/

## Texts for the presentation of BOLDCODE

The objective here is to take the texts of the historical presentation of the company (the PDF that we send to every customer), to complete it and to improve it.

### Deliverables

* A text for about us
* A text for our team
* A text for our vision
* A text for our ethical values

Length : 2.500 to 5.000 characters each, or about 250 to 500 words.

## Texts for BOLDCODE services and products

The aim here is to take the existing content of the BOLDCODE catalog and to improve it if necessary.

Each service or product presentation must follow this structure:

* Goals (the problem that we solve / the value we bring)
* Deliverables (what you get)
* Methodology (how we do that)
* Price (starting price, average price)

### Deliverables

* Improved texts for products and services
* Length: existing length (to be determined)

## A selection of annexes for each page.

The idea here is to think about which annex contents would be the most relevant to each main content.

This selection of related content will always be presented next to the main content and followed by an insert allowing the visitor to contact the company for a possible project.

### Deliverables

For each product, each service, each blog post, each case study, you need to identify and propose a list of the 2 or 3 services and products of the company that would be the most relevant.