Design et développement d'un site web avec react

Je parle parfaitement francais mais j'ai redigé cette annonce avec mon responsable technique qui est anglophone. Afin de ne pas perdre du temps a la traduire, je la mets directement en anglis.

Ideally you are both able to DESIGN and develop ONLY THE FRONT END of a website with REACT and the word press back end.
You are, optionally, also able to use relay and GraphQL to wire up front end and back-end. If it is not the case, you can still apply to the job, a back end developer will do it.
Front end will be in react and back end will be word press (Text and image management) and GraphQl (Management of things which come from)

V1 - Corporate website only
V2 - Simple feature from a mobile application made in react native
V3 - Complex features from a mobile application made in react native
Project should be done in less than a month!
Web site should be responsive and connected to google analytics

IN YOUR ANSWER, DO NOT COPY PAST A TEXT AS AN ANSWER BUT:
1. Give me MAXIMUM 3 clickable links of website you have done with react and indicate if you managed the design with it
2. Give me your availability percentage for the following next weeks

Development Strategy:
The provider understand that he will use our bitbucket to create repository and pull requests as soon as possible (Strategy described below). Design should be validated prior development.
The back-end is out of scope. While the back-end is being developed, the provider will work according to the following way:
• React
• Redux
• Build Presentational components entirely
• The container components should return data from Relay or wordpress)
• Use eslint-config-airbnb coding standard and enforce it as much as possible, every exception must be clearly explained
• Write tests
• DON'T have any state in the components, use the Redux store, it it's data you can pass dummy data from the container components to the presentational components
• The code should run for all browser
• Of course use ES6+ and React components as Classes
• Always define types and requirements for the components' props
• End-to-end tests are mandatory
For team work and code review you will work in the following way:

Branching

In order to always have a working version of the code, no commits should be done on master. The general workflow we would like to have is
- Have one branch per feature
- When a feature is done, the developer creates a pull request
- The pull request is reviewed by peers and suggestions are made if there is something that should be changed
- Tests are run by continuous integrations servers to ensure that this new feature does no break any tests written before this feature
- When everything is fine the branch is merged

Committing

In order to make the git history clear and help code reviews, commits:
- Should be as as atomic as possible (ie. as often as possible), it is possible to commit even if a feature is not fully done, it does not matter since every work is done on a separate branch. 10 commits per day minimum.
- They should have a small title (It should respect the linux kernel convention to be less than 70-75 chars)
- They should have an extended description (wrapped at 72 characters per line)
- Generated code / code from external projects (ie. the code from react native starter kit), and Sportunity code, should not be in the same commit

Do not use colors directly in stylesheets instead of using the /src/theme/colors file
Do not put images directly in code but use the file src/theme/images.js

Pull requests and commits won’t be considered if:
1. You do not make one commit per functionality. Otherwise review is impossible.
2. You do not separate containers and presentation. Otherwise future evolution will be too complicated.
3. Commits are not properly named to ease review from Guillaume and other developers.
4. Driven tests are, as much as possible, not made.
An example of a proper commits development is provided in our bitbucket account (made per Guillaume) and the provider must respect the code style and standards.
Every end of day between 18:00 and 19:00 you will have to:
• Create a pull request
Provider must keep a constant communication with technical and no-technical project managers.

Planning:
Provider must communicate a planning estimation before starting the project.
Communication:
No information and/or communication should be made without a written agreement. This contract is governed by the NDA that you will have to signe prior to the project start.