Re: [freenet-dev] Internationalization on the new site

Since you guys (Dan and Florent) are the two guys volunteering to do the actual work here, I'm hopeful you can come to an agreement between you about how to proceed, otherwise we'll be dead in the water with it (which is exactly what I had hoped to avoid). We do now have a credit card and so we

Re: [freenet-dev] Internationalization on the new site

Hi Florent, I understand you're averse to the ruby ecosystem, and for good reason, however I see jekyll+plugins as the path of least resistance between us and a functioning site. I want to constrain the scope of this work, and I am afraid that a survey of static site generators and translation

Re: [freenet-dev] Internationalization on the new site

There is a misunderstanding here... either we can satisfy ourselves with github pages' version of jekyll and plugins... or we won't use jekyll at all. The last thing we need is a jekyll plugin that we can't use on github pages! Ian has arranged for the project to have a debit card ... so now we

Re: [freenet-dev] Internationalization on the new site

We had some discussions in IRC over the past week around the i18n, modifying content vs deploying as-is, and gettext. Since we dropped github pages as our target, I'm looking into writing a small plugin for Jekyll today to aid i18n support, I'm also going to double check that there's no existing

Re: [freenet-dev] Internationalization on the new site

Guys, where are we on this?  It's been several weeks since the last update. On Mon, Nov 7, 2016 1:10 AM, x...@freenetproject.org wrote: On Wednesday, November 02, 2016 10:52:39 PM Dan Roberts wrote: > I'm doing my best to avoid any "design" decisions, so I had no plan to > include the

Re: [freenet-dev] Internationalization on the new site

On Thu, 2016-11-03 at 11:51 +, Matthew Toseland wrote: > On 03/11/16 05:52, Dan Roberts wrote: > > On Tue, Nov 1, 2016 at 2:26 AM, Florent Daigniere < > > nextg...@freenetproject.org> wrote: > > > > > > > > Do you have any plan to handle the bank-balance stuff? Or is that > > > gone > > > in

Re: [freenet-dev] Internationalization on the new site

On 03/11/16 05:52, Dan Roberts wrote: > On Tue, Nov 1, 2016 at 2:26 AM, Florent Daigniere < > nextg...@freenetproject.org> wrote: > >> >> Do you have any plan to handle the bank-balance stuff? Or is that gone >> in the new design? > I'm doing my best to avoid any "design" decisions, so I had no

Re: [freenet-dev] Internationalization on the new site

On Tue, Nov 1, 2016 at 2:26 AM, Florent Daigniere < nextg...@freenetproject.org> wrote: > On Tue, 2016-11-01 at 01:05 -0700, Dan Roberts wrote: > > On Mon, Oct 31, 2016 at 7:01 AM, Florent Daigniere > > wrote: > > > On Sun, 2016-10-30 at 09:37 -0700, Dan Roberts

Re: [freenet-dev] Internationalization on the new site

Hi Arne, I wasn't aware of that but I definitely am interested. Per the original design, the social buttons are only links anyways, so there shouldn't be any privacy concern there, but if we want to embed a like button, I think we ought to employ your solution. Thanks, Dan On Tue, Nov 1,

Re: [freenet-dev] Internationalization on the new site

Dan Roberts writes: > We need to decide what to do with regards to the social media links > peppered throughout the design. Stripping them leaves the header and footer > looking fairly barren, and I think there may be some value in having some > extra social media presence (even if it's little

Re: [freenet-dev] Internationalization on the new site

On Tue, 2016-11-01 at 01:05 -0700, Dan Roberts wrote: > On Mon, Oct 31, 2016 at 7:01 AM, Florent Daigniere > wrote: > > On Sun, 2016-10-30 at 09:37 -0700, Dan Roberts wrote: > > > At this point I consider the hosting platform to a blocker for > > > completing the

Re: [freenet-dev] Internationalization on the new site

On Mon, Oct 31, 2016 at 7:01 AM, Florent Daigniere < nextg...@freenetproject.org> wrote: > On Sun, 2016-10-30 at 09:37 -0700, Dan Roberts wrote: > > At this point I consider the hosting platform to a blocker for > > completing the website redesign. > > > You shouldn't. I'm a bit concerned that

Re: [freenet-dev] Internationalization on the new site

On Sun, 2016-10-30 at 09:37 -0700, Dan Roberts wrote: > At this point I consider the hosting platform to a blocker for > completing the website redesign. You shouldn't. > Shall I proceed for the moment assuming that we're using github > pages?  Yes; We might put something in front, but that's

Re: [freenet-dev] Internationalization on the new site

On Sun, Oct 30, 2016 1:10 PM, Florent Daigniere nextg...@freenetproject.org wrote: Yes, AWS is something I've practised recently and it won't be a problem... The only real question is how we will deal with the billing (few cents a month but it has to be paid by card). That's ok, I should be

Re: [freenet-dev] Internationalization on the new site

On Sun, 2016-10-30 at 17:47 +, Ian Clarke wrote: > I'm open to AWS, however if Dan has already built on Jekyll will there > be a lot of work to switch to something like Hugo? I don't think so; We don't need any fancy feature. > Still an imperfect solution to the internationalization

Re: [freenet-dev] Internationalization on the new site

I'm open to AWS, however if Dan has already built on Jekyll will there be a lot of work to switch to something like Hugo? Still an imperfect solution to the internationalization problem, but perhaps we just need to accept that. Florent, if we decide to go with AWS, will you have time to to set

Re: [freenet-dev] Internationalization on the new site

I forgot the main advantage of the solution I'm proposing: AWS will get us a free wildcard certificate for everything we host on their infrastructure (we're currently paying for it and it will come due for renewal in April) without us having to fill in any paperwork (it's been a problem in the

Re: [freenet-dev] Internationalization on the new site

On Sun, 2016-10-30 at 16:58 +, Ian Clarke wrote: > 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

Re: [freenet-dev] Internationalization on the new site

My favourite solution would be based on AWS: S3 for storage, cloudfront as a CDN in front A Lambda function to trigger rebuilds when the bucket is updated (or an api-endpoint we'd get github to trigger on commit) As for the static-page generator, I am allergic to ruby's ecosystem. Not because

Re: [freenet-dev] Internationalization on the new site

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

Re: [freenet-dev] Internationalization on the new site

On Sun, Oct 30, 2016 11:37 AM, Dan Roberts ademan...@gmail.com wrote: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

Re: [freenet-dev] Internationalization on the new site

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

Re: [freenet-dev] Internationalization on the new site

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

Re: [freenet-dev] Internationalization on the new site

On Sat, 2016-10-15 at 14:33 +, Ian Clarke wrote: > On Sat, Oct 15, 2016 12:49 AM, Florent Daigniere nextgens@freenetproje > ct.org > wrote: > In any case the result is inferior to the current solution. It will: > - require user-interaction (and an ugly UX element) to switch language > (for

Re: [freenet-dev] Internationalization on the new site

On Sat, Oct 15, 2016 12:49 AM, Florent Daigniere nextg...@freenetproject.org wrote: In any case the result is inferior to the current solution. It will: - require user-interaction (and an ugly UX element) to switch language (for those without JS) Almost all users will have JS. - require JS

Re: [freenet-dev] Internationalization on the new site

On Fri, 2016-10-14 at 20:19 +, Ian Clarke wrote: > I posted a question to Reddit about how we can internationalize a > Github Pages > site, there are a few answers already: > https://www.reddit.com/r/github/comments/57gjpj/what_are_bestpractices > _for_localization_of_a/ > Thoughts? > You've