From dev-return-87990-apmail-lucene-dev-archive=lucene.apache.org@lucene.apache.org Wed Feb 1 00:35:01 2012 Return-Path: X-Original-To: apmail-lucene-dev-archive@www.apache.org Delivered-To: apmail-lucene-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2A7E595F3 for ; Wed, 1 Feb 2012 00:35:01 +0000 (UTC) Received: (qmail 17787 invoked by uid 500); 1 Feb 2012 00:34:59 -0000 Delivered-To: apmail-lucene-dev-archive@lucene.apache.org Received: (qmail 17708 invoked by uid 500); 1 Feb 2012 00:34:59 -0000 Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@lucene.apache.org Delivered-To: mailing list dev@lucene.apache.org Received: (qmail 17701 invoked by uid 99); 1 Feb 2012 00:34:58 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Feb 2012 00:34:58 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [174.121.162.194] (HELO r2-dallas.webserversystems.com) (174.121.162.194) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Feb 2012 00:34:53 +0000 Received: from 35.79-161-195.customer.lyse.net ([79.161.195.35] helo=[192.168.10.109]) by r2-dallas.webserversystems.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from ) id 1RsO9g-00086W-Fz for dev@lucene.apache.org; Tue, 31 Jan 2012 18:34:32 -0600 From: =?iso-8859-1?Q?Jan_H=F8ydahl?= Mime-Version: 1.0 (Apple Message framework v1251.1) Content-Type: multipart/alternative; boundary="Apple-Mail=_574E9124-18CF-427A-A74C-01B06F3C26CD" Subject: Re: [DISCUSS] New Website Date: Wed, 1 Feb 2012 01:34:30 +0100 In-Reply-To: To: dev@lucene.apache.org References: Message-Id: <9794AA6D-F94D-486E-AD40-7D07080DA547@cominvent.com> X-Mailer: Apple Mail (2.1251.1) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - r2-dallas.webserversystems.com X-AntiAbuse: Original Domain - lucene.apache.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - cominvent.com X-Source: X-Source-Args: X-Source-Dir: --Apple-Mail=_574E9124-18CF-427A-A74C-01B06F3C26CD Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 +1, looks much more inviting for everyone! Great work. Minors: * Enlarge the search box so the full text "Search with Apache Solr..." = is visible. Hey, it's the home page of the world's best search engine, = search should be prominent - so why not make the search box muuuch wider = and add AutoComplete. * Why is the search automatically constrained to the "Lucene-Core" = project, even when searching from /solr/? If I am at Solr home page and = search "tutorial", the first hit should be the Solr tutorial, not the = Lucene one. -- Jan H=F8ydahl, search solution architect Cominvent AS - www.cominvent.com Solr Training - www.solrtraining.com On 31. jan. 2012, at 20:38, Grant Ingersoll wrote: > As many of you know, I've been doing a slow burn on switching us over = to the new ASF CMS. I'm finally at a point where I think we are ready, = for the most part, so I'd like to propose we make the leap and switch. = I finally had time to figure out a workaround for INFRA-3850 and have = released the logjam caused by that blocker in terms of the L&F of the = site. >=20 > You can see the new site at http://lucene.staging.apache.org/. I've = ported almost all of the existing sites and done a lot to make it look = better in terms of getting the CSS right, etc. >=20 > The new site is almost dead simple to edit: =20 >=20 > 1. svn co https://svn.apache.org/repos/asf/lucene/cms/trunk cms/trunk > 2. svn co https://svn.apache.org/repos/infra/websites/cms/build if you = wish to build and test locally > a. http://www.apache.org/dev/cmsref.html#local-build for details = on building locally. If you are on a mac, you may need some perl = dependencies installed. > b. cd asf-cms > c. ./build_site.pl --target-base=3D --source=3D../trunk/ > 3. Edit the files in cms/trunk/content and cms/trunk/templates as you = see fit. When you are satisfied, svn commit. > 4. Browse to the staging site to see them live. > 5. TBD: publish to the main site. I'll figure that out when switching = and post. >=20 > Markdown Reference: http://daringfireball.net/projects/markdown/syntax > CMS Reference: http://www.apache.org/dev/cmsref.html and = http://www.apache.org/dev/cms.html >=20 > (This info is available on the site at: = http://lucene.staging.apache.org/site-instructions.html) >=20 > The whole process is 1000x easier than Forrest. You can even edit via = the web using a WYSWIG editor if you so desire. >=20 > !!!!!!!!!!!!!!!********************* > Now, here's the kicker, I'd like to switch to the new sites over this = weekend or early next week at the latest and then iterate from there. I = don't have a solution for the Core versioned docs yet, but those can be = figured out later. Presumably we can convert them to markdown at some = point before the next release and just maintain pointers to the old = versions. > !!!!!!!!!!!!!!!********************* >=20 > So, I'd suggest everyone give it a pass through, fix items as they see = them and/or otherwise pitch in and help, because I'm tired of our = current site and how poor it makes us look. =20 >=20 > -Grant >=20 >=20 >=20 >=20 --Apple-Mail=_574E9124-18CF-427A-A74C-01B06F3C26CD Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1 +1, = looks much more inviting for everyone! Great = work.

