From dev-return-17841-archive-asf-public=cust-asf.ponee.io@manifoldcf.apache.org Mon Mar 5 09:42:06 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id C8F5F180676 for ; Mon, 5 Mar 2018 09:42:05 +0100 (CET) Received: (qmail 89091 invoked by uid 500); 5 Mar 2018 08:42:04 -0000 Mailing-List: contact dev-help@manifoldcf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@manifoldcf.apache.org Delivered-To: mailing list dev@manifoldcf.apache.org Received: (qmail 89048 invoked by uid 99); 5 Mar 2018 08:42:04 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Mar 2018 08:42:04 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id EFDDCC5DB9 for ; Mon, 5 Mar 2018 08:42:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -110.311 X-Spam-Level: X-Spam-Status: No, score=-110.311 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id 3TKYrXrVqlXR for ; Mon, 5 Mar 2018 08:42:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 1F7375F3B5 for ; Mon, 5 Mar 2018 08:42:02 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id DAB0EE0332 for ; Mon, 5 Mar 2018 08:42:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 3FE552126C for ; Mon, 5 Mar 2018 08:42:00 +0000 (UTC) Date: Mon, 5 Mar 2018 08:42:00 +0000 (UTC) From: "Piergiorgio Lucidi (JIRA)" To: dev@manifoldcf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CONNECTORS-1495) Brand new website MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CONNECTORS-1495?page=3Dcom.atla= ssian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId= =3D16385797#comment-16385797 ]=20 Piergiorgio Lucidi commented on CONNECTORS-1495: ------------------------------------------------ Hi [~sonosolobit], discussing with=C2=A0[~kwright@metacarta.com]=C2=A0we would like to approac= h to Jekyll in a light way, this means that before looking at the documenta= tion, we could try to use Jekyll only for the website and then approach to = the complex part. We could learn Jekyll approaching with the website (Step 1) and then we wil= l rearrange the documentation (Step 2). In order to simplify the process we could use an existent template in the A= pache Community that is actually using Jekyll, probably CloudStack could be= a good start. Below my comments about your questions: # The site structure needs to be rethought in a way that better adapts to = the jekyll folder structure. In particular, we need to consider the multili= ngual nature of the actual site. We need to consider also that in jekyll we= can use the tag or category system to group the pages. +1 from me. =C2=A0 {quote}2. How can we use (if it=E2=80=99s possible) the markdown syntax wit= h the asiatic languages?=C2=A0 {quote} I don't know=C2=A0:P=C2=A0we have to look at it closely. =C2=A0 {quote}3. Jekyll hasn=E2=80=99t a native search engine. As suggested by Pie= rgiorgio, we could use solr (like now). In that case we might need to modif= y the jekyll theme to integrate the search form and the results page.=C2=A0 {quote} I'm pretty sure that we can find something that can allow us to index our c= ontent, for example something similar to the following: [https://github.com/andyfowler/jekyll-plugins/blob/master/solr.rb] =C2=A0 {quote}4. A manual conversion of the existing pages in markdown isn=E2=80= =99t too difficult or too long. The text structure is quite simple. The slo= west (and boring) part is related to the insertion of the inline images and= the rebuild of the tables. {quote} If we find the right syntax we can work together and divide the effort in a= n appropriate way, we are a community: you are not alone=C2=A0;) =C2=A0 {quote}5. We should consider splitting the longest documents in smaller pie= ces (for example the "end user documentation"). {quote} +1 but during Step 2. {quote}6. We need to select the jekyll plugins (syntax highlight, image man= ager,=C2=A0 tables, etc) to use for the site. The jekyll plugin list is her= e:=C2=A0[https://jekyllrb.com/docs/plugins/|https://jekyllrb.com/docs/plugi= ns/)] {quote} The first one is=C2=A0required to index the content against Solr: [https://github.com/andyfowler/jekyll-plugins/blob/master/solr.rb] I think that we only need to start and then during our work we will start t= o choose plugins dedicated to different capabilities. > Brand new website > ----------------- > > Key: CONNECTORS-1495 > URL: https://issues.apache.org/jira/browse/CONNECTORS-149= 5 > Project: ManifoldCF > Issue Type: New Feature > Components: Site > Affects Versions: ManifoldCF 2.9.1 > Reporter: Piergiorgio Lucidi > Assignee: Piergiorgio Lucidi > Priority: Major > Fix For: ManifoldCF next > > Original Estimate: 480h > Remaining Estimate: 480h > > The community decided to work on a brand new website: > [http://mail-archives.apache.org/mod_mbox/manifoldcf-dev/201712.mbox/%3CC= AHVHQx8odjgXMw%3DnhmSeDt0pYOUd0j%2BtkmMNtFnCJvHFcZwyEg%40mail.gmail.com%3E] > The proposed technology is Jekyll but we have also to decide the website = template to use. > [~kamaci] suggested the [Apache CloudStack|https://cloudstack.apache.org/= ] template. > [~molgun] proposed this approach: > # Find a modern new static site generator like Jekyll [1] > # Create a template > # Start to use it in a specific path like=C2=A0[https://manifoldcf.apach= e.org/*new*] > # Migrate our Forrest xml's to Markdown (we can automate this somehow) > # Start to serve our new site on root path > [1]=C2=A0[https://jekyllrb.com/docs/home/] > =C2=A0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)