<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Cécile Fécherolle</title>
    <description>The latest articles on DEV Community by Cécile Fécherolle (@cfecherolle).</description>
    <link>https://dev.to/cfecherolle</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F111418%2F4882074b-7c7f-4de7-a98f-2547d0f0c242.png</url>
      <title>DEV Community: Cécile Fécherolle</title>
      <link>https://dev.to/cfecherolle</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/cfecherolle"/>
    <language>en</language>
    <item>
      <title>What are your tools for keeping dependencies and plugins versions up-to-date?</title>
      <dc:creator>Cécile Fécherolle</dc:creator>
      <pubDate>Fri, 14 May 2021 12:37:44 +0000</pubDate>
      <link>https://dev.to/cfecherolle/what-are-your-tools-for-keeping-dependencies-and-plugins-versions-up-to-date-126g</link>
      <guid>https://dev.to/cfecherolle/what-are-your-tools-for-keeping-dependencies-and-plugins-versions-up-to-date-126g</guid>
      <description>&lt;p&gt;Hi everyone!&lt;/p&gt;

&lt;p&gt;I rarely post here but today I decided to ask the community about some tooling.&lt;/p&gt;

&lt;p&gt;One thing that I find daunting in today's web dev ecosystem is how to keep track of dependencies and plugin versions in all layers of our apps and, say, not miss a lot of versions for one tool or the other.&lt;/p&gt;

&lt;p&gt;For example, in the project I'm working on, we have a front-end app made with React, a Java/Spring Boot back-end, a Keycloak authentication system, and so on.&lt;/p&gt;

&lt;p&gt;So I was asking myself: is there some kind of tool to subscribe to new versions of packages/libs, get warnings about end of life, and such? &lt;/p&gt;

&lt;p&gt;I do know there are tools like Maven versions plugin for Java or npm packages to be run manually to get info on possible updates.&lt;/p&gt;

&lt;p&gt;My actual question is: how do you guys regularly check for those? Do you have like a calendar reminder to launch a bunch of tools manually (my current "solution" as of today), or something else that I don't know about?&lt;/p&gt;

&lt;p&gt;Waiting for your feedback 😊&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>tooling</category>
      <category>security</category>
      <category>help</category>
    </item>
    <item>
      <title>Netlify CMS or Forestry.io?</title>
      <dc:creator>Cécile Fécherolle</dc:creator>
      <pubDate>Tue, 24 Mar 2020 21:27:11 +0000</pubDate>
      <link>https://dev.to/cfecherolle/netlify-cms-or-forestry-io-3i8g</link>
      <guid>https://dev.to/cfecherolle/netlify-cms-or-forestry-io-3i8g</guid>
      <description>&lt;p&gt;Hey guys!&lt;/p&gt;

&lt;p&gt;First post here. I'm a little bit unsure of what comes next but thought asking for advice here would do me good!&lt;/p&gt;

&lt;p&gt;I'm doing some ground-laying research for an upcoming personal project (a portfolio + tech blog combination for personal branding and online presence). My "plan" is to create a simple design myself and generate a static website around it, and handle a small blogging environment without too much hassle.&lt;/p&gt;

&lt;p&gt;So far I've read a lot about SSG and what revolves around it, and I'd like to go with:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;VueJS&lt;/li&gt;
&lt;li&gt;Gridsome as SSG tool&lt;/li&gt;
&lt;li&gt;Git (of course)&lt;/li&gt;
&lt;li&gt;Netlify for deployment, hosting and such, because it honestly looks like a game-changer from what I've read. (also: free plan, yay!)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Knowing all this, I'm trying to figure which Git-based CMS to use for the blogging part (plus portfolio sections content, for easier updates, versionning, and such).&lt;/p&gt;

&lt;p&gt;I'm hesitating between Forestry (&lt;a href="https://forestry.io/"&gt;https://forestry.io/&lt;/a&gt;) and Netlify CMS (&lt;a href="https://www.netlifycms.org/"&gt;https://www.netlifycms.org/&lt;/a&gt;).&lt;/p&gt;

&lt;p&gt;I've read lots of good stuff about both of them, and Netlify CMS seems loosely coupled (if coupled at all) with Netlify, so both options seem reasonable.&lt;/p&gt;

&lt;p&gt;I would really appreciate some dev feedbacks on any of these two CMS solutions (pros, cons...) to help me choose!&lt;/p&gt;

&lt;p&gt;Apart from that, remarks about the project stack I'm envisioning will be gladly heard, as long as they're polite and constructive!&lt;/p&gt;

&lt;p&gt;Thanks in advance, I'm really looking forward to reading from you :)&lt;/p&gt;

</description>
      <category>discuss</category>
      <category>javascript</category>
      <category>webdev</category>
      <category>cms</category>
    </item>
  </channel>
</rss>
