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.
Related
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 2 years ago.
Improve this question
I'm still a beginner, and for some reason using a built in model such as User seems bugs me a bit. Should I create my own User model to become a more independent programmer, or will the User model do just as fine if not better for my project? Please tell me about the pros and cons about the User model. Any help is much appreciated.
it bugged me a bit too and now I use node, though Django is great for getting started with conventional concepts you'll keep running into over and over. For example, If you use the User module, you get authentication and admin panel with not too much more work. The downside is you'll feel a bit like an outsider in your own code. Modifying a built in model is weird, especially when so many other Django components depend on so many attributes.
If you're weighing your options, consider how much you need the free admin and auth. My personal recommendation is to build your own User model and implement the Django-specific attributes yourself.
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 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 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).
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 8 years ago.
Improve this question
I would like to be able to create a pretty dead simple Ember.js application and have it populate a Google Spreadsheet, and also have the capability to go back and edit records. Is this even feasible? Does anybody know of a good tutorial, github repo or gist demonstrating this?
Right now it is just an idea, and searching the web did not yield much. Is this because it is a foolish idea, or just because nobody has done it yet?
Yes there is: ember-gdrive
provides ember data bindings for google drive.