[Services] [META] – Create landing pages for our Services

[zufrieden]

Enhance our services pages to convert !

Actual structure

1. Intro block
2. Deliverables
3. Block to switch to another service
4. Our last featured project (no matter what skills)
5. Our featured client logo (Toooo long list already addressed here #246)
6. Call to action

   Desired structure

7. Intro block
8. More details about the service (could be illustrated with icons, I'm looking at you @guillaumeberry)
9. Call to action to contact us
10. Project concerned to this particular service
11. People concerned to this particular service (good idea no ?)
12. Call to action to contact us
13. Articles concerned to this particular service
14. Block to switch to another service

    Actual URL's

/fr/nous/faisons/du-design /fr/nous/faisons/de-la-strategie-digitale /fr/nous/travaillons/les-technologies

[zufrieden]

@KidValdez @gido WDYT?

[zufrieden]

Open question on that topic @tonifisler @gido ... Should we have a content type for this ? Should we change skills taxonomy to handle an intro, detail on deliverable list ? We can set a hierarchy on them. So group skills by service and then imagine a landing page per skills regrouping concerned project, articles and people. See Strategy, Design, Technology as meta skills /fr/skills/backend become /fr/skills/technology/backend

[gido]

I like the idea of hierarchy in skills, this should solve some issues about the landing page.

I'm validating 1, 2, 3, 4, 6, 7, 8.

I'm not really sure about the point 5. People concerned to this particular skill/service (is designer will all have all "design" skills ? is developper will all have "web application development skill" ?). What if someone have only notion of a skill ?

[gido]

FYI, this is what I have in local just by using the description field of a skill (and putting raw html in it):

[Saniha]

So...... Who's validating what? @gido I saw your words. @KidValdez What do you think??

[KidValdez]

Comme Gilles je valides: 1, 2, 3, 4, 6, 7, 8.

Le point 5 n'ai pas essentiel.

[zufrieden]

Good merci

un début de hierarchy

-> @guillaumeberry on aurait besoin d'une maquette

[ludovicrenevey]

Hi @KidValdez, @gido, @zufrieden, @Saniha !

We have now the structure of the "Expertise" template (second level) as you validated it :

1. Intro block
2. More details about the service (icons)
3. Call to action to contact us
4. Project concerned to this particular service
5. Call to action to contact us
6. Articles concerned to this particular service
7. Block to switch to another service

I would add the technology we use as a distinct part of the template. LIIP does it that way and I think it is a good idea. What is your opinion ?

Concerning the first level, the page of our 3 services (stratégie, design, technologie), how should we design it ? Here is one proposal :

1. Intro
2. Teaser of the expertise (title, icon, summary, technologies we master)
3. Articles concerned to all expertises of the service in question

[tonifisler]

Taxonomy term pages are our services.

• [x] Add fields to Skills taxonomy
  • Description ✔︎ (ckeditor and all the fuzz)
  • Images (to insert in ckeditor)
  • Quote
  • SVG icon (currently image field, must be changed to file field)
• [x] List related projects
• [ ] List related people
• [ ] List related articles (last 2 or 3)
• [ ] Block to go to other services (on hold for now)

URL pattern: /fr/skills/frontend

[tonifisler]

We still want to display the siblings and other skills at the bottom of the skill page. cc @guillaumeberry