Perhaps you all are not aware that the reason the wiki has been shut down numerous times is that the load generated on the free server we get from pair.com has exceeded the level they are willing to accept.
Any solution we pick which would increase the load on that server would only ensure that they move it offline more frequently. (any CMS would only increase the load from the current site) Thus the desire for a more static solution. I hope to have something to try online in the next day or so. We can try the work flow and see if it's reasonable for the scons.org website. (Once again.. not the wiki). If so then some light skinning of the design should make it more SCons like and then could be deployed. -Bill On Fri, May 15, 2015 at 1:42 AM, anatoly techtonik <[email protected]> wrote: > On Thu, May 14, 2015 at 11:22 PM, Dirk Bächle <[email protected]> wrote: > > someone has to actually write and publish stuff with the selected > > technology. > > I'm definitely more interested in the latter > > So, the question is the workflow or design? > > Current workflow requires access to repository, and update on server > side is manual. This can be changed to update server side > automatically. > > Going with site generator won't add a form to post announcements to > social media. > > -- > anatoly t. > _______________________________________________ > Scons-dev mailing list > [email protected] > https://pairlist2.pair.net/mailman/listinfo/scons-dev >
_______________________________________________ Scons-dev mailing list [email protected] https://pairlist2.pair.net/mailman/listinfo/scons-dev
