<?xml version="1.0" encoding="utf-8"?>
<!-- generator="Kirby" -->
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom">

  <channel>
    <title>Mot-cl&#233;: content creation &#183; Blog &#183; Liip</title>
    <link>https://www.liip.ch/fr/blog/tags/content+creation</link>
    <generator>Kirby</generator>
    <lastBuildDate>Tue, 24 Jul 2018 00:00:00 +0200</lastBuildDate>
    <atom:link href="https://www.liip.ch" rel="self" type="application/rss+xml" />

        <description>Articles du blog Liip avec le mot-cl&#233; &#8220;content creation&#8221;</description>
    
        <language>fr</language>
    
        <item>
      <title>Words and the design process, InVision Design Talk, our learnings and readings</title>
      <link>https://www.liip.ch/fr/blog/words-and-design-invision-designtalk-our-learnings</link>
      <guid>https://www.liip.ch/fr/blog/words-and-design-invision-designtalk-our-learnings</guid>
      <pubDate>Tue, 24 Jul 2018 00:00:00 +0200</pubDate>
      <description><![CDATA[<h2>Thanks to Invision, we get a week of free great talks!</h2>
<p>Invision proposed <a href="https://www.invisionapp.com/webinars/designtalks-ux-copy">four talks about UX copy</a>, about process, inclusive UX copy, how UX writers and designers can better collaborate, and how to improve forms with great copy.</p>
<p><a href="https://ux.shopify.com/@bizsanford">Biz Sanford</a> held the first talk. She manages Shopify’s voice and tone, sets content standards, and teaches her workmates how to write their own content.<br />
Her talk was about consistent interface content. It is a core element of a well-designed user experience. She explained how to incorporate content throughout the design process.<br />
Her main advice was to be specific. Any Lorem ipsum text or scribble should be banished from sketching to wireframing.</p>
<h2>My key learnings about Biz inspiring talk</h2>
<h3>Step 1: Sketching</h3>
<p>When sketching, we don’t find the exact words that we will use in the final copy. Our content will go through feedback rounds before it is final. However, we should already chose appropriate words. We should be especially careful with the following components that are key to the functionality:</p>
<ul>
<li>headings for pages and sections,</li>
<li>key verbs and nouns,</li>
<li>buttons and link text.<br />
Words are essential to the user experience, they lead the user to do what they want. Sketching with words will help you have a better overview of what needs to be designed. It is useful to work with a diverse team to gather different words: don’t stick to you own jargon.</li>
</ul>
<h3>Step 2: Wireframing</h3>
<p>Her idea to break down in a table like Googlesheets or Excel all the content elements is most interesting! It makes sure we don’t forget a piece of the scenario. I find it especially useful for multilingual websites. The table provides an overview of the naming of all elements, their translation, and any design needed (like an icon). It can be shared with all team members. It will ensure a consistent naming of the elements in all languages. </p>
<h3>Step 3: Content in low fidelity mockups</h3>
<p>At this stage, we use realistic content and real data. To show that it is not a finalised version of the content, we can use a funny font (like comic sans). It helps every team member understand how it works without too many explanations. We want to gather robust feedbacks on flow and functionality rather than wording or typo.<br />
My favourite advice she gave was to use the wording of your users. You can talk to the team members who have direct contact with your customers for example. I find that a team often uses specific jargons, maybe legal or technical and often does not realise that their users speak a different language. </p>
<h3>Step 4: Content in high fidelity mockups</h3>
<p>At Shopify, the project team organises polish reviews. The team sits together and ‘plays’ with the product to check that everything is right.<br />
It is definitely something I would like to start here at Liip! It’s useful to have team members who did not write the copy doing some re-readings. When we are too focused on our work, sometimes mistakes slip our notice and external advice is the key to go back on track. </p>
<h3>Questions &amp; Answers with Biz</h3>
<p>It was a live talk. Wand we could ask questions and comment. Here is a few themes that came up.<br />
<strong>Content is often dealt with at the end of a project. How to be a strong advocate for content?</strong><br />
Designers are content’s best ally. Designers can encourage to use real content and use it early. People will follow. The usefulness of content is self explanatory when it’s already incorporated in the design.<br />
<strong>Consistency is essential.</strong><br />
Users don’t care that one team did this and another team did that. Consistency builds credibility and trust. A good option is to create a glossary where all team members can contribute. At the best, the glossary is shared with the marketing team too.<br />
<strong>Does the layout fits the content or does the content fits the layout?</strong><br />
Neither! Both of them shape each other, this is why content should be involved as early as possible. Designers and content strategists should collaborate all along the way. </p>
<h3>Further readings on content at Shopify and usefool tools</h3>
<p>If you missed Biz’s talk and my little summary woke your curiosity up, read her blog post <em><a href="https://ux.shopify.com/words-and-the-design-process-f41472a249fb">Words and the design process - Greetings from a friendly content strategist</a></em>. She explains everything with details, sketches and images. The content of this blogpost is very similar to the content of her talk.<br />
The content team at Shopify shares many learnings. <em><a href="https://ux.shopify.com/tagged/content-strategy">Read their blog to learn more on content and design</a></em>.<br />
For example I recommend <em><a href="https://ux.shopify.com/product-content-at-each-stage-of-a-project-55195190d8b5">Product content at each stage of a project - How content strategists help teams build better products</a></em>. The blogpost helps you pinpoint where and when you can add-value in a project.</p>
<p>Julien, who participated to the meet-up wrote a great blog post (in French) to share his personal learnings <em><a href="https://julien-ferla.ch/la-place-de-la-copy-dans-le-processus-de-creation/">La place de la Copy dans le processus de création</a>.</em></p>
<h3>Useful tools to test the readability</h3>
<p>To test the readability of our English content, we can use the Hemingway App.<br />
To test the readability of our German content, we can use the website Psychometrica.<br />
Do you have such a tool for French?</p>
<figure><img src="https://liip.rokka.io/www_inarticle/e04d0e/invision-talk-setting.jpg" alt=""></figure>
<p>Cosy setting to enjoy the talk =)</p>
<h2>Watching the talk together and sharing learnings</h2>
<p>Since it was a remote talk, we created a cosy atmosphere at Liip to have a chance to discuss and share our learnings. I very much enjoyed our evening! Thanks to all participants and my team mates who make fun and projects possible everyday !</p>]]></description>
                  <enclosure url="http://liip.rokka.io/www_card_2/1dc4d3/csl-meetup-banner.jpg" length="885814" type="image/png" />
          </item>
        <item>
      <title>OctoberCMS&#8230; or why do we need yet another CMS?</title>
      <link>https://www.liip.ch/fr/blog/octobercms-or-why-do-we-need-yet-another-cms</link>
      <guid>https://www.liip.ch/fr/blog/octobercms-or-why-do-we-need-yet-another-cms</guid>
      <pubDate>Wed, 24 Jan 2018 00:00:00 +0100</pubDate>
      <description><![CDATA[<p>Over the last few years we created lots of projects with WordPress and it was - and still is - a pleasure to do so. But we had some requests where WordPress just didn't exactly fit. WordPress is great when it comes to basic websites. But as soon as you have requirements which are more complex or you even need to create a web application, WordPress isn't the right choice probably.</p>
<h2>What is OctoberCMS?</h2>
<p>WordPress is based on simplicity - everything is a post, which makes it easy to use for content authors and developers. Thanks to this concept, (nearly) all backend forms look consistent which helps content authors a lot. But this simplicity makes it harder for developers to create backends for more complex content.</p>
<p>This is where OctoberCMS jumps in. It is a great mix of a file based and database driven CMS. Everything which is more or less static (like pages, menus and templates) is saved as files. Like this the content can be served really fast. However you can of course edit these entities directly through the backend.</p>
<p>Everything which is more dynamic and more complex (like events, news or blogposts) is stored in custom tables in the database. Thanks to this you will have full freedom on how to create your own types.</p>
<h2>Complexity doesn't matter</h2>
<p>With this strategy OctoberCMS can be used for simple websites as well as for really complex ones. When using it for simple websites, the user experience of the backend can be compared to the one of WordPress. It is easy to use and looks consistent. On top of that it adds some useful features for power users, like editing multiple content elements in tabs or keyboard shortcut. The most useful one is saving data with <kbd>CMD+S</kbd> / <kbd>CTRL+S</kbd>. I'm already at a point where I find myself trying to save blogposts in WordPress with this key combination (which doesn't work sadly).</p>
<p>When using it for a more complex website you'll get full freedom on what to use OctoberCMS for. You can easily use it as a headless CMS for any sort of web application. To help you with this, the backend gives you a base structure for list views and form views for each model. If required you can modify these templates to fit your own needs. The provided form widgets helps creating consistent backend forms for almost every use case. If needed you can create your own form widgets without any hassle. This means the backend is highly customizable which improves the usability when editing complex content extremely.</p>
<h2>Still not convinced?</h2>
<p>Let's look at some more, great reasons why you should consider OctoberCMS for your next website:</p>
<ul>
<li><strong>Based on Laravel:</strong> OctoberCMS is based on the <a href="https://laravel.com/">Laravel framework</a> (which is based on Symfony. It builds a really solid foundation for the core, plugins and themes.</li>
<li><strong>Clean code:</strong> By using the Laravel framework there is clear <a href="https://laravel.com/docs/5.5/contributions#coding-style">coding style definition</a> which helps your code base to stay clean.</li>
<li><strong>Open Source:</strong> The whole OctoberCMS project is hosted as open source software on <a href="https://github.com/octobercms/october">GitHub</a> which is a really important thing to build a big user community around.</li>
<li><strong>Easy to extend:</strong> OctoberCMS is built for extensibility. The best example for that is that even the most basic features, like creating and editing pages, are provided via a <a href="https://github.com/rainlab/pages-plugin">plugin</a> and are not hardcoded in the core.</li>
<li><strong>Database query building with Eloquent:</strong> For database query building Laravel has <a href="https://laravel.com/docs/5.5/eloquent">Eloquent ORM</a> integrated. With this you can easily create database queries which fits your needs.</li>
<li><strong>Database migrations:</strong> The whole OctoberCMS setup (core and plugins) is based on <a href="https://octobercms.com/docs/database/structure#migration-structure">database migrations</a>. This helps keeping the database consistent when installing or updating plugins or the core. With this mechanism you can easily rollback to an older version if something doesn't work as expected.</li>
<li><strong>Event driven:</strong> The whole setup is <a href="https://octobercms.com/docs/services/events">event driven</a> which enables you hook into core or plugin processes and extend them easily.</li>
<li><strong>Twig templates:</strong> OctoberCMS uses <a href="https://octobercms.com/docs/markup/templating">twig as templating engine</a>. This makes it possible to completely separate your data from the templates.</li>
<li><strong>Integrated assets pipeline:</strong> OctoberCMS comes with a twig based <a href="https://octobercms.com/docs/markup/filter-theme">assets pipeline</a> to compile and minify your CSS (support for Sass &amp; Less) and JS files. All you need to do is including your source files directly in your twig templates and they get compiled, minified and cached automatically when calling the website the first time. If you have more complex requirements Laravel provides an abstraction layer above webpack called <a href="https://github.com/JeffreyWay/laravel-mix">Laravel Mix</a> which makes the creating of webpack based build tasks easy.</li>
</ul>
<h2>The bad parts</h2>
<p>Not everything can be nice and shiny. So here we go with the imperfect or missing parts of OctoberCMS:</p>
<h3>Core bugs</h3>
<p>First of all since this is a rather new CMS project (compared to other big players on the market) you might find some more or less &quot;simple&quot; core bugs while implementing a complex backend feature. This can be annoying, but since the community is very active (on <a href="https://octobercms.com/forum/post/octobercms-is-now-on-slack">Slack</a> or on <a href="https://github.com/octobercms/october">GitHub</a>) you will get help quickly.</p>
<h3>i18n</h3>
<p>Another important topic is <strong>i18n</strong>: OctoberCMS provides an implementation for translating content as a <a href="https://github.com/rainlab/translate-plugin">plugin</a>. With it you are able to translate most of your content from a base language to other languages which works fine.</p>
<p>But since you always need your content to exist in a base language you are limited to only translating your website and not doing real i18n stuff like different content in different languages. The good thing about this is that the folks behind this plugin are working on that feature right now and since the <a href="https://github.com/rainlab/translate-plugin">plugin is hosted on GitHub</a> you can help if you want.</p>
<h2>That's all folks</h2>
<p>We're really looking forward to build a lot more websites with OctoberCMS. And if you are a web developer you should really consider it when planning your next CMS project.</p>]]></description>
                  <enclosure url="http://liip.rokka.io/www_card_2/846eca/octobercms.jpg" length="52020" type="image/png" />
          </item>
        <item>
      <title>Swissquote: How to become a leader in banking in 26 years?</title>
      <link>https://www.liip.ch/fr/blog/smv-swissquote</link>
      <guid>https://www.liip.ch/fr/blog/smv-swissquote</guid>
      <pubDate>Wed, 23 Nov 2016 00:00:00 +0100</pubDate>
      <description><![CDATA[<p><em> <a href="https://www.swissmarketingvaud.ch/evenements/swissquote-en-26-ans-devenir-leader-par-linnovation-et-le-marketing-de-contenu/">Swissmarketing Vaud</a>invited Jan De Schepper, Head of Marketing at Swissquote. I expected a guide to be a leader in a few simple steps. Highly interesting, this conference actually felt like one of my masterclass.</em></p>
<p>Report of the conference</p>
<p>SWISSQUOTE, EN 26 ANS, DEVENIR LEADER PAR L'INNOVATION ET LE MARKETING DE CONTENU</p>
<p>Jan de Schepper</p>
<p>At this conference, what I wanted to know was how to become a leader. I expected De Schepper to hand me over the strategic marketing keys to success. The secret recipe for me to make Liip, my entreprise, an absolute leader in web development.</p>
<p>What kind of advice did I get?</p>
<h2>Swissquote, a content brand</h2>
<p>According to De Schepper, the foundation of a company leaves a significant mark. The founders, Marc Bürki et Paolo Buzzi owned Marvel Communication SA, a company specialized in financial information softwares. Once they figured out that they could provide the services they were talking about, Swissquote became a bank and IPO'd as such on the 29th of May 2000. The focus of Swissquote was on content creation right from the beginning.</p>
<h2>A basic brand structure</h2>
<p>At Swissquote, they believe that the brand defines who they are and how they act. Their brand structure is actually not original, as it involves a vision and six values.</p>
<p>In De Schepper's words, a vision is like an Evening Star (Etoile du Berger in French). It is what leads your way.</p>
<blockquote>
<p>To be the world's most pioneering and intuitive online bank.</p>
</blockquote>
<p>They are two essential words building this vision: pioneering and intuitive. “We are and want to stay pioneer, because our concurrence is international.” says De Schepper. Thus, innovation is fundamental. Secondly, UX is key, everything from the service to the platform has to be intuitive.</p>
<p>Swissquote has 6 fundamentals brand values</p>
<ul>
<li>Dare to be different</li>
<li>In pursuit of excellence</li>
<li>Unite as one</li>
<li>Always say it how it is</li>
<li>Champion the customer</li>
<li>Do the right thing</li>
</ul>
<h2>Tips and tricks to create content</h2>
<h3>Be customer-focused, not product-focused</h3>
<p>You should create and use personas. Personas must define who the users are with as much details as possible. It is easier to produce content when you have someone specific in mind. At Swissquote, they statistically analyzed data from their users to create their personas. Then they did some focus group to refine their analyses.</p>
<p>Secondly, they analyzed the Trader Journey to see what can be done in order to increase the conversion from one step to another. The content is then based on the needs and expectations of the users during their journey. In other words, they analyse the blockers in the Trader Journey. For example, does the type user X miss information at a certain point in his journey? Which info? How can it be provided?</p>
<h3>Think as a publisher</h3>
<p>When you create content, you should think as a publisher, not as an advertiser. You do not promote your product, you provide:</p>
<ul>
<li>Information</li>
<li>Inspiration</li>
<li>Utility</li>
<li>Entertainment</li>
</ul>
<h3>Create valuable content</h3>
<p>In order to be valuable, the content you create has to fulfill the following adjectives (see picture).</p>
<figure><img src="https://liip.rokka.io/www_inarticle/6c27b04f55deadb1e9e48ddb3c1c2e7c11c83e22/cotnent-1024x559.jpg" alt="Content"></figure>
<p>For example: Authentic: do not speak about something you have no idea about</p>
<p>Sharable: People share because they want transmit something about themselves, who they are, what they believe in. It's egoistic. Provide content according to who your users are.</p>
<p>Collaborative: Have partners that bring you visibility</p>
<h3>Plan the diffusion</h3>
<p>Think in terms of three categories:</p>
<ul>
<li>Paid media : the content you pay to be published (advertisement),</li>
<li>Owned media: the communication channel you own,</li>
<li>Earned media: the channel that publish your content (for example, you video on someone else's page).</li>
</ul>
<h2>De Schepper best advice</h2>
<p>…according to me, it is the best piece of advice: Iterate!</p>
<p>Try once, analyse, do it again with slight changes, analyse, try again and go on and on.</p>
<h2>Swissquote Magazine as a case study</h2>
<p>As an example, you can see the strategy of the publication in the pictures of the slides at the end of the article.</p>
<h2>To conclude: apply your theory and iterate</h2>
<p>De Schepper reminded me of my master class. I got out thinking that I should carefully stick to what I learnt. In the turmoil of daily business, I mostly feel that I should act and that standstill is the worst.</p>
<p>In fact, I know the theory to become a leader or make my entreprise a leader. However the team at Swissquote is a master in applying these theories. One of their most brilliant success, is the creation of a magazine, which is today an authority in their field of expertise.</p>
<p>The secret recipe is iteration. I should take the time to analyse. Each analysis is an opportunity to do better and increase the success of my next marketing action.</p>
<h2>Swissquote Magazine</h2>
<figure><img src="https://liip.rokka.io/www_inarticle/075090706395462aec36046c3fa51b8fed5c142e/case-study-2-1024x899.jpg" alt="Swissquote - objective"></figure>
<figure><img src="https://liip.rokka.io/www_inarticle/395588335842fce8bbef697f7795f5f6e73811f2/case-study1-1024x869.jpg" alt="Swissquote-distribution"></figure>
<figure><img src="https://liip.rokka.io/www_inarticle/e91b3cc622bec081afcb1ebe3c3e05380907ff69/case-study-3-1024x992.jpg" alt="Swissquote-Costs"></figure>]]></description>
                  <enclosure url="http://liip.rokka.io/www_card_2/107fcf06903d143c7087d059bc89873283952dd1/case-study-2.jpg" length="66247" type="image/jpeg" />
          </item>
    
  </channel>
</rss>