Minors:
* Enlarge the search box so = the full text "Search with Apache Solr..." is visible. Hey, it's the = home page of the world's best search engine, search should be prominent = - so why not make the search box muuuch wider and add = AutoComplete.
* Why is the search automatically constrained to = the "Lucene-Core" project, even when searching from /solr/? If I am at = Solr home page and search "tutorial", the first hit should be the Solr = tutorial, not the Lucene one.

--
Jan = H=F8ydahl, search solution architect
Cominvent AS - www.cominvent.com
Solr Training = - www.solrtraining.com

On 31. jan. 2012, at 20:38, Grant Ingersoll = wrote:

As many of you = know, I've been doing a slow burn on switching us over to the new ASF = CMS.  I'm finally at a point where I think we are ready, for the = most part, so I'd like to propose we make the leap and switch.  I = finally had time to figure out a workaround for INFRA-3850 and have = released the logjam caused by that blocker in terms of the L&F of = the site.

You can see the new site at http://lucene.staging.apache.or= g/.  I've ported almost all of the existing sites and done a = lot to make it look better in terms of getting the CSS right, = etc.

The new site is almost dead simple to = edit:  

2. svn = co https://svn= .apache.org/repos/infra/websites/cms/build if you wish to build and = test locally
a. http://www.apac= he.org/dev/cmsref.html#local-build for details on building = locally.  If you are on a mac, you may need some perl dependencies = installed.
b. cd asf-cms
= c. ./build_site.pl --target-base=3D<path to output on = local HTTPd server, I use ~/Sites> --source=3D../trunk/
3. =  Edit the files in cms/trunk/content and cms/trunk/templates as you = see fit.  When you are satisfied, svn commit.
4. Browse = to the staging site to see them live.
5. TBD: publish to the = main site.  I'll figure that out when switching and = post.


(This info is available on the site = at: http://lu= cene.staging.apache.org/site-instructions.html)

The whole process is 1000x easier than Forrest.  You can even = edit via the web using a WYSWIG editor if you so = desire.

!!!!!!!!!!!!!!!*********************
Now, here's the kicker, I'd like to switch to the new sites over = this weekend or early next week at the latest and then iterate from = there.  I don't have a solution for the Core versioned docs yet, = but those can be figured out later.  Presumably we can convert them = to markdown at some point before the next release and just maintain = pointers to the old = versions.
!!!!!!!!!!!!!!!*********************

So, I'd suggest everyone give it a pass through, fix items as = they see them and/or otherwise pitch in and help, because I'm tired of = our current site and how poor it makes us look. =  

-Grant


=



= --Apple-Mail=_574E9124-18CF-427A-A74C-01B06F3C26CD--