<?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>Forem: Jonathan</title>
    <description>The latest articles on Forem by Jonathan (@jonathanazerty).</description>
    <link>https://forem.com/jonathanazerty</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%2F748879%2F717290ed-b269-430d-af67-3d675bfd4f47.jpeg</url>
      <title>Forem: Jonathan</title>
      <link>https://forem.com/jonathanazerty</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://forem.com/feed/jonathanazerty"/>
    <language>en</language>
    <item>
      <title>How to plan a React project? For beginners</title>
      <dc:creator>Jonathan</dc:creator>
      <pubDate>Sun, 14 Nov 2021 20:35:25 +0000</pubDate>
      <link>https://forem.com/jonathanazerty/how-to-plan-a-react-project-for-beginners-16pg</link>
      <guid>https://forem.com/jonathanazerty/how-to-plan-a-react-project-for-beginners-16pg</guid>
      <description>&lt;p&gt;&lt;strong&gt;STEP 1: CONCEPT&lt;/strong&gt;&lt;br&gt;
&lt;strong&gt;STEP 2: APPROACH&lt;/strong&gt;&lt;br&gt;
&lt;strong&gt;STEP 3: ORGANIZE&lt;/strong&gt;&lt;br&gt;
&lt;strong&gt;STEP 4: BUILD&lt;/strong&gt;&lt;br&gt;
&lt;strong&gt;STEP 5: INSPECT&lt;/strong&gt;&lt;br&gt;
&lt;strong&gt;STEP 6: REFLECT&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;...&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;WHY DO YOU NEED A PLAN?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;First and foremost, you need a strategy to begin with a project to &lt;strong&gt;&lt;em&gt;set the direction&lt;/em&gt;&lt;/strong&gt; and &lt;strong&gt;&lt;em&gt;establish the priorities&lt;/em&gt;&lt;/strong&gt; for the project.&lt;br&gt;
It will &lt;strong&gt;&lt;em&gt;help&lt;/em&gt;&lt;/strong&gt; you (and others if you work on a group project) to make it &lt;strong&gt;&lt;em&gt;clear what to work on&lt;/em&gt;&lt;/strong&gt; and &lt;strong&gt;&lt;em&gt;easy to communicate&lt;/em&gt;&lt;/strong&gt; with clients (and colleagues/boss).&lt;/p&gt;

&lt;p&gt;Planning will give you &lt;strong&gt;&lt;em&gt;control&lt;/em&gt;&lt;/strong&gt;, a &lt;strong&gt;&lt;em&gt;timeline&lt;/em&gt;&lt;/strong&gt;, &lt;strong&gt;&lt;em&gt;reassurance&lt;/em&gt;&lt;/strong&gt;, &lt;strong&gt;&lt;em&gt;efficiency&lt;/em&gt;&lt;/strong&gt;, &lt;strong&gt;&lt;em&gt;productivity&lt;/em&gt;&lt;/strong&gt;, &lt;strong&gt;&lt;em&gt;progress&lt;/em&gt;&lt;/strong&gt;, &lt;strong&gt;&lt;em&gt;flexibility&lt;/em&gt;&lt;/strong&gt; and of course the &lt;strong&gt;&lt;em&gt;desired results&lt;/em&gt;&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;The fact remains that a lot of things are beyond human control, but for those things that &lt;strong&gt;&lt;em&gt;are controllable&lt;/em&gt;&lt;/strong&gt;, planning &lt;strong&gt;&lt;em&gt;ensures you more control&lt;/em&gt;&lt;/strong&gt; over the project, which leads to a better result !&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Don't underestimate planning!&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;so START PLANNING !&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;STEP 1: CONCEPT&lt;/strong&gt; (&lt;em&gt;You can skip this part if you already got a concept&lt;/em&gt;)&lt;br&gt;
So before you actually start building, you should to think about what exactly should be built. &lt;br&gt;
Start brainstorming about some ideas &lt;/p&gt;

