Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 7984F200C28 for ; Mon, 13 Mar 2017 17:41:41 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 7823C160B6C; Mon, 13 Mar 2017 16:41:41 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id C0A5B160B5D for ; Mon, 13 Mar 2017 17:41:40 +0100 (CET) Received: (qmail 28661 invoked by uid 500); 13 Mar 2017 16:41:40 -0000 Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list dev@ignite.apache.org Received: (qmail 28633 invoked by uid 99); 13 Mar 2017 16:41:39 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 13 Mar 2017 16:41:39 +0000 Received: from [192.168.75.221] (c-73-222-138-29.hsd1.ca.comcast.net [73.222.138.29]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id E43E51A0193 for ; Mon, 13 Mar 2017 16:41:38 +0000 (UTC) From: Denis Magda Content-Type: multipart/alternative; boundary="Apple-Mail=_83CCCC79-1F0E-49DB-89AC-71983B371386" Mime-Version: 1.0 (Mac OS X Mail 10.2 $3259$) Subject: Re: More SEO and API doc cleanup Date: Mon, 13 Mar 2017 09:41:37 -0700 References: <94050632-077A-4B38-8761-2F061B5E4FB1@apache.org> <08532A13-43C9-47E6-9635-A47531738DE2@gridgain.com> To: dev@ignite.apache.org In-Reply-To: <08532A13-43C9-47E6-9635-A47531738DE2@gridgain.com> Message-Id: <7F7FEE06-258C-4E27-A9BE-85C1EEF84A9A@apache.org> X-Mailer: Apple Mail (2.3259) archived-at: Mon, 13 Mar 2017 16:41:41 -0000 --Apple-Mail=_83CCCC79-1F0E-49DB-89AC-71983B371386 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > 2. Add the following tag to all .html files: > " = /> >=20 > Bear in mind to change the url accordingly. For example, for java = index version would be: /releases/latest/javadoc/index.html = Has the tag to be added to the html files of the latest documentation? = Don=E2=80=99t think that we should update all the files all the times. =E2=80=94 Denis > On Mar 13, 2017, at 8:22 AM, Mauricio Stekl = wrote: >=20 > Hi Denis,=20 >=20 > Thanks for taking care of the marge!=20 >=20 > About the latest doc reference, when a new version is released it = would be necessary to do 2 things: >=20 > 1. Update the new version number on the .htaccess file:=20 >=20 > RewriteRule ^releases/latest/(.*)$ /releases/1.9.0/$1 [L] >=20 > 2. Add the following tag to all .html files: > " = /> >=20 > Bear in mind to change the url accordingly. For example, for java = index version would be: /releases/latest/javadoc/index.html = >=20 > This 2nd step can be done with any simple script. In particular I = wrote/use the attached .php scripts which, besides this task, also does = other things related to SEO (adding noindex, GA tracking code, etc). It = contains some basic comments with instructions. >=20 >=20 > Anyway, I do volunteer to do these 2 simple steps every time a new = release is done.=20 >=20 > Best, > Mauricio Stekl >=20 >=20 >=20 >=20 > >=20 >> On Mar 10, 2017, at 19:37, Denis Magda > wrote: >>=20 >> Hello Mauricio, >>=20 >> Thanks a lot, I=E2=80=99ve reviewed and merged your changes! >>=20 >>> - Setup rewrite rule on .htaccess so latest API doc can have = always the same URL ( for example = https://ignite.apache.org/releases/latest/javadoc/ = >) In this case I = pointed it to version 1.9.0. This will prevent having to manually change = all inbound links every time a new release is done. Also will help = search engines to correctly identify the latest documentation that = should be listed on results. >>=20 >>=20 >> Many special thanks for this improvement. I wish we did this earlier. >>=20 >> BTW, what we need to do to update this latest doc reference when a = new version is rolled out? Could you share the instructions? >>=20 >> =E2=80=94 >> Denis >>=20 >>> On Mar 10, 2017, at 1:54 PM, Mauricio Stekl > wrote: >>>=20 >>> Hello Igniters,=20 >>>=20 >>> I am sending a .patch file attached with some changes related to SEO = that I have done to Apache Ignite website.=20 >>>=20 >>> Here are some details:=20 >>>=20 >>> - Setup rewrite rule on .htaccess so latest API doc can have = always the same URL ( for example = https://ignite.apache.org/releases/latest/javadoc/ = >) In this case I = pointed it to version 1.9.0. This will prevent having to manually change = all inbound links every time a new release is done. Also will help = search engines to correctly identify the latest documentation that = should be listed on results. >>> - Added NOINDEX meta tag to all API documentation for versions = <=3D 1.8.0. This will help crawlers to give more page authority to = latest version of the doc, and will avoid indexing more than 25.000 = URLs. >>> - Added canonical url tags and GA tracking code to all .html = files for 1.9.0.=20 >>> - Updated some anchor tags on the homepage which were linking to = the features using only the icons and not the feature's title text. >>> - Updated sitemap.xml with 1.9.0 URLs. >>> - Updated the links on navigation so they point to latest = version of API documentation. >>>=20 >>>=20 >>> I will appreciate if any of the committers could merge this on = website=E2=80=99s repo. >>>=20 >>> Please let me know if you have any question. >>>=20 >>> Thanks in advance. >>>=20 >>> Best, >>> Mauricio Stekl >>>=20 >>>=20 >>> >=20 --Apple-Mail=_83CCCC79-1F0E-49DB-89AC-71983B371386--