Derek, Empirically by evidence of the lack of material on-line or obvious solutions, you may be right. But I respectfully disagree. Almost every website has an About Us page for example and a pile of other simple flat pages.
And Django supports flatpages natively, just not with a well documented easy way to edit them easily! Regards, Bernd. On Monday, 4 March 2019 17:40:35 UTC+11, Derek wrote: > > "Surely it's a ubiquitous need" > > No, I think not. In the dim and distant past I used to write copious help > files for various Windows apps ... but on the web? No one really reads > manuals or help files any more - your app needs to be simple and obvious to > use. > > If you are that noble as to still want to write a manual, I'd suggest > using any number of really good off-line tools and make the manual > downloadable as a PDF - most of those tools will also generate a series of > static webpages which you can host quite easily. Suggestion: ReadTheDocs > uses Sphinx to generate docs for Python libraries; but there is no reason > you could not also use that to write end-user documentation. > > HTH. > > On Friday, 22 February 2019 12:02:27 UTC+2, ukeplayer01 wrote: >> >> Sorry to go off topic but I can recommend HuGo for simple markdown web >> pages. >> Cheers >> Roger >> On 22/2/19 5:24 pm, Bernd Wechner wrote: >> >> Hmmm, no-one has any thoughts here ... and I'm on ma' own reinventing the >> wheel? Surely tehre's a canonical way to provide help on Django website . >> I'm leaning toward simple flatpages app with a tinymce editor for them for >> the admin. >> >> On Tuesday, 19 February 2019 16:26:57 UTC+11, Bernd Wechner wrote: >>> >>> I'm at the point of wanting to write some help for a website, the >>> standard helpfile sort of scenario ;-). If that means little to you, just a >>> hierarchy of pages that document things and can be linked. >>> >>> I wrote page one with the Django flatpages app: >>> >>> https://docs.djangoproject.com/en/2.1/ref/contrib/flatpages/ >>> >>> But it's not real comfy in terms of editing and maintaining. So I looked >>> on-line for solutions and of course nothing with "help" in the search terms >>> is going anywhere fast (finds me a lot of help about Django ;-). so better >>> keywordss needed but I have found a pile of maybe options and am suddenly >>> bamboozled by what is vogue, current, maintained, has a lasting future etc. >>> >>> https://github.com/klen/django_markdown >>> >>> Untouched in 4 years with 22 open issues Hmm. >>> >>> And this looks nice: >>> >>> https://github.com/mjr27/django-flatpages-tinymce >>> >>> but untouched in 7 years and 4 open issues. >>> >>> Now untouched doesn't mean bad, could just be mature, stable and works >>> perfectly, already fro 7 years. These are the things it's hard to gauge. >>> But if I'm looking at TinyMCE how about: >>> >>> https://github.com/aljosa/django-tinymce >>> >>> on which it depends. NO bad, updated a month ago to make it work with >>> Django 2.1 so seems alive! But my site is math heavy so I want equation >>> ease so how about: >>> >>> And this looks good: >>> >>> https://www.codecogs.com/latex/integration/tinymce_v3/install.php >>> >>> This looks maybe: >>> >>> https://github.com/iCAPLyon1/tinymce-formula >>> >>> This looks unconvincing: >>> >>> https://github.com/foraker/tinymce_equation_editor >>> >>> and do we want this: >>> >>> https://github.com/Tivix/django-flatpages-nav >>> >>> or this as well: >>> >>> Or hang on why do this piecemeal why not use Wagtail from the word go: >>> >>> http://docs.wagtail.io/en/v2.4/index.html >>> >>> Or would wagtail introduce too much coordination trouble between its >>> templates and my sites ... etc. etc. I'm full of questions and really just >>> wondering, is there a canonical solution to a site documentation page >>> hierarchy and managing it nicely? >>> >>> Regards, >>> >>> Bernd. >>> >>> >>> -- >> 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 post to this group, send email to django...@googlegroups.com. >> Visit this group at https://groups.google.com/group/django-users. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/django-users/750a97d8-87f9-42f4-997e-5810e1a5c48a%40googlegroups.com >> >> <https://groups.google.com/d/msgid/django-users/750a97d8-87f9-42f4-997e-5810e1a5c48a%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> >> -- 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+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/03256e04-f43d-415e-8ad4-030157802c36%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
