I guess another possibility we can consider, at least as an interim step, is to host the static site on our existing server. This would at-least allow us to get the new site up quickly, but of course it wouldn't solve the headache of having to pay for and administer our own web server. There may be an easy way here to solve the internationalization problem without relying on JavaScript.
On Sun, Oct 30, 2016 11:37 AM, Dan Roberts ademan...@gmail.com wrote: Bumping this. My apologies for the lack of update on the website, the past three weeks I've been working 60+ hours a week preparing for a trade show. At this point I consider the hosting platform to a blocker for completing the website redesign. Shall I proceed for the moment assuming that we're using github pages? If we abandon github pages, that frees me to identify and select a more i18n friendly site generator, so I haven't put much more work into the Jekyll version. At present the Jekyll version's English translation is effectively complete, however I do think some content curation will be necessary to better fit the new format. Thanks, Dan On Oct 15, 2016 1:05 PM, "Ian Clarke" <i...@freenetproject.org> wrote: > > On Sat, Oct 15, 2016 11:22 AM, Florent Daigniere nextg...@freenetproject.org > wrote: > > Almost all users will have JS. > > > Our user-base is less likely than the average to have it enabled, that's > > why I am pointing it out here. > > > > > Perhaps. > Or S3/cloudfront or something else. Speaking of which, do we plan to > > drop SSL support too? Or the domain that we have been using for a decade > > and a half? > > > > > From https://help.github.com/articles/securing-your-github-pages-site-with-https/ > > "HTTPS is not supported for GitHub Pages using custom domains." > > > > > That is definitely troubling, is this the first time this problem has been > raised? I don't recall seeing anyone mention this before. > S3/cloudfront are options if we keep the site static, but then that would have > the limitations you've already pointed out with respect to internationalization. > Google App Engine should be able to address the internationalization problem, it > does (or at least it did once) have the limitation that the URL needs to begin > with "www", but we can set up a redirect if necessary for that. > Ian. > > Ian Clarke > Founder, The Freenet Project > Email: i...@freenetproject.org > _______________________________________________ > Devl mailing list > Devl@freenetproject.org <Devl@freenetproject.org> > https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl <https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl> _______________________________________________ Devl mailing list Devl@freenetproject.org https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl --Ian ClarkeStacks - The AI CFO for your personal financeshttp://trystacks.com/ _______________________________________________ Devl mailing list Devl@freenetproject.org https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
