aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Jencks <david.a.jen...@gmail.com>
Subject Re: The project website
Date Tue, 11 Aug 2020 16:43:12 GMT
I think we’re at a point where we can switch  to this Antora site, get all the publishing wrinkles worked out, and then add the newer content.

I guess one other thing we probably want is a .htaccess file to redirect from the old locations to the new site?

Shall I talk with Andrew about how to proceed with this?

Thanks
David Jencks

> On Aug 11, 2020, at 9:35 AM, David Jencks <david.a.jencks@gmail.com> wrote:
> 
> How’s this?  https://aries-preview.s3-us-west-2.amazonaws.com/documentation/index.html <https://aries-preview.s3-us-west-2.amazonaws.com/documentation/index.html>
> 
> David Jencks
> 
>> On Aug 10, 2020, at 2:36 PM, Raymond Auge <raymond.auge@liferay.com.INVALID <mailto:raymond.auge@liferay.com.INVALID>> wrote:
>> 
>> Ideally remove it.
>> 
>> Next option, just make it like 1 line?
>> 
>> - Ray
>> 
>> On Mon., Aug. 10, 2020, 4:45 p.m. David Jencks, <david.a.jencks@gmail.com <mailto:david.a.jencks@gmail.com>>
>> wrote:
>> 
>>> Of course.  What do you suggest?
>>> 
>>> David
>>> 
>>>> On Aug 10, 2020, at 1:06 PM, Raymond Auge <raymond.auge@liferay.com.INVALID <mailto:raymond.auge@liferay.com.INVALID>>
>>> wrote:
>>>> 
>>>> Can we reduce/simplify the footer a little bit with all the antora
>>> details?
>>>> 
>>>> - Ray
>>>> 
>>>> 
>>>> 
>>>> On Mon, Aug 10, 2020 at 3:58 PM David Jencks <david.a.jencks@gmail.com <mailto:david.a.jencks@gmail.com>
>>> <mailto:david.a.jencks@gmail.com <mailto:david.a.jencks@gmail.com>>>
>>>> wrote:
>>>> 
>>>>> WD_Y_T?  https://aries-preview.s3-us-west-2.amazonaws.com/index.html <https://aries-preview.s3-us-west-2.amazonaws.com/index.html>
>>>>> 
>>>>> Looks good to me, shall I commit it?
>>>>> 
>>>>> David
>>>>> 
>>>>> 
>>>>> 
>>>>>> On Aug 10, 2020, at 10:59 AM, Raymond Auge <raymond.auge@liferay.com <mailto:raymond.auge@liferay.com>
>>> .INVALID>
>>>>> wrote:
>>>>>> 
>>>>>> WDYT?
>>>>>> 
>>>>>> - Ray
>>>>>> 
>>>>>> On Mon, Aug 10, 2020 at 12:42 PM Raymond Auge <
>>> raymond.auge@liferay.com <mailto:raymond.auge@liferay.com>
>>>>> <mailto:raymond.auge@liferay.com <mailto:raymond.auge@liferay.com> <mailto:raymond.auge@liferay.com <mailto:raymond.auge@liferay.com>>>>
>>> wrote:
>>>>>> working on it...
>>>>>> 
>>>>>> On Mon, Aug 10, 2020 at 11:41 AM David Jencks <
>>> david.a.jencks@gmail.com <mailto:david.a.jencks@gmail.com> <mailto:david.a.jencks@gmail.com <mailto:david.a.jencks@gmail.com>>
>>>>> <mailto:david.a.jencks@gmail.com <mailto:david.a.jencks@gmail.com> <mailto:david.a.jencks@gmail.com <mailto:david.a.jencks@gmail.com>>>>
>>> wrote:
>>>>>> If you can fix or get fixed the logo that would be fantastic!
>>>>>> 
>>>>>> David Jencks
>>>>>> 
>>>>>>> On Aug 10, 2020, at 7:52 AM, Raymond Auge <raymond.auge@liferay.com <mailto:raymond.auge@liferay.com>
>>> <mailto:raymond.auge@liferay.com <mailto:raymond.auge@liferay.com>>
>>>>> <mailto:raymond.auge@liferay.com <mailto:raymond.auge@liferay.com> <mailto:raymond.auge@liferay.com <mailto:raymond.auge@liferay.com>>>.INVALID>
>>> wrote:
>>>>>>> 
>>>>>>> Can we at least fix the logo? It's really bad :D
>>>>>>> 
>>>>>>> Anyone opposed to removing the text from the logo so we can just use
>>>>> markup?
>>>>>>> 
>>>>>>> - Ray
>>>>>>> 
>>>>>>> On Mon, Aug 10, 2020 at 10:47 AM David Jencks <
>>>>> david.a.jencks@gmail.com <mailto:david.a.jencks@gmail.com> <mailto:david.a.jencks@gmail.com <mailto:david.a.jencks@gmail.com>> <mailto:
>>> david.a.jencks@gmail.com <mailto:david.a.jencks@gmail.com> <mailto:david.a.jencks@gmail.com <mailto:david.a.jencks@gmail.com>>>>
>>>>>>> wrote:
>>>>>>> 
>>>>>>>> You can clone what I have now, but I wonder if we should get the
>>>>>>>> publishing steps working and get the repos under aries first, on the
>>>>> theory
>>>>>>>> that the preview is as good as the current site :-)
>>>>>>>> 
>>>>>>>> David Jencks
>>>>>>>> 
>>>>>>>>> On Aug 10, 2020, at 7:18 AM, Raymond Auge <raymond.auge@liferay.com <mailto:raymond.auge@liferay.com>
>>> <mailto:raymond.auge@liferay.com <mailto:raymond.auge@liferay.com>>
>>>>> <mailto:raymond.auge@liferay.com <mailto:raymond.auge@liferay.com> <mailto:raymond.auge@liferay.com <mailto:raymond.auge@liferay.com>
>>>>> .INVALID>
>>>>>>>> wrote:
>>>>>>>>> 
>>>>>>>>> @djenks I took a quick look at the preview site and it looks fine to
>>>>> me.
>>>>>>>>> The logo is clearly in terrible shape ;) but we can fix that I
>>>>> think. I
>>>>>>>>> happen to know a graphic artist who might be able to fix it and turn
>>>>> it
>>>>>>>>> into a higher quality version (ideally svg, if we could find the
>>>>> source
>>>>>>>> of
>>>>>>>>> the image that would be the best route.)
>>>>>>>>> 
>>>>>>>>> Now, as far as I can tell, a lot of the site content is super
>>>>> outdated
>>>>>>>> and
>>>>>>>>> I don't believe anyone has maintained `Application` for a very long
>>>>> time.
>>>>>>>>> Also, there is no central build anymore so almost all the "Building
>>>>>>>> Aries"
>>>>>>>>> is wrong since most projects are standalone builds. I would remove
>>>>> almost
>>>>>>>>> all of that stuff.
>>>>>>>>> 
>>>>>>>>> Once you have a repo with docs I can clone maybe I can take a crack
>>>>> at
>>>>>>>>> removing some of the cruft.
>>>>>>>>> 
>>>>>>>>> - Ray
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> On Mon, Aug 10, 2020 at 10:11 AM Raymond Auge <
>>>>> raymond.auge@liferay.com <mailto:raymond.auge@liferay.com> <mailto:raymond.auge@liferay.com <mailto:raymond.auge@liferay.com>> <mailto:
>>> raymond.auge@liferay.com <mailto:raymond.auge@liferay.com> <mailto:raymond.auge@liferay.com <mailto:raymond.auge@liferay.com>>>>
>>>>>>>>> wrote:
>>>>>>>>> 
>>>>>>>>>> Hey so I don't want to interrupt since it seems like you guys are
>>>>>>>> running
>>>>>>>>>> with this and I don't want to start a parallel stream.
>>>>>>>>>> 
>>>>>>>>>> One key point I want to make sure we all consider is that there
>>>>> _are_ at
>>>>>>>>>> slew of external projects (cdi, component-dsl, containers,
>>>>>>>>>> jaxrs-whiteboard, journaled-events, jpa, rsa, tx-control) that need
>>>>> to
>>>>>>>>>> somehow be integrated into the process with the caveat that their
>>>>> own
>>>>>>>> site
>>>>>>>>>> content should really be in their own repository alongside the
>>>>> source
>>>>>>>> code,
>>>>>>>>>> again for simplicity.
>>>>>>>>>> 
>>>>>>>>>> I thought Antora could do that (since it had a git client build
>>>>> it), but
>>>>>>>>>> now I'm no longer sure about that?
>>>>>>>>>> 
>>>>>>>>>> - Ray
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> On Sun, Aug 9, 2020 at 11:48 AM Romain Manni-Bucau <
>>>>>>>> rmannibucau@gmail.com <mailto:rmannibucau@gmail.com> <mailto:rmannibucau@gmail.com <mailto:rmannibucau@gmail.com>> <mailto:
>>> rmannibucau@gmail.com <mailto:rmannibucau@gmail.com> <mailto:rmannibucau@gmail.com <mailto:rmannibucau@gmail.com>>>>
>>>>>>>>>> wrote:
>>>>>>>>>> 
>>>>>>>>>>> Le dim. 9 août 2020 à 16:43, David Jencks <
>>>>> david.a.jencks@gmail.com <mailto:david.a.jencks@gmail.com> <mailto:david.a.jencks@gmail.com <mailto:david.a.jencks@gmail.com>> <mailto:
>>> david.a.jencks@gmail.com <mailto:david.a.jencks@gmail.com> <mailto:david.a.jencks@gmail.com <mailto:david.a.jencks@gmail.com>>>> a
>>>>>>>>>>> écrit :
>>>>>>>>>>> 
>>>>>>>>>>>> Well, your talend example
>>>>>>>>>>>> - isn’t self contained
>>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>> As mentionned, just used it as a proof we dont need a front build.
>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>> - doesn’t have the css and js processing/compression/checking that
>>>>> a
>>>>>>>> built
>>>>>>>>>>>> Antora UI has
>>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>> Only for customizations which does not impact perfs - or is likely
>>>>>>>> faster
>>>>>>>>>>> than a custom fulll build like antora thanks cdn.
>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>>> which would get a -1 from me.
>>>>>>>>>>>> 
>>>>>>>>>>>> It also has the script references in head-meta.hbs rather than
>>>>>>>>>>>> head-scripts.hbs, I have to wonder why.
>>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>> To have script per page and not global without a complex if logic,
>>>>> not
>>>>>>>>>>> needed for aries.
>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>>> I have no problem with a bootstrap based UI if the above problems
>>>>> are
>>>>>>>>>>>> fixed, but constructing one is beyond my current abilities or
>>>>>>>> interest.
>>>>>>>>>>>> Since generally no one is interested in websites let alone their
>>>>> UI I
>>>>>>>>>>> think
>>>>>>>>>>>> sticking with the simplest possible modification of the default
>>> UI
>>>>>>>> makes
>>>>>>>>>>>> sense.
>>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>> I wouldnt use antora like ui, it is not that common for aries or
>>>>> asf
>>>>>>>> users
>>>>>>>>>>> and requires a lot of tuning to make it doc friendly - talend
>>>>> flavor
>>>>>>>> was
>>>>>>>>>>> done with a doc team and layout was not (upfront) obvious for me.
>>>>>>>>>>> Guess we cna inherit the nav mecanism.
>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>>> David Jencks
>>>>>>>>>>>> 
>>>>>>>>>>>>> On Aug 9, 2020, at 12:27 AM, Romain Manni-Bucau <
>>>>>>>>>>> rmannibucau@gmail.com <mailto:rmannibucau@gmail.com> <mailto:rmannibucau@gmail.com <mailto:rmannibucau@gmail.com>> <mailto:
>>> rmannibucau@gmail.com <mailto:rmannibucau@gmail.com> <mailto:rmannibucau@gmail.com <mailto:rmannibucau@gmail.com>>>>
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>> 
>>>>>>>>>>>>> Le sam. 8 août 2020 à 20:25, David Jencks <
>>>>> david.a.jencks@gmail.com <mailto:david.a.jencks@gmail.com> <mailto:david.a.jencks@gmail.com <mailto:david.a.jencks@gmail.com>> <mailto:
>>> david.a.jencks@gmail.com <mailto:david.a.jencks@gmail.com> <mailto:david.a.jencks@gmail.com <mailto:david.a.jencks@gmail.com>>>
>>>>>>>>>>>> <mailto:david.a.jencks@gmail.com <mailto:david.a.jencks@gmail.com> <mailto:
>>> david.a.jencks@gmail.com <mailto:david.a.jencks@gmail.com>> <mailto:david.a.jencks@gmail.com <mailto:david.a.jencks@gmail.com> <mailto:
>>> david.a.jencks@gmail.com <mailto:david.a.jencks@gmail.com>>>>>
>>>>> a
>>>>>>>>>>>>> écrit :
>>>>>>>>>>>>> 
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> On Aug 8, 2020, at 10:31 AM, Romain Manni-Bucau <
>>>>>>>>>>> rmannibucau@gmail.com <mailto:rmannibucau@gmail.com> <mailto:rmannibucau@gmail.com <mailto:rmannibucau@gmail.com>> <mailto:
>>> rmannibucau@gmail.com <mailto:rmannibucau@gmail.com> <mailto:rmannibucau@gmail.com <mailto:rmannibucau@gmail.com>>>
>>>>>>>>>>>>> 
>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> Le sam. 8 août 2020 à 08:46, David Jencks <
>>>>>>>> david.a.jencks@gmail.com <mailto:david.a.jencks@gmail.com> <mailto:david.a.jencks@gmail.com <mailto:david.a.jencks@gmail.com>> <mailto:
>>> david.a.jencks@gmail.com <mailto:david.a.jencks@gmail.com> <mailto:david.a.jencks@gmail.com <mailto:david.a.jencks@gmail.com>>>>
>>>>>>>>>>> a
>>>>>>>>>>>>>>> écrit :
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> Supplemental UI is a horrible workaround for the insufficient
>>>>> UI
>>>>>>>>>>>>>> builder.
>>>>>>>>>>>>>>>> I’ve somewhat improved the UI builder by making it a separate
>>>>>>>>>>> project,
>>>>>>>>>>>>>> and
>>>>>>>>>>>>>>>> making it able to aggregate lots of UI bits:
>>>>> antora-ui-builder <
>>>>>>>>>>>>>>>> https://gitlab.com/djencks/antora-ui-builder <https://gitlab.com/djencks/antora-ui-builder> <
>>> https://gitlab.com/djencks/antora-ui-builder <https://gitlab.com/djencks/antora-ui-builder>> <
>>>>> https://gitlab.com/djencks/antora-ui-builder <https://gitlab.com/djencks/antora-ui-builder> <
>>> https://gitlab.com/djencks/antora-ui-builder <https://gitlab.com/djencks/antora-ui-builder>>>>
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> If we go with it, can we fork it at asf?
>>>>>>>>>>>>>>> Not depending on one - even very good ;) - man project is
>>>>> always
>>>>>>>>>>> saner,
>>>>>>>>>>>>>> it
>>>>>>>>>>>>>>> already bite us by the past.
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> I hesitated to suggest using it for that reason.  We can’t fork
>>>>> it
>>>>>>>> at
>>>>>>>>>>>>>> Apache (mpl2.0) but anyone can fork it at GitLab.  After
>>> working
>>>>>>>> with
>>>>>>>>>>>>>> node.js stuff for a few months I have the impression that the
>>>>> vast
>>>>>>>>>>>> majority
>>>>>>>>>>>>>> of node projects are one-man efforts.  The idea of a builder is
>>>>> an
>>>>>>>>>>> open
>>>>>>>>>>>>>> issue in the default UI, but I got tired of waiting and wrote
>>>>> one.
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> The other reason I think my builder to start with is reasonable
>>>>> is
>>>>>>>>>>> that
>>>>>>>>>>>>>> it’s very easy to turn a project using it into a fork of the
>>>>> default
>>>>>>>>>>> UI.
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> Now we can just move on bootstrap and use cdn, supplemental ui
>>>>> is
>>>>>>>>>>> then
>>>>>>>>>>>>>>> mainly just about hbs/templates and does not need much front
>>>>> build
>>>>>>>>>>> (as
>>>>>>>>>>>>>> most
>>>>>>>>>>>>>>> asf sites).
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> I don’t understand what you mean, could you clarify?
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> I think we’ll want to change the colors (at least I do) which
>>>>>>>>>>> involves
>>>>>>>>>>>> css
>>>>>>>>>>>>>> which can’t be done with supplemental UI.
>>>>>>>>>>>>>> 
>>>>>>>>>>>>> 
>>>>>>>>>>>>> It can since you fully control the templates - this is what is
>>>>> done
>>>>>>>> in
>>>>>>>>>>>> the
>>>>>>>>>>>>> link i shared on a bootstrap base.
>>>>>>>>>>>>> Just tune the hbs template.
>>>>>>>>>>>>> 
>>>>>>>>>>>>> 
>>>>>>>>>>>>>> David Jencks
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> I’m planning to set up a UI project using this for Aries
>>>>> tomorrow
>>>>>>>>>>> and
>>>>>>>>>>>>>>>> include the logo, Apache feather, and perhaps lunr search…
>>>>> that’s
>>>>>>>>>>> why
>>>>>>>>>>>> I
>>>>>>>>>>>>>> was
>>>>>>>>>>>>>>>> asking if Aries has a favorite color :-)  Using my ui-builder
>>>>>>>>>>> project
>>>>>>>>>>>>>> may
>>>>>>>>>>>>>>>> tie us to something less likely to be maintained than Antora,
>>>>> but
>>>>>>>>>>> it
>>>>>>>>>>>>>>>> certainly separates the alterations from the default UI
>>>>> clearly,
>>>>>>>>>>> which
>>>>>>>>>>>>>>>> forking does not.  Lets get something that looks good and
>>>>> discuss
>>>>>>>>>>> it
>>>>>>>>>>>>>>>> further.
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> I agree checking all the links is a good idea :-).  Camel
>>>>> uses the
>>>>>>>>>>>> xref
>>>>>>>>>>>>>>>> checker and a link checker, I think I’ve seen a different
>>> link
>>>>>>>>>>> checker
>>>>>>>>>>>>>>>> strongly recommended, I’ll try to find it.
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> Are you suggesting that the “full content” should be one
>>> “old”
>>>>>>>>>>> version
>>>>>>>>>>>>>> and
>>>>>>>>>>>>>>>> that the “currently relevant content” should be a separate
>>>>>>>> “latest”
>>>>>>>>>>>>>>>> version?  Otherwise I’m not sure what you are suggesting.
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> Thanks!
>>>>>>>>>>>>>>>> David Jencks
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> On Aug 7, 2020, at 11:17 PM, Romain Manni-Bucau <
>>>>>>>>>>>> rmannibucau@gmail.com <mailto:rmannibucau@gmail.com> <mailto:rmannibucau@gmail.com <mailto:rmannibucau@gmail.com>> <mailto:
>>> rmannibucau@gmail.com <mailto:rmannibucau@gmail.com> <mailto:rmannibucau@gmail.com <mailto:rmannibucau@gmail.com>>>
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> About the theme, Dan says default one is not for prod so we
>>>>>>>> should
>>>>>>>>>>>> fork
>>>>>>>>>>>>>>>> it
>>>>>>>>>>>>>>>>> and just do an aries theme instead of inheriting from
>>> default
>>>>>>>> one.
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>> 
>>>>> 
>>> https://github.com/Talend/component-runtime/tree/master/documentation/src/main/antora/supplemental-ui <https://github.com/Talend/component-runtime/tree/master/documentation/src/main/antora/supplemental-ui>
>>> <
>>> https://github.com/Talend/component-runtime/tree/master/documentation/src/main/antora/supplemental-ui <https://github.com/Talend/component-runtime/tree/master/documentation/src/main/antora/supplemental-ui>
>>>> 
>>>>> <
>>>>> 
>>> https://github.com/Talend/component-runtime/tree/master/documentation/src/main/antora/supplemental-ui <https://github.com/Talend/component-runtime/tree/master/documentation/src/main/antora/supplemental-ui>
>>> <
>>> https://github.com/Talend/component-runtime/tree/master/documentation/src/main/antora/supplemental-ui <https://github.com/Talend/component-runtime/tree/master/documentation/src/main/antora/supplemental-ui>
>>>> 
>>>>>> 
>>>>>>>>>>>>>>>>> can help to bootstrap it (needs to import a few tpl from
>>>>> default
>>>>>>>>>>>> antora
>>>>>>>>>>>>>>>>> theme). It is based on bootstrap but any stack works.
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> About the content: I'd ensure current links - except
>>>>> index.hml -
>>>>>>>>>>> are
>>>>>>>>>>>>>> not
>>>>>>>>>>>>>>>>> broken and maybe register new clean up content on antora
>>>>> version?
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> Know tomee did it, got a clean site, then imported back old
>>>>>>>>>>> content
>>>>>>>>>>>>>> which
>>>>>>>>>>>>>>>>> made the site messy so not fully sure we should do it but
>>> the
>>>>>>>>>>> clean
>>>>>>>>>>>>>>>> version
>>>>>>>>>>>>>>>>> got some nice feedback  from users.
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> Le sam. 8 août 2020 à 02:48, David Jencks <
>>>>>>>>>>> david.a.jencks@gmail.com <mailto:david.a.jencks@gmail.com> <mailto:david.a.jencks@gmail.com <mailto:david.a.jencks@gmail.com>>
>>> <mailto:david.a.jencks@gmail.com <mailto:david.a.jencks@gmail.com> <mailto:david.a.jencks@gmail.com <mailto:david.a.jencks@gmail.com>>>>
>>>>>>>>>>>> a
>>>>>>>>>>>>>>>>> écrit :
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> I’ve done about 90% of (5).  What remains is mostly escaped
>>>>> html
>>>>>>>>>>>> links
>>>>>>>>>>>>>>>> in
>>>>>>>>>>>>>>>>>> tables.  I suspect this can be condensed using attributes.
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> Please take a look at the preview
>>>>>>>>>>>>>>>>>> 
>>> https://aries-preview.s3-us-west-2.amazonaws.com/index.html <https://aries-preview.s3-us-west-2.amazonaws.com/index.html> <
>>> https://aries-preview.s3-us-west-2.amazonaws.com/index.html <https://aries-preview.s3-us-west-2.amazonaws.com/index.html>>
>>>>> <https://aries-preview.s3-us-west-2.amazonaws.com/index.html <https://aries-preview.s3-us-west-2.amazonaws.com/index.html> <
>>> https://aries-preview.s3-us-west-2.amazonaws.com/index.html <https://aries-preview.s3-us-west-2.amazonaws.com/index.html>>> <
>>>>>>>>>>>>>>>>>> 
>>> https://aries-preview.s3-us-west-2.amazonaws.com/index.html <https://aries-preview.s3-us-west-2.amazonaws.com/index.html> <
>>> https://aries-preview.s3-us-west-2.amazonaws.com/index.html <https://aries-preview.s3-us-west-2.amazonaws.com/index.html>>
>>>>> <https://aries-preview.s3-us-west-2.amazonaws.com/index.html <https://aries-preview.s3-us-west-2.amazonaws.com/index.html> <
>>> https://aries-preview.s3-us-west-2.amazonaws.com/index.html <https://aries-preview.s3-us-west-2.amazonaws.com/index.html>>>>.
>>>>>>>> A
>>>>>>>>>>>> lot
>>>>>>>>>>>>>> of
>>>>>>>>>>>>>>>>>> the content looks to me as if it may be totally obsolete
>>> and
>>>>>>>>>>>>>> misleading
>>>>>>>>>>>>>>>> and
>>>>>>>>>>>>>>>>>> the site might be improved by removing it.  Fixing the html
>>>>>>>> links
>>>>>>>>>>>> will
>>>>>>>>>>>>>>>> be a
>>>>>>>>>>>>>>>>>> noticeable amount of work and if we’re going to drop the
>>>>> pages
>>>>>>>>>>> I’d
>>>>>>>>>>>>>> like
>>>>>>>>>>>>>>>> to
>>>>>>>>>>>>>>>>>> avoid doing it.
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> Next step is to refine the left side nav.
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> David Jencks
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>> On Aug 7, 2020, at 3:37 PM, David Jencks <
>>>>>>>>>>> david.a.jencks@gmail.com <mailto:david.a.jencks@gmail.com> <mailto:david.a.jencks@gmail.com <mailto:david.a.jencks@gmail.com>>
>>> <mailto:david.a.jencks@gmail.com <mailto:david.a.jencks@gmail.com> <mailto:david.a.jencks@gmail.com <mailto:david.a.jencks@gmail.com>>>
>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>> That’s my idea :-)
>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>> The current site doesn’t seem very themed.  Does Aries
>>>>> have a
>>>>>>>>>>>>>> favorite
>>>>>>>>>>>>>>>>>> color?  I find a color distinction between header and
>>>>> footer and
>>>>>>>>>>> the
>>>>>>>>>>>>>>>> body a
>>>>>>>>>>>>>>>>>> nice framing of the content.
>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>> BTW I’m most of the way through (5).  I realize I
>>>>> committed the
>>>>>>>>>>>>>>>>>> “author-mode” local version of the playbook, I’ll fix that
>>>>> when
>>>>>>>> I
>>>>>>>>>>>>>> commit
>>>>>>>>>>>>>>>>>> the asciidoc fixes.
>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>> Also BTW, svn2git creates a new git repo, which is where
>>>>> we are
>>>>>>>>>>>> now.
>>>>>>>>>>>>>>>>>> I’ve never done it but think that by adding it as a remote
>>>>> to
>>>>>>>> the
>>>>>>>>>>>> main
>>>>>>>>>>>>>>>> git
>>>>>>>>>>>>>>>>>> repo I’ll be able to merge in the site as a merge from a
>>>>> branch.
>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>> I suppose a first draft of the nav file could mirror the
>>>>>>>>>>> directly
>>>>>>>>>>>>>>>>>> structure…. right now it’s just an alphabetical list of all
>>>>>>>>>>> pages.
>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>> David Jencks
>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>> On Aug 7, 2020, at 12:21 PM, Romain Manni-Bucau <
>>>>>>>>>>>>>>>> rmannibucau@gmail.com <mailto:rmannibucau@gmail.com> <mailto:rmannibucau@gmail.com <mailto:rmannibucau@gmail.com>>
>>> <mailto:rmannibucau@gmail.com <mailto:rmannibucau@gmail.com> <mailto:rmannibucau@gmail.com <mailto:rmannibucau@gmail.com>>>>
>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>> So is the plan to add all sources (git repos) and do the
>>>>>>>>>>> theme? (I
>>>>>>>>>>>>>>>>>> would be
>>>>>>>>>>>>>>>>>>>> for it)
>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>> Le ven. 7 août 2020 à 20:25, David Jencks <
>>>>>>>>>>>> david.a.jencks@gmail.com <mailto:david.a.jencks@gmail.com> <mailto:david.a.jencks@gmail.com <mailto:david.a.jencks@gmail.com>>
>>> <mailto:david.a.jencks@gmail.com <mailto:david.a.jencks@gmail.com> <mailto:david.a.jencks@gmail.com <mailto:david.a.jencks@gmail.com>>>
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> a
>>>>>>>>>>>>>>>>>>>> écrit :
>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>> I’ve done 1-3, and 4 enough to build a site with all
>>> adoc
>>>>>>>>>>> pages
>>>>>>>>>>>>>>>> listed
>>>>>>>>>>>>>>>>>> in
>>>>>>>>>>>>>>>>>>>>> the nav.
>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>> Site is previewed at
>>>>>>>>>>>>>>>>>>>>> 
>>>>> https://aries-preview.s3-us-west-2.amazonaws.com/index.html <https://aries-preview.s3-us-west-2.amazonaws.com/index.html> <
>>> https://aries-preview.s3-us-west-2.amazonaws.com/index.html <https://aries-preview.s3-us-west-2.amazonaws.com/index.html>> <
>>>>> https://aries-preview.s3-us-west-2.amazonaws.com/index.html <https://aries-preview.s3-us-west-2.amazonaws.com/index.html> <
>>> https://aries-preview.s3-us-west-2.amazonaws.com/index.html <https://aries-preview.s3-us-west-2.amazonaws.com/index.html>>>
>>>>>>>> <
>>>>>>>>>>>>>>>>>>>>> 
>>>>> https://aries-preview.s3-us-west-2.amazonaws.com/index.html <https://aries-preview.s3-us-west-2.amazonaws.com/index.html> <
>>> https://aries-preview.s3-us-west-2.amazonaws.com/index.html <https://aries-preview.s3-us-west-2.amazonaws.com/index.html>> <
>>>>> https://aries-preview.s3-us-west-2.amazonaws.com/index.html <https://aries-preview.s3-us-west-2.amazonaws.com/index.html> <
>>> https://aries-preview.s3-us-west-2.amazonaws.com/index.html <https://aries-preview.s3-us-west-2.amazonaws.com/index.html>>>
>>>>>>>>> .
>>>>>>>>>>>>>> Note
>>>>>>>>>>>>>>>>>> that
>>>>>>>>>>>>>>>>>>>>> this is not a web server, and some things that work on a
>>>>> web
>>>>>>>>>>>> server
>>>>>>>>>>>>>>>>>> give
>>>>>>>>>>>>>>>>>>>>> you an error. I don’t know of any with this particular
>>>>>>>>>>> preview,
>>>>>>>>>>>> but
>>>>>>>>>>>>>>>>>> don’t
>>>>>>>>>>>>>>>>>>>>> assume something will necessarily be broken if it
>>> doesn’t
>>>>>>>> work
>>>>>>>>>>>>>> here.
>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>> Git repos from which this is built:
>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>> content:  aries-antora-site <
>>>>>>>>>>>>>>>>>> https://github.com/djencks/aries-antora-site <https://github.com/djencks/aries-antora-site> <
>>> https://github.com/djencks/aries-antora-site <https://github.com/djencks/aries-antora-site>> <
>>>>> https://github.com/djencks/aries-antora-site <https://github.com/djencks/aries-antora-site> <
>>> https://github.com/djencks/aries-antora-site <https://github.com/djencks/aries-antora-site>>>>
>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>> Antora playbook:  aries-antora <
>>>>>>>>>>>>>>>>>> https://github.com/djencks/aries-antora <https://github.com/djencks/aries-antora> <
>>> https://github.com/djencks/aries-antora <https://github.com/djencks/aries-antora>> <
>>>>> https://github.com/djencks/aries-antora <https://github.com/djencks/aries-antora> <
>>> https://github.com/djencks/aries-antora <https://github.com/djencks/aries-antora>>>>
>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>> To build it yourself, install node and npm.
>>>>>>>>>>>>>>>>>>>>> Clone the aries-antora <
>>>>>>>>>>> https://github.com/djencks/aries-antora <https://github.com/djencks/aries-antora> <
>>> https://github.com/djencks/aries-antora <https://github.com/djencks/aries-antora>> <
>>>>> https://github.com/djencks/aries-antora <https://github.com/djencks/aries-antora> <
>>> https://github.com/djencks/aries-antora <https://github.com/djencks/aries-antora>>>>
>>>>>>>>>>>>>>>>>> playbook
>>>>>>>>>>>>>>>>>>>>> project.
>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>> Run npm run clean-build.  The site will be under build.
>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>> I left the mdtext files in place next to the adoc
>>>>>>>>>>> translations so
>>>>>>>>>>>>>> it
>>>>>>>>>>>>>>>>>> will
>>>>>>>>>>>>>>>>>>>>> be easy to check back when looking for errors.
>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>> David Jencks
>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>> On Aug 5, 2020, at 11:25 PM, David Jencks <
>>>>>>>>>>>>>> david.a.jencks@gmail.com <mailto:david.a.jencks@gmail.com> <mailto:david.a.jencks@gmail.com <mailto:david.a.jencks@gmail.com>>
>>> <mailto:david.a.jencks@gmail.com <mailto:david.a.jencks@gmail.com> <mailto:david.a.jencks@gmail.com <mailto:david.a.jencks@gmail.com>>>
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>> I looked at this briefly…
>>>>>>>>>>>>>>>>>>>>>> i think the following steps will lead us to a nice
>>>>> Antora
>>>>>>>>>>> site:
>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>> 1. convert the svn to a git repo
>>>>>>>>>>>>>>>>>>>>>> 2. translate the .markdown files to asciidoc in place
>>>>> with
>>>>>>>>>>>>>>>>>>>>> kramdown-asciidoc asciidoctor/kramdown-asciidoc: A
>>>>> kramdown
>>>>>>>>>>> ... -
>>>>>>>>>>>>>>>>>>>>> GitHubgithub.com <http://githubgithub.com/> <http://githubgithub.com/ <http://githubgithub.com/>> ›
>>> asciidoctor › kramdown-asciidoc <
>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>> 
>>>>> 
>>> https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=&ved=2ahUKEwi6mdCO9oXrAhWwJDQIHYAeCt0QFjAAegQIBRAB&url=https%3A%2F%2Fgithub.com%2Fasciidoctor%2Fkramdown-asciidoc&usg=AOvVaw2sOAmH3_x0kdG3iuFoZ7OX <https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=&ved=2ahUKEwi6mdCO9oXrAhWwJDQIHYAeCt0QFjAAegQIBRAB&url=https%3A%2F%2Fgithub.com%2Fasciidoctor%2Fkramdown-asciidoc&usg=AOvVaw2sOAmH3_x0kdG3iuFoZ7OX>
>>> <
>>> https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=&ved=2ahUKEwi6mdCO9oXrAhWwJDQIHYAeCt0QFjAAegQIBRAB&url=https%3A%2F%2Fgithub.com%2Fasciidoctor%2Fkramdown-asciidoc&usg=AOvVaw2sOAmH3_x0kdG3iuFoZ7OX <https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=&ved=2ahUKEwi6mdCO9oXrAhWwJDQIHYAeCt0QFjAAegQIBRAB&url=https%3A%2F%2Fgithub.com%2Fasciidoctor%2Fkramdown-asciidoc&usg=AOvVaw2sOAmH3_x0kdG3iuFoZ7OX>
>>>> 
>>>>> <
>>>>> 
>>> https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=&ved=2ahUKEwi6mdCO9oXrAhWwJDQIHYAeCt0QFjAAegQIBRAB&url=https%3A%2F%2Fgithub.com%2Fasciidoctor%2Fkramdown-asciidoc&usg=AOvVaw2sOAmH3_x0kdG3iuFoZ7OX <https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=&ved=2ahUKEwi6mdCO9oXrAhWwJDQIHYAeCt0QFjAAegQIBRAB&url=https%3A%2F%2Fgithub.com%2Fasciidoctor%2Fkramdown-asciidoc&usg=AOvVaw2sOAmH3_x0kdG3iuFoZ7OX>
>>> <
>>> https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=&ved=2ahUKEwi6mdCO9oXrAhWwJDQIHYAeCt0QFjAAegQIBRAB&url=https%3A%2F%2Fgithub.com%2Fasciidoctor%2Fkramdown-asciidoc&usg=AOvVaw2sOAmH3_x0kdG3iuFoZ7OX <https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=&ved=2ahUKEwi6mdCO9oXrAhWwJDQIHYAeCt0QFjAAegQIBRAB&url=https%3A%2F%2Fgithub.com%2Fasciidoctor%2Fkramdown-asciidoc&usg=AOvVaw2sOAmH3_x0kdG3iuFoZ7OX>
>>>> 
>>>>>> 
>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>> (there will be plenty of errors to fix….)
>>>>>>>>>>>>>>>>>>>>>> 3. Move the content to an Antora structure with some
>>>>> minimal
>>>>>>>>>>>>>> amount
>>>>>>>>>>>>>>>> of
>>>>>>>>>>>>>>>>>>>>> (re)organization.
>>>>>>>>>>>>>>>>>>>>>> 4. Set up Antora navigation, build, and UI
>>>>>>>>>>>>>>>>>>>>>> 5. Fix the asciidoc errors.
>>>>>>>>>>>>>>>>>>>>>> 6. Consider what further reorganization is appropriate,
>>>>> such
>>>>>>>>>>> as
>>>>>>>>>>>>>>>> moving
>>>>>>>>>>>>>>>>>>>>> the docs for (sub)projects to those subprojects.
>>>>>>>>>>>>>>>>>>>>>> 7. Figure out how to use the Apache publish-to-git
>>>>> system
>>>>>>>>>>>>>>>>>>>>>> 8. Refine the UI.
>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>> I think it will be simplest if I just do steps 1-4.
>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>> There seems to already be a git aries-site repo that
>>>>> looks
>>>>>>>>>>>>>>>> abandoned.
>>>>>>>>>>>>>>>>>>>>> Can I move the current content to a different branch and
>>>>> use
>>>>>>>>>>> that
>>>>>>>>>>>>>> for
>>>>>>>>>>>>>>>>>> (1)?
>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>> Comments? Objections?
>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>> David Jencks
>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>>> On Aug 5, 2020, at 11:44 AM, Raymond Auge <
>>>>>>>>>>>>>>>> raymond.auge@liferay.com <mailto:raymond.auge@liferay.com> <mailto:raymond.auge@liferay.com <mailto:raymond.auge@liferay.com>>
>>> <mailto:raymond.auge@liferay.com <mailto:raymond.auge@liferay.com> <mailto:raymond.auge@liferay.com <mailto:raymond.auge@liferay.com>>>
>>>>>>>>>>>>>>>>>> .INVALID
>>>>>>>>>>>>>>>>>>>>> <mailto:raymond.auge@liferay.com.INVALID <mailto:raymond.auge@liferay.com.INVALID> <mailto:
>>> raymond.auge@liferay.com.INVALID <mailto:raymond.auge@liferay.com.INVALID>> <mailto:
>>>>> raymond.auge@liferay.com.INVALID <mailto:raymond.auge@liferay.com.INVALID> <mailto:
>>> raymond.auge@liferay.com.INVALID <mailto:raymond.auge@liferay.com.INVALID>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>>> https://svn.apache.org/repos/asf/aries/site/trunk/ <https://svn.apache.org/repos/asf/aries/site/trunk/> <
>>> https://svn.apache.org/repos/asf/aries/site/trunk/ <https://svn.apache.org/repos/asf/aries/site/trunk/>> <
>>>>> https://svn.apache.org/repos/asf/aries/site/trunk/ <https://svn.apache.org/repos/asf/aries/site/trunk/> <
>>> https://svn.apache.org/repos/asf/aries/site/trunk/ <https://svn.apache.org/repos/asf/aries/site/trunk/>>> <
>>>>>>>>>>>>>>>>>>>>> https://svn.apache.org/repos/asf/aries/site/trunk/ <https://svn.apache.org/repos/asf/aries/site/trunk/> <
>>> https://svn.apache.org/repos/asf/aries/site/trunk/ <https://svn.apache.org/repos/asf/aries/site/trunk/>> <
>>>>> https://svn.apache.org/repos/asf/aries/site/trunk/ <https://svn.apache.org/repos/asf/aries/site/trunk/> <
>>> https://svn.apache.org/repos/asf/aries/site/trunk/ <https://svn.apache.org/repos/asf/aries/site/trunk/>>>>
>>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>>> - Ray
>>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>>> On Wed, Aug 5, 2020 at 2:36 PM David Jencks <
>>>>>>>>>>>>>>>>>> david.a.jencks@gmail.com <mailto:david.a.jencks@gmail.com> <mailto:david.a.jencks@gmail.com <mailto:david.a.jencks@gmail.com>>
>>> <mailto:david.a.jencks@gmail.com <mailto:david.a.jencks@gmail.com> <mailto:david.a.jencks@gmail.com <mailto:david.a.jencks@gmail.com>>>>
>>>>>>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>>>> I looked around a little bit and couldn’t find the
>>>>> source
>>>>>>>>>>> for
>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>>>>> current
>>>>>>>>>>>>>>>>>>>>>>>> website.  Is it hidden somewhere in Apache CMS svn?
>>>>> Does
>>>>>>>>>>>> anyone
>>>>>>>>>>>>>>>>>> know
>>>>>>>>>>>>>>>>>>>>> where?
>>>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>>>> thanks
>>>>>>>>>>>>>>>>>>>>>>>> david jencks
>>>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>>>>> On Aug 4, 2020, at 9:51 PM, Romain Manni-Bucau <
>>>>>>>>>>>>>>>>>> rmannibucau@gmail.com <mailto:rmannibucau@gmail.com> <mailto:rmannibucau@gmail.com <mailto:rmannibucau@gmail.com>>
>>> <mailto:rmannibucau@gmail.com <mailto:rmannibucau@gmail.com> <mailto:rmannibucau@gmail.com <mailto:rmannibucau@gmail.com>>>
>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>>>>> Buildbot uses bash so just ensure node is there - a
>>>>> bit
>>>>>>>>>>> like
>>>>>>>>>>>>>>>> travis
>>>>>>>>>>>>>>>>>>>>> does
>>>>>>>>>>>>>>>>>>>>>>>> -
>>>>>>>>>>>>>>>>>>>>>>>>> and if not download it and that's it.
>>>>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>>>>> Alternatively frontend plugin works well as
>>>>> mzntionned by
>>>>>>>>>>>>>> David:
>>>>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>> 
>>>>> 
>>> https://github.com/Talend/component-runtime/blob/master/documentation/pom.xml#L567 <https://github.com/Talend/component-runtime/blob/master/documentation/pom.xml#L567>
>>> <
>>> https://github.com/Talend/component-runtime/blob/master/documentation/pom.xml#L567 <https://github.com/Talend/component-runtime/blob/master/documentation/pom.xml#L567>
>>>> 
>>>>> <
>>>>> 
>>> https://github.com/Talend/component-runtime/blob/master/documentation/pom.xml#L567 <https://github.com/Talend/component-runtime/blob/master/documentation/pom.xml#L567>
>>> <
>>> https://github.com/Talend/component-runtime/blob/master/documentation/pom.xml#L567 <https://github.com/Talend/component-runtime/blob/master/documentation/pom.xml#L567>
>>>> 
>>>>>> 
>>>>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>>>>> Le mar. 4 août 2020 à 21:27, David Jencks <
>>>>>>>>>>>>>>>>>> david.a.jencks@gmail.com <mailto:david.a.jencks@gmail.com> <mailto:david.a.jencks@gmail.com <mailto:david.a.jencks@gmail.com>>
>>> <mailto:david.a.jencks@gmail.com <mailto:david.a.jencks@gmail.com> <mailto:david.a.jencks@gmail.com <mailto:david.a.jencks@gmail.com>>>>
>>>>>>>>>>>>>>>>>>>>> a
>>>>>>>>>>>>>>>>>>>>>>>>> écrit :
>>>>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>>>>>> In typical apache fashion, there doesn’t appear to
>>>>> be
>>>>>>>> any
>>>>>>>>>>>>>> actual
>>>>>>>>>>>>>>>>>>>>>>>>>> information about how to use buildbot or what it
>>> can
>>>>>>>> do.
>>>>>>>>>>>>>>>> However,
>>>>>>>>>>>>>>>>>>>>>>>> buildbot
>>>>>>>>>>>>>>>>>>>>>>>>>> claims to be a general purpose tool.  It’s possible
>>>>> to
>>>>>>>>>>> run
>>>>>>>>>>>>>>>> Antora
>>>>>>>>>>>>>>>>>>>>> from
>>>>>>>>>>>>>>>>>>>>>>>>>> maven, so if we can’t figure out any more direct
>>>>>>>>>>> approach we
>>>>>>>>>>>>>> can
>>>>>>>>>>>>>>>>>> do
>>>>>>>>>>>>>>>>>>>>>>>> that.
>>>>>>>>>>>>>>>>>>>>>>>>>> Building on GitHub using GitHub actions might be
>>>>> another
>>>>>>>>>>>>>> option:
>>>>>>>>>>>>>>>>>>>>> that’s
>>>>>>>>>>>>>>>>>>>>>>>>>> definitely possible.
>>>>>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>>>>>> David Jencks
>>>>>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>>>>>>> On Aug 4, 2020, at 12:00 PM, Raymond Auge <
>>>>>>>>>>>>>>>>>> raymond.auge@liferay.com <mailto:raymond.auge@liferay.com> <mailto:raymond.auge@liferay.com <mailto:raymond.auge@liferay.com>>
>>> <mailto:raymond.auge@liferay.com <mailto:raymond.auge@liferay.com> <mailto:raymond.auge@liferay.com <mailto:raymond.auge@liferay.com>>>
>>>>>>>>>>>>>>>>>>>>>>>> .INVALID>
>>>>>>>>>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>>>>>>> It looks like antora requires node.js to build?
>>> Can
>>>>>>>>>>> such a
>>>>>>>>>>>>>>>> thing
>>>>>>>>>>>>>>>>>>>>> run on
>>>>>>>>>>>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>>>>>>>>>>> ASF buildbot jobs?
>>>>>>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>>>>>>> - Ray
>>>>>>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>>>>>>> On Tue, Aug 4, 2020 at 12:46 PM Romain Manni-Bucau
>>>>> <
>>>>>>>>>>>>>>>>>>>>>>>>>> rmannibucau@gmail.com <mailto:rmannibucau@gmail.com> <mailto:
>>> rmannibucau@gmail.com <mailto:rmannibucau@gmail.com>> <mailto:rmannibucau@gmail.com <mailto:rmannibucau@gmail.com> <mailto:
>>> rmannibucau@gmail.com <mailto:rmannibucau@gmail.com>>
>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>>>>>>>> +1, also enables to trivially generate doc
>>>>>>>>>>> parts/partials
>>>>>>>>>>>>>>>> which
>>>>>>>>>>>>>>>>>> is
>>>>>>>>>>>>>>>>>>>>>>>> super
>>>>>>>>>>>>>>>>>>>>>>>>>>>> important for all the configuration IMHO.
>>>>>>>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>>>>>>>> Romain Manni-Bucau
>>>>>>>>>>>>>>>>>>>>>>>>>>>> @rmannibucau <https://twitter.com/rmannibucau <https://twitter.com/rmannibucau> <
>>> https://twitter.com/rmannibucau <https://twitter.com/rmannibucau>> <
>>>>> https://twitter.com/rmannibucau <https://twitter.com/rmannibucau> <https://twitter.com/rmannibucau <https://twitter.com/rmannibucau>>>> |
>>>>>>>> Blog
>>>>>>>>>>>>>>>>>>>>>>>>>>>> <https://rmannibucau.metawerx.net/ <https://rmannibucau.metawerx.net/> <
>>> https://rmannibucau.metawerx.net/ <https://rmannibucau.metawerx.net/>> <
>>>>> https://rmannibucau.metawerx.net/ <https://rmannibucau.metawerx.net/> <https://rmannibucau.metawerx.net/ <https://rmannibucau.metawerx.net/>>>>
>>> | Old Blog
>>>>>>>>>>>>>>>>>>>>>>>>>>>> <http://rmannibucau.wordpress.com <http://rmannibucau.wordpress.com/> <
>>> http://rmannibucau.wordpress.com/ <http://rmannibucau.wordpress.com/>> <
>>>>> http://rmannibucau.wordpress.com/ <http://rmannibucau.wordpress.com/> <http://rmannibucau.wordpress.com/ <http://rmannibucau.wordpress.com/>>>>
>>> | Github <
>>>>>>>>>>>>>>>>>>>>>>>>>>>> https://github.com/rmannibucau <https://github.com/rmannibucau> <
>>> https://github.com/rmannibucau <https://github.com/rmannibucau>> <
>>>>> https://github.com/rmannibucau <https://github.com/rmannibucau> <https://github.com/rmannibucau <https://github.com/rmannibucau>>>> |
>>>>>>>>>>>>>>>>>>>>>>>>>>>> LinkedIn <
>>> https://www.linkedin.com/in/rmannibucau <https://www.linkedin.com/in/rmannibucau> <
>>> https://www.linkedin.com/in/rmannibucau <https://www.linkedin.com/in/rmannibucau>>
>>>>> <https://www.linkedin.com/in/rmannibucau <https://www.linkedin.com/in/rmannibucau> <
>>> https://www.linkedin.com/in/rmannibucau <https://www.linkedin.com/in/rmannibucau>>>> |
>>>>>>>>>>> Book
>>>>>>>>>>>>>>>>>>>>>>>>>>>> <
>>>>>>>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>> 
>>>>> 
>>> https://www.packtpub.com/application-development/java-ee-8-high-performance <https://www.packtpub.com/application-development/java-ee-8-high-performance>
>>> <
>>> https://www.packtpub.com/application-development/java-ee-8-high-performance <https://www.packtpub.com/application-development/java-ee-8-high-performance>
>>>> 
>>>>> <
>>>>> 
>>> https://www.packtpub.com/application-development/java-ee-8-high-performance <https://www.packtpub.com/application-development/java-ee-8-high-performance>
>>> <
>>> https://www.packtpub.com/application-development/java-ee-8-high-performance <https://www.packtpub.com/application-development/java-ee-8-high-performance>
>>>> 
>>>>>> 
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>>>>>>>> Le mar. 4 août 2020 à 18:36, Raymond Auge <
>>>>>>>>>>>>>>>>>>>>> raymond.auge@liferay.com <mailto:raymond.auge@liferay.com> <mailto:
>>> raymond.auge@liferay.com <mailto:raymond.auge@liferay.com>> <mailto:
>>>>> raymond.auge@liferay.com <mailto:raymond.auge@liferay.com> <mailto:raymond.auge@liferay.com <mailto:raymond.auge@liferay.com>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>> .invalid>
>>>>>>>>>>>>>>>>>>>>>>>>>>>> a écrit :
>>>>>>>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> I would make a case to integrate the site
>>> content
>>>>>>>> into
>>>>>>>>>>>> the
>>>>>>>>>>>>>>>> same
>>>>>>>>>>>>>>>>>>>>>>>>>>>> repository
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> that contains the code.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Why? This makes it much more apt to being kept
>>>>> up to
>>>>>>>>>>> date
>>>>>>>>>>>>>>>> since
>>>>>>>>>>>>>>>>>>>>>>>> changes
>>>>>>>>>>>>>>>>>>>>>>>>>>>> can
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> be made to both sources, docs and site content
>>>>> in a
>>>>>>>>>>>> single
>>>>>>>>>>>>>>>>>>>>> changeset.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Thoughts?
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> - Ray
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On Tue, Aug 4, 2020 at 12:31 PM Raymond Auge <
>>>>>>>>>>>>>>>>>>>>>>>> raymond.auge@liferay.com <mailto:raymond.auge@liferay.com> <mailto:
>>> raymond.auge@liferay.com <mailto:raymond.auge@liferay.com>> <mailto:
>>>>> raymond.auge@liferay.com <mailto:raymond.auge@liferay.com> <mailto:raymond.auge@liferay.com <mailto:raymond.auge@liferay.com>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> For reference here is the INFRA ticket [1] for
>>>>> this
>>>>>>>>>>>>>>>> migration
>>>>>>>>>>>>>>>>>>>>> task.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> - Ray
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [1]
>>>>>>>>>>> https://issues.apache.org/jira/browse/INFRA-20633 <https://issues.apache.org/jira/browse/INFRA-20633> <
>>> https://issues.apache.org/jira/browse/INFRA-20633 <https://issues.apache.org/jira/browse/INFRA-20633>> <
>>>>> https://issues.apache.org/jira/browse/INFRA-20633 <https://issues.apache.org/jira/browse/INFRA-20633> <
>>> https://issues.apache.org/jira/browse/INFRA-20633 <https://issues.apache.org/jira/browse/INFRA-20633>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On Tue, Aug 4, 2020 at 12:19 PM Raymond Auge <
>>>>>>>>>>>>>>>>>>>>>>>>>> raymond.auge@liferay.com <mailto:raymond.auge@liferay.com> <mailto:
>>> raymond.auge@liferay.com <mailto:raymond.auge@liferay.com>> <mailto:
>>>>> raymond.auge@liferay.com <mailto:raymond.auge@liferay.com> <mailto:raymond.auge@liferay.com <mailto:raymond.auge@liferay.com>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> David, That would be great!
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Let's see where consensus takes us.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> So far we have antora as a candidate. Does
>>>>> anyone
>>>>>>>>>>> else
>>>>>>>>>>>>>>>> have a
>>>>>>>>>>>>>>>>>>>>>>>> strong
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> desire to take some other solution?
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> - Ray
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On Tue, Aug 4, 2020 at 12:09 PM David Jencks <
>>>>>>>>>>>>>>>>>>>>>>>>>>>> david.a.jencks@gmail.com <mailto:david.a.jencks@gmail.com> <mailto:
>>> david.a.jencks@gmail.com <mailto:david.a.jencks@gmail.com>> <mailto:
>>>>> david.a.jencks@gmail.com <mailto:david.a.jencks@gmail.com> <mailto:david.a.jencks@gmail.com <mailto:david.a.jencks@gmail.com>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> The Camel website is mostly built with Antora
>>>>> (I
>>>>>>>>>>> don’t
>>>>>>>>>>>>>>>>>>>>> understand
>>>>>>>>>>>>>>>>>>>>>>>>>>>> their
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> reluctance to use it for everything).
>>>>>>>>>>>>>>>>>>>>> https://camel.apache.org/ <https://camel.apache.org/> <https://camel.apache.org/ <https://camel.apache.org/>> <
>>> https://camel.apache.org/ <https://camel.apache.org/> <https://camel.apache.org/ <https://camel.apache.org/>>> <
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> https://camel.apache.org/ <https://camel.apache.org/> <
>>> https://camel.apache.org/ <https://camel.apache.org/>> <
>>>>> https://camel.apache.org/ <https://camel.apache.org/> <https://camel.apache.org/ <https://camel.apache.org/>>>>
> 


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message