<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Clement “Snowji” D on Medium]]></title>
        <description><![CDATA[Stories by Clement “Snowji” D on Medium]]></description>
        <link>https://medium.com/@clement.darrouzes?source=rss-8ce28357b3af------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*kvWWHloAoc8k3Toa</url>
            <title>Stories by Clement “Snowji” D on Medium</title>
            <link>https://medium.com/@clement.darrouzes?source=rss-8ce28357b3af------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 12:15:46 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@clement.darrouzes/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[XP Feedback — File architecture for our projects]]></title>
            <link>https://medium.com/kaliop/xp-feedback-file-architecture-for-our-projects-6e743a8158e1?source=rss-8ce28357b3af------2</link>
            <guid isPermaLink="false">https://medium.com/p/6e743a8158e1</guid>
            <category><![CDATA[architecture-components]]></category>
            <category><![CDATA[react-native]]></category>
            <category><![CDATA[vuejs]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[symfony]]></category>
            <dc:creator><![CDATA[Clement “Snowji” D]]></dc:creator>
            <pubDate>Thu, 09 Jan 2020 09:22:17 GMT</pubDate>
            <atom:updated>2020-01-09T09:22:17.479Z</atom:updated>
            <content:encoded><![CDATA[<h3>XP Feedback — File architecture for our projects</h3><p>Firstly, if you prefer to read french version, find it here : “coming soon”</p><p>I was able twice to experience a heavy refactor, the one of the architecture of projects files.<br>The first one, thus the oldest (2016), was on a <strong>Symphony (PHP)</strong> project. The second one was some time ago (late 2018) on a <strong>React Native (Javascript)</strong>.</p><p>You might tell me : “but what is the link between these two technologies and their files architecture ?” Precisely ! Their documentation, most of tutorials and more lead us on the same way in terms of files organisation.</p><p>The objective here is to give you a feedback, what I learned of my experience, not to feed a never-ending debate to find which is best. You are free to choose what suits you best. I still wish to raise the fact that even if this part doesn’t seem very important, it is nevertheless structuring and it has an impact to the development of a project.</p><h3><strong>State of play :</strong></h3><p><em>Nb : Do not consider my project trees as fully realistic, these are examples created only for the sake of writing this article.</em></p><p>In both cases, whether for React Native or Symfony, the potential problem is the same for both, and the same goes for the solution. Let’s take a look for now at the architectures offered by these frameworks.</p><p>Symfony : the official documentation and the standard source code suggest that we arrange the files by type. For example, controllers will be in a Controller folder, forms in a Form folder, etc.<br>React Native : just like Symfony, if you start a React Native project, the basic architecture will propose you to organize your code by type as well. Put all components together in a Components folder, the same goes for others such as selectors, reducers, etc.<br>These architecture proposals also apply to <strong>VueJS</strong>, a framework frontend that I particularly like.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/659/1*ISbG50BsTS1LUAgRhPLxng.jpeg" /><figcaption>files organization by type</figcaption></figure><p>We will agree that this architecture provides a good readability of the file structure because the grouping is quite logical. However, we don’t encounter it often because it lacks organization and it looks quite basic. Yet, this architecture becomes even more convenient if you add sub-folders for each type in order to provide some value and business logic. Below, you can find a standard organization that is found in most projects.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/659/1*mPorSABs42BS_y83qArXVQ.jpeg" /><figcaption>files organization by type and sub folders</figcaption></figure><p>Now, let’s push this logic further, or rather the other way around : put the profession on the first level and the types on the second.</p><h3><strong>Moving forward to improve productivity and readability</strong></h3><p>Rather than organizing files by type, try to highlight the profession of your project. It is this business aspect that represents a project, which structures it.</p><p>The discourse of this architecture can be found in some documentation or articles, but is rarely highlighted. Example on the documentation of Symfony, which advises to create only one Bundle and which finally suggests to highlight the profession in its “best practices” :</p><p><a href="https://symfony.com/doc/current/best_practices.html#don-t-create-any-bundle-to-organize-your-application-logic">https://symfony.com/doc/current/best_practices.html#don-t-create-any-bundle-to-organize-your-application-logic</a></p><p>The goal is therefore to gather all the files related to the “articles” of your project, or everything related to the “user”, or to the “products”, for example.</p><p>Through my experience so far and after testing both architectures, the latter (and I will illustrate it to you) is much easier to use, facilitates the readability and logic of your code, and therefore the understanding and productivity in your project.</p><p>Here is what it can give for the frameworks mentioned today.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/659/1*tVQyouYSEsJQSNBqYrGDfw.jpeg" /><figcaption>files organization by profession</figcaption></figure><p>As you can see, it is still quite trivial and can be applied to a wide range of frameworks.<br>However, you have to remain pragmatic. This is why in my previous example, there are times when some files remain at the root of a folder and have no parent “type” folder. That is because if they are alone, it is useless to create a folder for a single file. This architecture is very well suited for large projects. It will provide less readability for a micro project with a relatively low business value.</p><p>Finally, I will have no more arguments than this illustration above showing you the final result of this type of architecture, inviting you to try it out in order to build your own opinion.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6e743a8158e1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/kaliop/xp-feedback-file-architecture-for-our-projects-6e743a8158e1">XP Feedback — File architecture for our projects</a> was originally published in <a href="https://medium.com/kaliop">Kaliop</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>