Deciding on Database

[Rushikesh Patil]

Hello everyone, Hope you are doing well. 

I am building a website with django which will be used to view different documentation related to the construction industry, in an easy to use and share format. 

The main viewer page will have a vertical nav bar with different chapters and sections. And the right side will be the content. 

What I am trying to figure out is instead of doing a hardcoded HTML css static file, use the database to create a html file . What do you think is the best way to go about ir. I thought about it a lot and the problems I see is where there are lists/tables/images in content. I am having a hard time deciding what models should I create.

Please see attached for what I am trying to build. 

[RLM]

Hello

I am a 25 year python dev working with Flask and Django experience and this is totally off topic but may I suggest you look at Hugo the static web site generator in the Go language.
It is easy to use, easier than some pythonic web site generators.

Easy to modify and update and is essentially ready to use and can be fully manipulated to do what you want. I used this system on AWS for a Australian national web site and find updating documents and comments is very simple, plus no one  can modify anything unless you grant express permissions. Plus you can decide whether it becomes public or private with the click of a checkbox.

Used in conjunction with AWS S3 buckets  it provides, for us, a very workable system. With AWS security the site is entirely safe.

My utmost apologies to the Python, Django community but sometimes other tools are worth looking at.

Roger

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/eca1e72f-7b8f-4d14-884f-d7a3b2d67491%40googlegroups.com.

[Alexander Alemayhu]

I also think a static site generator might make more sense especially if the content is only really being read and edited. i.e. no dynamic parts (not including client side stuff like search). It’s also much easier to maintain and deploy IMHO. 

Don’t know all your requirements but it also sounds like you don’t really need a database but rather a content management system for easily writing / editing the documentation.

Useful links

https://www.staticgen.com

https://headlesscms.org

To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/f8609fd2-849a-7d5c-5f65-4d7a0046f71f%40gmail.com.

--

Mit freundlichen Grüßen

Alexander Alemayhu