-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi Dave,
Hosting a static site is a non-issue. We can easily do it on SL servers. We can even configure it to automatically rebuild on git update. I would not use github pages. It does not yet support TLS, which is very important in this day and age. Don't let Jekyll limit you either. I have not compared it to other solutions, especially not when making a wiki. We can run anything on our servers. Could this project also merge the developer site back into the static-wiki? Right now it feels very oddly separated. Thanks, Sam On 12 April 2016 7:51:12 AM AEST, Dave Crossland <[email protected]> wrote: >Hi Sebastian! > >In the "Seeking insights into Oversight_Board/Decisions" thread you >said, > >On 11 April 2016 at 14:57, Sebastian Silva <[email protected]> > wrote: > >> El 11/04/16 a las 13:56, Walter Bender escribió: >> >> >>> Generally I think all mediawiki instances should be retired and >replaced >>> with a static site generator backed by a distributed version control >"pull >>> request" model of collaboration. >>> >>> http://designwithfontforge.com has semi-prominent "edit this page" >(that >>> could be even more prominent) and Github itself and 3rd party web >editors >>> like http://prose.io provide the "wiki" experience of editing pages >>> directly, but with the PR permissions model that - IMHO - cultivates >more >>> quality. >>> >> Mediawiki has been an administration burden from infrastructure team >and >> Local Labs as well. >> >> +1 on static site generators. Last year we replaced Wordpress for >Nikola >> at somosazucar.org. Lektor is also interesting. Both are small enough >to >> fit into a Sugar Activity for offline scenarios :-) > > >Both are pure python too. Cool :) > >I propose using https://pages.github.com for hosting the site, and thus >the >Jeykll static site generator (writte in ruby) > >If Nikola/Lektor/anything-else is used as the static site generator, >the >site source can be hosted on github, and travis can be used to run the >SSG >and upload the build to a server via SFTP or git or similar (in a >secure >way.) > >Here are some explanations: > >https://docs.travis-ci.com/user/deployment/custom/ > >https://docs.travis-ci.com/user/uploading-artifacts/ > >How to decide hosting sites on pages.github.com or elsewhere? > >Cheers >Dave > > >------------------------------------------------------------------------ > >_______________________________________________ >IAEP -- It's An Education Project (not a laptop project!) >[email protected] >http://lists.sugarlabs.org/listinfo/iaep - -- Sent from my phone. Please excuse my brevity. -----BEGIN PGP SIGNATURE----- Version: APG v1.1.1 iQJOBAEBCgA4BQJXDGu4MRxTYW0gUC4gKE1vYmlsZSBOZXh1cyA0IEN5YW5vZ2Vu KSA8c2FtQHNhbS50b2RheT4ACgkQvdyMwXnhrYM4Jg/+IlF46KWPehevVCHoDM75 yeOO0b4fzt7c5d557L+ASvIA2vyiGcPYLeSvVxUQRoFjaLn3r1eoL8AuWZkt0okD Bqqxtz3n0SL5rwzH9f3c+iJSsKg98JrnoVMYHcs4T/pCiVYs85UY906HMjGDsOOs fbWvy0qU1vA5RHwX2iRjVzAjQG9z9cbL28VuxpxbDaRxkE1d8PRCK64PlwvQkOHy 63z7fhGbsnqFcEuaJ8pZ/e3/XKhscP3rrAvSAAAMKT12FjZh87Dc/vtJza9D9HO9 QzkOqtiCSjEshhEJ1TanwTxvesgRPMMUsmqcYrW0pUgbgT2wxBFCMv7g/OqzWV26 mt/vjU/ewN0f5CCAeP0B5vS8m09tqkqGj9C+CeA8kBI7c53WF5vpdRTJ/OV+NEZ3 xyv/B7o9t0BxrFKFJjbnV3cli0xhGlvBI23FXe5DR7VXH1u3PkKXSS590GgjLKrB jU0f0Idvu1/KHLpS2cMqPlAeEIF1q8x9GRIe/x/g56r2/Y7RvmSYk/3urtNj0oim MxhBpVjGWSheNj6A1p7+tn5B/uqI9YZnWuSqoWopCQGbuDCZLr6wuHXTibLU4EHL 3H77O3WZOBK6HtE7abBXsnb3g/D0e4TMQL4PLgI3908nk5eBFtof6ETy46BolkE8 idY2QmYF7tqlSATiiSK2FP8= =D9j4 -----END PGP SIGNATURE----- _______________________________________________ IAEP -- It's An Education Project (not a laptop project!) [email protected] http://lists.sugarlabs.org/listinfo/iaep
