Re: Should we just go ahead and redesign the website?

+1 in favor of immediate action on the website.

The wiki was really supposed to be the developer resource originally,
right? So a separate place for developer doc seems not only logical but
also something we've already wanted in the past.

On Aug 6, 2016 12:03 PM, "Ian Clarke" <[email protected]> wrote:

> When I've raised the subject of a website redesign in the past, the only
> voices
> I heard in response were opposed to it.
> But it appears that some people agreed with me yet remained silent at the
> time,
> giving me the misleading impression that I had a minority view.
> I'm happy to carve off up-to $5k of that $25k right now, commission a new
> design
> on 99designs (probably around $1k), get a service like
> https://thesiteslinger.com/ to convert it to HTML (probably a few hundred
> $$ -
> I've worked with them before, they're good), and from there we can set it
> up,
> perhaps using Github Pages.
> I think we should reduce the amount of content on the main website
> significantly, limiting it to user-focussed content like explaining what
> Freenet
> is and how to use it.
> Developer docs and other more detailed information can be migrated to
> Github
> wiki and linked from the main website.
> This can be handled separately to the prioritization process.
> Thoughts?
> Ian.
> Ian Clarke
> Founder, The Freenet Project
> Email: [email protected]
> _______________________________________________
> Devl mailing list
> [email protected]
> https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
_______________________________________________
Devl mailing list
[email protected]
https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl