Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Esther Baruk <esther.baruk@gmail.com>
To: Amir Chaudhry <amc79@cam.ac.uk>
Cc: caml users <caml-list@inria.fr>,
	 "infrastructure@lists.ocaml.org"
	<infrastructure@lists.ocaml.org>
Subject: Re: [Caml-list] [ocaml-infra] [ANN] New OCaml.org design is now live!
Date: Thu, 21 Nov 2013 10:53:10 +0100	[thread overview]
Message-ID: <CAFzMiE2vqdW38c5xc=1fv8BA_PAXZwdxAYTOLvB0vjRi97yF=Q@mail.gmail.com> (raw)
In-Reply-To: <ACA7BF27-1EC8-4FCD-B99B-332AA9A0F9DF@cam.ac.uk>

[-- Attachment #1: Type: text/plain, Size: 3770 bytes --]

Wow, this is really great !
It has really changed compared to its first design :)

Congratulations and thanks for all the great work that has been done !

Cheers,

Esther


On Thu, Nov 21, 2013 at 12:08 AM, Amir Chaudhry <amc79@cam.ac.uk> wrote:

> Dear caml-list,
>
> As some of you may have noticed, the new OCaml.org site is now live!
>
> The DNS may still be propagating so if http://ocaml.org hasn't updated
> for you then try http://166.78.252.20.  This post is in two parts: the
> first is the announcement and the second is a call for content.
>
>
> ### New OCaml.org website design!
>
> The new site represents a major milestone in the continuing growth of the
> OCaml ecosystem. It's the culmination of a lot of volunteer work over the
> last several months and I'd specifically like to thank Christophe, Ashish
> and Philippe for their dedication (the commit logs speak volumes).
>
> We began this journey just over 8 months ago with paper, pencils and a lot
> of ideas. This led to a comprehensive set of wireframes and walk-throughs
> of the site [1], which then developed into a collection of Photoshop
> mockups [2].  In turn, these formed the basis for the html templates and
> style sheets, which we've adapted to fit our needs across the site.
>
> Alongside the design process, we also considered the kind of structure and
> workflow we aspired to, both as maintainers and contributors.  This led us
> to develop completely new tools for Markdown and templating in OCaml [3, 4,
> 5], which are now available in OPAM for the benefit all.  Working on all
> these things in parallel definitely had it challenges (which I'll write
> about separately) but the result has been worth the effort.
>
> The journey is ongoing and we still have many more improvements we hope to
> make. The site you see today primarily improves upon the design, structure
> and workflows but in time, we also intend to incorporate more information
> on packages and documentation. With the new tooling, moving the website
> forward will become much easier and I hope that more members of the
> community become involved in the generation and curation of content.  This
> brings me to the second part of this post.
>
>
> ### Call for content
>
> We have lots of great content on the website but there are parts that
> could do with refreshing and gaps that could be filled.  As a community
> driven site, we need ongoing contributions to ensure that the site best
> reflects its members.
>
> For example, if you do commercial work on OCaml then maybe you'd like to
> add yourself to the support page [6]? Perhaps there are tutorials you can
> help to complete, like 99 problems [7]?  If you're not sure where to begin,
> there are already a number of content issues you could contribute to [8].
>
> Although we've gone through a bug-hunt already, feedback on the site is
> still very welcome.  You can either create an issue on the tracker
> (preferred), or email the infrastructure list.
>
> It's fantastic how far we've come and I look forward to the next phase!
>
> Best wishes,
> Amir
>
>
> [1] http://amirchaudhry.com/wireframe-demos-for-ocamlorg/
> [2] https://github.com/ocaml/ocaml.org/wiki/Site-Redesign
> [3] http://lists.ocaml.org/pipermail/infrastructure/2013-July/000211.html
> [4] http://pw374.github.io/posts/2013-09-05-22-31-26-about-omd.html
> [5]
> http://pw374.github.io/posts/2013-10-03-20-35-12-using-mpp-two-different-ways.html
> [6] http://ocaml.org/community/support.html
> [7] http://ocaml.org/learn/tutorials/99problems.html
> [8] https://github.com/ocaml/ocaml.org/issues?labels=content
>
> _______________________________________________
> Infrastructure mailing list
> Infrastructure@lists.ocaml.org
> http://lists.ocaml.org/listinfo/infrastructure
>

[-- Attachment #2: Type: text/html, Size: 5271 bytes --]

      reply	other threads:[~2013-11-21  9:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-20 23:08 [Caml-list] " Amir Chaudhry
2013-11-21  9:53 ` Esther Baruk [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAFzMiE2vqdW38c5xc=1fv8BA_PAXZwdxAYTOLvB0vjRi97yF=Q@mail.gmail.com' \
    --to=esther.baruk@gmail.com \
    --cc=amc79@cam.ac.uk \
    --cc=caml-list@inria.fr \
    --cc=infrastructure@lists.ocaml.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox