I agree with whomever said we need to think about the redesign first. We
need to figure out what the communication goals of the website and then go
from there.
For example the current website seems to have most of the following:
- External:
- Attract new users
- Attract new contributors
- Fundraising
- Internal:
- Provide a place for contributors to organize themselves
- Keep the community updated on important updates
- Access important information about the Foundation or Project
These may be too many goals, or the wrong ones, but it's a place to start.
Once we have our goals set out, we can reboot the experience to reach those
goals.
On Tue, Sep 6, 2016 at 9:35 AM, Andreas Nilsson <[email protected]> wrote:
> On 2016-09-06 18:03, Sriram Ramkrishna wrote:
>
>
> I agree with Andreas, we had that solution before and it didn't really pan
> out. It was huge relief to actually switch into wordpress at the time.
>
>
> Well, gnomeweb-wml also had some very specific pain points, in particular
> it's build system, that other static generators necessary won't have.
>
> Fabiana mentioned over lunch that gnome.org uses wordpress a bit
> backwards in places. Some parts that belongs in the content, are actually
> hardcoded in the theme, and some layout things, that should live in the
> theme, are done in the content. So it would probably be good to clean that
> up as part of a redesign of gnome.org, if we decide to remain with the
> current system.
> - Andreas
>
> _______________________________________________
> engagement-list mailing list
> [email protected]
> https://mail.gnome.org/mailman/listinfo/engagement-list
>
>
--
............................................................
.................
*Nuritzi Sanchez* | +1.650.218.7388 | Endless <http://endlessm.com/>
_______________________________________________
engagement-list mailing list
[email protected]
https://mail.gnome.org/mailman/listinfo/engagement-list
