The latest articles on DEV Community by Soroosh (@sorooshdev). https://dev.to/sorooshdev 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%2F1070996%2F8601913c-5686-40db-b54a-90ea755e1282.png https://dev.to/sorooshdev en Soroosh Mon, 24 Apr 2023 21:09:22 +0000 https://dev.to/sorooshdev/first-post-on-dev-lets-build-a-django-powered-cms-4ip8 https://dev.to/sorooshdev/first-post-on-dev-lets-build-a-django-powered-cms-4ip8 <p>Hey there, This is my first post on dev and No I am not the crazy guy who wants to reinvent the wheel!<br> Yes, I am trying to build a new CMS using Django and yes, of course, there already is a great Django CMS. <a href="https://wagtail.org/">Hats off to Wagtail</a>.<br> I am going to develop BiliCMS anyway. I just can't resist naming products, now I have a name and an idea all that is left to do is to design, implement, test, and maintain my product.</p> <h2> Why build a new CMS? </h2> <p>Actually, I have to build websites for my clients on a daily basis. Sometimes I use an existing CMS like Wagtail or WordPress and sometimes I start developing a product suitable for a specific client from the scratch. Now I am thinking maybe if I start to generalize the needs of most of my clients they can have their websites ready faster and I need to do less work in order to deliver. That's the problem almost all content management systems are trying to solve.<br> A large portion of the clients that I am talking about require some sort of e-commerce website. I need e-commerce support and I need my code to be easily customizable. More importantly, I feel more confident when I understand all of my code base. So that's why I decided to build a new CMS.</p> <h2> Why the blog post? </h2> <p>Maybe I share a common problem with a fellow developer or two.<br> Usually, I am very private about my work, but this time I decided to mix some kind of social interaction with the project I am devoting my time to it. So, I decided to make myself write a little bit of a report about what's going on with the project now and then. I am not sure about it but it might help me stay excited and focused down the road.<br> I am also excited to know what other people think about it. Any kind of comment and opinions are encouraged.</p> <h2> Care to contribute? Let's do it together! </h2> <p>The result of this experience (that's what it is to me) whatever it will be is to be published on a public repository on GitHub. And as I mentioned before I am going to blog my way through it. I hope down the road I could benefit from the ideas and opinions of other developers. If you want to join the journey and contribute to the project, Great! Let's do it together then.</p> <h2> What's up with the project today? </h2> <p>I mentioned earlier about writing little bits of reports about the work I am doing. Here is that report. All I have done until now is I managed to specify the potential user's needs and write down some value propositions and then based on that I wrote a Product specifications document that loosely describes what the end result should be. In the following days, I hope to be done with the initial design phases.<br> In my next post, I plan to publish the Product specification document.</p> <p>What do you think? any suggestions or opinions? Should I not do it? What would you do or think about if you were to develop your own CMS? Let me know.</p> django opensource webdev community