Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 years ago.
Improve this question
After creating reusable Django apps do one make an app that glue them together to create a website? Also is it correct to make each menu item and section an app itself in Django? The source code of https://www.djangoproject.com/ is probably the best example of how to correctly structure Django websites if it is available.
How you organise your project is up to you and mostly depends on the project's specific needs, but yes using a "main" app to glue the pieces together is a common and working pattern. Also you don't have to try and make your project's apps reusable - start with just what your project requires and if you find out some parts solve recurring problems it will be time to factor them out as more generic apps.
Wrt/ your menus they have to match the site features not it's implementation so the "one app one menu" thing very seldom makes sense. And since it's a "glue" part it really belongs to the project's main app (even if it usually delegates parts of the job to other apps).
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 3 years ago.
Improve this question
I'm working on a development road map for a django project. My choosen IDE is pycharm pro and mock up tool is bootstrap studio. One of my criteria is a calendar and I have discovered that none of the existing public projects will meet my needs so I will have to create one from scratch (no problem). My typical approach would have been that the UI and the django project would be done in near parallel periodically merging and diverging the two. However, given the ability of the two software tools, I'm starting to think that that a better approach may be to do the UI first in BSS, next import the templates into the django project and finally perform the django dev to meet the needs of the UI.
The specific calendar functionality is not the issue here, this is a methodology question. While I know that there is a subjective answer to this question (which is not the "answer" I'm looking for here), there also has to be an objective answer as to why this would not work, or be the incorrect approach.
Doing the UI first is fine if you already know exactly what you want it to do and can specify that. Doing the Django first lets you play around with a working rough version and get a better feel for what works best before fine tuning the look and feel. Like you suggest, working on them both together will let each inform the other.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
I have been learning the Django framework for the last few weeks and I need to create a simple website for a dentist. The site just needs to have a few pages with flat data.
I was wondering whether using Django for this sort of project is good?
I am also not sure whether I need any applications for this except a contact form, the site will mostly contain only views and templates.
I would strongly recommend to use frameworks like Django (RoR, Flask, Express), because it helps to make a web application easily (scaffolding).
You don't need to reinvent the wheel to make something simple.
By the way, for only-static content 2-3 pages I would recommend do not use programming tools. Use generators like Tilda / Wix or something similar to it.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 years ago.
Improve this question
OVERVIEW
I'd like to test some Django websites using random data on a production server using real domain names, but these websites will be simple tests with possible duplicated data (quite probable not following Google rules). I know usually for this you use a development/staging/virtual box for such a task, but I do want to use directly the production box with the real DNS.
Now, I'm kind of new on website development and SEO, and I wouldn't like to mess with SEO and Google.
What'd be the right way to proceed here? Should I try to avoid being indexed/crawled by Google somehow? Any other advices?
You can disallow the complete indexing of your page and then later (when you're done with coding) activate it again.
Thats probably the best way because google is not going to crawl "bad pages" (for example when your website still is in development) and thus you will not get a Ranking so far (called Page Ranking if you want to look it up).
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 9 years ago.
Improve this question
I'm currently developing a game with friends. We are searching for informations about design patterns for User Interface in order to implement a simple UI including: buttons, progress bar (for health, exp, mana, ...), text, views/subviews, and scroll views.
The first goal is to have something simple but working. We are not looking for patterns about making an UI loading from XML/JSON files, we just need information about the inheritance of our classes and their relationship.
While it doesn't matter while we talk about design patterns and algorithms, we develop in C++, using SFML/OpenGL 2.x for rendering.
Any additional information about implementation in C++/OpenGL are welcome :)
EDIT: I already know about the common design patterns and the MVC architecture, but I look for a far more simple alternative since our goal is not to recreate Qt or Cocoa.
My question is more about an alternative and how to organize these patterns.
I suggest you go over this site, it has a great example from "Gang of 4" (look it up)
great web for design patterns
and there is also a great tutorial in youtube
http://www.youtube.com/user/derekbanas
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
Is it possible to built my "Learning Management System (LMS)", on TOP of Content Management Systems like Mezzanine or Django-CMS ?
I'm building a product for a private school, and I found that the patterns are so close to a CMS, except for having my own models (Course, Subjects, etc.)...
There should be some learning curve to get the best result of a CMS, of course.
what do you recommend ??
Mezzanine has its own implementation of a page tree rather than using mptt, and it's quite solid. It's also designed for you to add your own Django models to the tree. From what you've said (which granted isn't much) it sounds quite suitable. Have a read over the relevant docs section here: http://mezzanine.jupo.org/docs/
I've not used mezzanine, but doing something like this would certainly be possible on top of django_cms.
It's quite straightforward to write custom plugins for a CMS, so you could build new widgets (assessments, polls etc) which can be dropped into cms-based pages. The menu's can also be extended , with new menus build based on objects in your models (e.g. courses, modules)... one gotcha with this is that the menus get cached, so the app either needs to be restarted to rebuild menus or you would have to add a hook to rebuild them manually. There are pretty good docs on this here:
http://docs.django-cms.org/en/2.1.3/extending_cms/custom_plugins.html
and on building custom apps, which can be hooked up to CMS urls:
http://docs.django-cms.org/en/2.1.3/extending_cms/app_integration.html
Overall, I quite like django_cms, although the breakage with successive versions (and also versions of MPTT on which it depends) has been quite a pain. It looks like they are trying to clean up this sort of thing in forthcoming releases though, and contrib.staticfiles is now supported which is nice.