Wednesday, 15 February 2012

python - Django project structure -


I have been playing with Django for a couple of weeks and I decided to try to make it my personal website.

There is only one thing that I have not been able to wrap my head so far, how should I structured this project? The site's required blog will be a one-off portfolio which will show posts about those projects (compared to categories on normal blogs) about those projects .

Now I have a question, should it be a big app or should I split it into many smaller apps and how will it be in that situation? you do this?

For now, it seems acceptable to do everything in an app, but my plan is to add facilities in that way and increase the site continuously. After some time I do not take out the possibility That it can be very complicated :)


This question has been closed because it is "mostly opinion based" ..

I'm asking for experience (which I do not have yet), able to make better choices To avoid this I should build my own project, it will have to be reconstituted later because I have done poorly due to the lack of experience. Of course, this requires some opinion-based answer.

As you only have a category of article , I recommend you start with an application Give it

Therefore, you can start with an application called projects . After this, if you want to write about your experiences, then create a new app by the name experiences , and so on.

Personally, my portfolio is built around three categories / applications:

  1. Skill,
  2. Projects,
  3. Experience.

The applications are ideal for large Django websites. I advise you to add an application to your project when it becomes bigger and more complex right now, making your life easier using only one application;)


No comments:

Post a Comment