On Mon, 25 Sept 2023, 00:57 Waldek Hebisch, <[email protected]> wrote:
> On Sat, Sep 23, 2023 at 02:23:04PM +0200, Ralf Hemmecke wrote: > > Since I currently put up the stuff at fricas.github.io, it actually > needn't > > be me. > > > > On 23.09.23 09:47, Qian Yun wrote: > > > Most importantly, documentation should be put there. > > > > Definitely, my suggestion would be that we simply serve the pages from > > > > https://fricas.github.io > > > > from https://fricas.org. And that would be completely easy to do. > > That would be easy, but I am affraid rather unsatisfactory. I mean, > API pages and PDF of FriCAS book are good things. But there are > only handful of other pages at fricas.github.io, I hope that we can > create more. Part of my question is to find out what is desirable > and possibly if there are persons willing to add something > > > The pages at fricas.github.io are generated from our official fricas git > > repository. Since sphinx-doc is involved the result is basically pure > html, > > Well, html and Javascript. IIUC search does not work without > Javascript. > > > no fancy content management system needed. > > OK, the generation of the book requires latex, and imagemagick and a few > > other things, but that's easy to setup. Otherwise only python3 and > sphinxdoc > > must be installed. > > sphinxdoc and python3 are somewhat problematic dependencies. Namely, > much of Python world is unstable, that is changes in incompatible > ways in rather short timeframe. We already had problems that > version of sphinxdoc that you use was incompatible with my > system and version I had did not work with your sources. > you can always pin down versions of python3 and its packages such as sphinx etc, by no means you must be on the latest versions > Also, batch regeneration may be OK for slowly changing things > or things tied to specific release. But I defintely do not want > to delay updates to FriCAS website waiting for release. > When page is really pure html I can update it using text editor > and immediately see results, not so with batch update. > > To put it differently, batch update is fine for "official" > documentaion. But it would be useful to have less > "official", more informal documentation. > > In ideal world we would first think about logical organization > of material that we want to present, and then think about > technology needed to do this. But I am affraid part of > problem is that there are different technologies and > they do not cooperate very nicely. And people get attached > to specific technology they use, so effort gets fragmented. > > > First we must decide whether we want the website fricas.org to be in > sync > > with the latest release or whether it should be in sync with the git > > repository. Other ideas? > > Official documentation should be with sync with latest release. > But other parts not, we should update them independently. > > -- > Waldek Hebisch > > -- > You received this message because you are subscribed to the Google Groups > "FriCAS - computer algebra system" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/fricas-devel/ZRDM9hC4mVYjICgk%40fricas.org > . > -- You received this message because you are subscribed to the Google Groups "FriCAS - computer algebra system" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/fricas-devel/CAAWYfq14-D%2BPKYSXje%3DsFO3Aq1wqgxmQWoQhea9cjb_W-2MnyQ%40mail.gmail.com.