&lt;p&gt;&lt;strong&gt;STEP 2: APPROACH&lt;/strong&gt;&lt;br&gt;
&lt;strong&gt;&lt;em&gt;Write down how you will be working&lt;/em&gt;&lt;/strong&gt; and if you will &lt;strong&gt;&lt;em&gt;use certain tools to help&lt;/em&gt;&lt;/strong&gt; with that. &lt;br&gt;
Like Todoist for example. See image.&lt;br&gt;
&lt;strong&gt;TODOIST&lt;/strong&gt; &lt;a href="https://todoist.com/" rel="noopener noreferrer"&gt;https://todoist.com/&lt;/a&gt;&lt;br&gt;
&lt;a href="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fp3lyqixsz7004nyeh9iv.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fp3lyqixsz7004nyeh9iv.jpg" alt="Image description"&gt;&lt;/a&gt;&lt;br&gt;
In the Todoist you can for example start with the following structure.&lt;br&gt;
&lt;strong&gt;Backlog, in progress, weekly planning and documents&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Backlog &amp;amp; in progress&lt;/strong&gt;&lt;br&gt;
&lt;a href="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fumy7vcj1jqegjmgux1xe.JPG" class="article-body-image-wrapper"&gt;&lt;img src="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fumy7vcj1jqegjmgux1xe.JPG" alt="Image description"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Weekly planning&lt;/strong&gt;&lt;br&gt;
Add the documents as a comment to keep track.&lt;br&gt;
&lt;a href="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F36siowwwldb80na2n01k.JPG" class="article-body-image-wrapper"&gt;&lt;img src="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F36siowwwldb80na2n01k.JPG" alt="Image description"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Documents&lt;/strong&gt;&lt;br&gt;
&lt;a href="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fivlrvclfibn57yo3qwvb.JPG" class="article-body-image-wrapper"&gt;&lt;img src="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fivlrvclfibn57yo3qwvb.JPG" alt="Image description"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Once you've done that, you can continue with the components.&lt;br&gt;
The most important thing in React are the components to start building the structure.&lt;br&gt;
Therefore, it is very important to &lt;strong&gt;sketch the structure of the components&lt;/strong&gt;. &lt;br&gt;
As you can see on the following image.&lt;br&gt;
&lt;a href="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F9lg4xjnets67j166m1gx.JPG" class="article-body-image-wrapper"&gt;&lt;img src="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F9lg4xjnets67j166m1gx.JPG" alt="Image description"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;After creating a clear structure on the Todoist and the components, you start with making it &lt;strong&gt;visual on for example FIGMA&lt;/strong&gt;(wireframe).&lt;br&gt;
Here you can start creating with the components you just thought of.&lt;br&gt;
As you can see on the following image for example.&lt;br&gt;
&lt;strong&gt;FIGMA&lt;/strong&gt; &lt;a href="https://www.figma.com/" rel="noopener noreferrer"&gt;https://www.figma.com/&lt;/a&gt;&lt;br&gt;
&lt;a href="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fqqibg5drofpdy9p04e2d.JPG" class="article-body-image-wrapper"&gt;&lt;img src="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fqqibg5drofpdy9p04e2d.JPG" alt="Image description"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;After figuring that out, it would also help to think about what techniques you would like to use and therefore which packages to use and write them down as well on the Todoist.&lt;br&gt;
&lt;a href="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fcrcdzr6qnqiwrnnvbjqr.JPG" class="article-body-image-wrapper"&gt;&lt;img src="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fcrcdzr6qnqiwrnnvbjqr.JPG" alt="Image description"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;And of course what's going to be your Git strategy.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;STEP 3: ORGANIZE&lt;/strong&gt;&lt;br&gt;
Once you got the approach figured out, it's time to start organizing what has been thought of for the project.&lt;br&gt;
If it's a group project, you can make it clear on who does what and when.&lt;br&gt;
Even when you are alone, you can &lt;strong&gt;write down when and what you will do&lt;/strong&gt;.&lt;br&gt;
Here you can find an example of a weekly planning.&lt;br&gt;
&lt;strong&gt;WEEK1&lt;/strong&gt;&lt;br&gt;
&lt;a href="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F46xqrew8xgoznzauq29a.JPG" class="article-body-image-wrapper"&gt;&lt;img src="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F46xqrew8xgoznzauq29a.JPG" alt="Image description"&gt;&lt;/a&gt;&lt;br&gt;
Which you can add as a comment in the Todoist.&lt;br&gt;
Also plan for time to work on unforseen issues&lt;br&gt;
Besides this weekly planning it's very important to &lt;strong&gt;start the day with a short 5min meeting on what you will do that day&lt;/strong&gt; and if there are problems, try to fix them if you don't manage to then try to fix it together or ask help!&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Communication is key !&lt;/strong&gt; &lt;/p&gt;

&lt;p&gt;Focus should also be on building itself, therefore, think about the &lt;strong&gt;&lt;em&gt;folder structure&lt;/em&gt;&lt;/strong&gt; as well. (this will depend on what kind of project you have).&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;STEP 4: BUILD&lt;/strong&gt;&lt;br&gt;
After preparing so well in advance, you will be so eager to start coding on your project !&lt;br&gt;
Start with everything that was talked about.&lt;br&gt;
&lt;strong&gt;Enjoy the journey and have fun!&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;STEP 5: INSPECT&lt;/strong&gt;&lt;br&gt;
After building the whole project, it's always important to &lt;strong&gt;&lt;em&gt;take some time to inspect&lt;/em&gt;&lt;/strong&gt; the whole project. Adjust where needed.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;STEP 6: REFLECT&lt;/strong&gt;&lt;br&gt;
Once you're done inspecting the pages, it's also important to take time to reflect on the project.&lt;br&gt;
To &lt;em&gt;**reflect on what went well and what went wrong&lt;/em&gt;&lt;em&gt;, *&lt;/em&gt;&lt;em&gt;to avoid making those mistakes on the next project&lt;/em&gt;** and &lt;strong&gt;&lt;em&gt;using what went well on the new project&lt;/em&gt;&lt;/strong&gt; so you keep growing and improving.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Hopefully this will help you out when planning your next or current project !&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;em&gt;Don't every forget to have fun, be curious and be eager to learn !&lt;/em&gt;&lt;/strong&gt;&lt;/p&gt;

</description>
      <category>react</category>
      <category>beginners</category>
      <category>webdev</category>
      <category>productivity</category>
    </item>
  </channel>
</rss>
