Re: Winning design selected

The designer said that she would work on it this weekend, so unfortunately
I don't think the timing will work :(  I do appreciate your enthusiasm
though!

On Fri, Sep 9, 2016 at 4:35 PM, Dan Roberts <[email protected]> wrote:

> Is there any chance I can get some sort of preliminary PSD today?  I'd
> really like to work on it over the weekend, come Monday I think I can
> showcase enough progress to justify going volunteer-only (but I'm not
> asking for a commitment to that decision)
>
> I also think our translation needs will make selecting a professional very
> difficult and/or expensive, and we may end up needing to do it ourselves
> anyways.
>
> Cheers,
> Dan
>
> On Sep 8, 2016 8:24 AM, "Ian Clarke" <[email protected]> wrote:
>
>> On Thu, Sep 8, 2016 7:21 AM, Steve Dougherty [email protected]
>> wrote:> What is your timeline for the whole site, or was two weeks your
>> target?
>> We
>>
>> > have a massive amount of copy to rewrite (and translations to redo?),
>> and
>>
>> > pages to restructure, or do you plan for us to get up and running with
>> the
>>
>> > old verbiage and gradually refine it? I do have some familiarity with
>>
>> > Jekyll but I have no experience with translating Jekyll sites, I'm
>>
>> > concerned about that. I do have a couple of ideas though.
>>
>>
>>
>>
>> I'd propose using the existing copy; anything else would introduce more
>>
>> delay and cause the new site to launch with less translation available.
>>
>>
>>
>>
>> While I want to get the new site launched ASAP, I have to disagree on this
>> point.  I think if we don't simplify the site significantly then it will
>> negate
>> a lot of the benefit of the redesign.  We can reintroduce content over
>> time, but
>> should do it in a way that it keeps the site looking simple for newbies
>> (while
>> allowing them to drill down to detail if they need it).
>>
>>
>> The community (and me because I get lots of source string clarification
>>
>> questions) have put a lot of effort into the translations already. The
>>
>> Spanish translations are complete; the French one has excellent (82%
>>
>> website; 97% overall) coverage.
>>
>>
>>
>>
>> This is all very valuable, but it will be very limiting if we require
>> that we
>> use all of that material on day-one of the new website.  We should launch
>> with
>> something simple, and then reintroduce this content over time, being
>> careful to
>> keep the site looking clean and simple for new users.
>> We can keep the old site on an alternate domain so nothing is lost -
>> perhaps
>> doing some kind of smart 404 redirect from the new site (although I'm not
>> sure
>> if Jekyll has that flexibility - requires investigation).
>>
>>
>> Whatever technology we use - be it through you or someone for hire - I'd
>> like to be sure it has support for localization in a way that makes it
>>
>> easy for translators to contribute. Being a Ruby thing, it looks like
>>
>> Jekyll uses YAML, which Transifex supports. Failing that, perhaps one of
>>
>> the formats Pontoon supports? [1][2]
>>
>>
>>
>>
>> Agreed, I have limited experience with localization technologies, but it
>> should
>> be a requirement for anyone that does the PSD -> Jekyll conversion that we
>> support localization.
>> Ian.
>> Ian Clarke
>> Founder, The Freenet Project
>> Email: [email protected]
>> _______________________________________________
>> Devl mailing list
>> [email protected]
>> https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
>
>


-- 
Ian Clarke
Founder, The Freenet Project
Email: [email protected]
_______________________________________________
Devl mailing list
[email protected]
https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl