I think the documentation pointers should point to Sourceforge https://sourceforge.net/projects/oorexx/files/oorexx-docs/ <https://sourceforge.net/projects/oorexx/files/oorexx-docs/>
with the appropriate subfolder renamed (currently 5.0.0beta) The documentation can be built automatically (some work needed still to rebuild only the changed docs + upload) Hälsningar/Regards/Grüsse, P.O. Jonsson oor...@jonases.se > Am 21.06.2022 um 21:34 schrieb Terry Fuller <t...@pgmguild.com>: > > On the topic of documentation... > > I don't want to connect the website issues as showstoppers for a 5.0 GA > release, but... > > All of the documentation pointers in oorexx.org/doc result in 404 errors. If > memory serves (and sometimes it doesn't, corrections gratefully received) we > now have Jenkins producing both PDF and html documentation... can that be set > up to push the build results to the website? alternatively, change the links > to point to the built files? > > Along those lines... the oorexx product brochure is pretty badly out of date > (touts the wonderful 32-bit implementations 😅 ). Once 5.0 is GA the brochure > really should be updated... also might be better implemented in something > more open source than ms.ppt. > > On 2022-06-21 05:06, René Jansen wrote: >> Another thing was documentation. There has been a lot of work done by Gil >> (and Jon and P.O. - afraid I am forgetting someone). >> >> >> >> >> _______________________________________________ >> Oorexx-devel mailing list >> Oorexx-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > -- > taf > > > > _______________________________________________ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel
_______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
