Hi folks,

On Tue, Jul 29, 2014 at 2:30 PM, Gershom B <[email protected]> wrote:

> Cc: admin, committee.
>
> My personal sense is that at the moment we should take the path of
> least resistance, which I understand is a new, separate platform site
> that looks _sorta_ like the proposed new one, but also isn't the new
> one, and isn't integrated with anything in particular?
>

+1. I think as long as it's linked prominently from both the current and
new-www, it should be fine for now.

>
> The key thing is to get the platform out and ready to go. When new-www
> is ready to go, we can look at how stuff ties together, but its ok to
> let things slip out of sync in the meantime.
>

Yep, in the long run it'd be nice to have a consistent visual identity
across the most prominent pages, but it's certainly more important to get a
modern Platform out there.

>
> In general, I advocate keeping a separate platform site perhaps even
> with a new domain such as platform.haskell.org, so that platform
> changes don't affect main website changes and vice-versa.
>

Another +1, as long as this wouldn't be difficult from a technical admin
point of view. The Platform is distinct from Haskell the language, and
while it might be nice to eventually run them from the same app, this
separation would be nice to maintain.

Cheers,
Adam

>
> On Tue, Jul 29, 2014 at 4:49 PM, Mateusz Kowalczyk
> <[email protected]> wrote:
> > On 07/29/2014 10:42 PM, Mark Lentczner wrote:
> >> As you all probably know, HP is about to release 2014.2.0.0. One of my
> last
> >> remaining chores is to update the website.
> >>
> >> Back at the start of the year, I had hoped to get some volunteer help in
> >> revamping the Haskell Platform site, as I was going to templatize the
> site
> >> (since much of the data on it comes from the build itself), and move
> away
> >> from hand updating all the detailed info. I got a volunteer (Erin Depew)
> >> who started working on some ideas.
> >>
> >> Then Chris' concept site appeared, and I put Erin and Chris in touch. At
> >> that point Erin switched to building somethin harmonious with Chris'
> >> design. But, until things were sorted out with how Chris' design would
> be
> >> deployed, Erin's work is a separate thing (no shared templates or CSS).
> >>
> >> I'm a bit down to the wire, and I understand from Chris that this team
> is
> >> now working to put out the new design. And I see
> http://new-www.haskell.org/
> >> is up.
> >>
> >> So, I'm looking for some direction from you:
> >>
> >> 1) Do you intend / want the HP site to continue to be a separate site,
> or
> >> do you want to see it integrated into the new main Haskell site more so
> >> than it was before?
> >
> > AFAIK, it has not been decided or even discussed whether
> > new-www.haskell.org thing is to become the new main site so asking about
> > integrating with that one might be a bit premature.
> >
> >> 2) Is there common resources for the new look that the Platform site
> should
> >> use?
> >> 3) Is any of this ready to go enough that I should base this Friday's HP
> >> annoucement and newsite on it? Or should I just work with the old design
> >> for the moment? (That isn't the path of least resistance because to do
> the
> >> old design I need to either a) edit it all by hand (again!), or b)
> >> templatize the old site (wasted work).)
> >>
> >> - Mark
> >>
> >>
> >>
> >> _______________________________________________
> >> haskell-infrastructure mailing list
> >> [email protected]
> >> http://community.galois.com/mailman/listinfo/haskell-infrastructure
> >>
> >
> >
> > --
> > Mateusz K.
> > _______________________________________________
> > haskell-infrastructure mailing list
> > [email protected]
> > http://community.galois.com/mailman/listinfo/haskell-infrastructure
>
_______________________________________________
haskell-infrastructure mailing list
[email protected]
http://community.galois.com/mailman/listinfo/haskell-infrastructure

Reply via email to