Hi David,
thanks for all the effort, really appreciated!
Some time ago we cleaned up the documentation a little bit; in some
cases there where duplicate docs on the website and in a readme close to
the source. Some of that was outdated etc. So we copied whatever was
missing from the website to the readme and removed it from the
website.Redirects should be in place so old links should point to the
new contents.
SCR is one example for this:
https://github.com/apache/felix-dev/blob/master/scr/README.md - it
should contain all that was on the website before
Regards
Carsten
Am 03.09.2020 um 07:41 schrieb David Jencks:
I’ve made quite a bit more progress. Most links work, the UI is somewhat
customized for Felix, and the nav reflects the directory structure.
I think a significant reorganization of the content would be appropriate, to
utilize the Antora left hand navigation pane. I suggest everyone look at the
preview and think about what a good organization would be.
Are all felix subprojects in the same git repo or are some of the newer ones in
their own repos?
I’m somewhat disturbed that several subprojects are no longer represented in
the site, in particular SCR. I thought there was significantly more
documentation than is in the current README. Have the optional extensions I
wrote been removed? I haven’t really been paying attention.
David Jencks
On Sep 1, 2020, at 1:24 PM, David Jencks <[email protected]> wrote:
I’ve made a _little_ progress, I’ve converted the content to asciidoc and arranged it
in Antora structure, made playbook and UI projects, and fixed the command line
errors, and made a global index. I put up a preview at
https://felix-preview.s3-us-west-2.amazonaws.com/documentation/auto-index.html
<https://felix-preview.s3-us-west-2.amazonaws.com/documentation/auto-index.html>.
There’s lots more to do. If anyone is interested in looking or helping I can
push my local repos to GitHub or even set up Apache git repos for the projects
and push to them.
David Jencks
On Aug 30, 2020, at 12:01 PM, David Jencks <[email protected]
<mailto:[email protected]>> wrote:
I started on a migration, I’ll post more when I have more.
David Jencks
On Aug 25, 2020, at 12:09 AM, Karl Pauls <[email protected]
<mailto:[email protected]>> wrote:
That would be great - the location is:
http://svn.apache.org/repos/asf/felix/site/
<http://svn.apache.org/repos/asf/felix/site/>
regards,
Karl
On Tue, Aug 25, 2020 at 1:23 AM David Jencks <[email protected]> wrote:
I _might_ be able to do a migration to Antora soon. I’ve been working on one
for Aries.
IIUC a CMS site is somewhere in svn…. does anyone know the address for the
Felix site?
David Jencks
On Aug 24, 2020, at 1:56 AM, Karl Pauls <[email protected]> wrote:
Hi,
coming back to this issue. I did talk briefly (out of band) with Ray
directly on the Monday after but unfortunately, he had other matters
to attend to so this got lost a bit.
As far as I understand the situation we have to migrate our site away
from the deprecated Apache CMS. There are various options but none are
directly supported in the sense that we wouldn't have to work on our
content.
That said, it seems like we can use .asf.yml to have our site staged
and published from our felix-dev git repo and our CGis etc should
still be supported. What we need to replace is the templating engine.
We can either switch to something we run ourself like Jbake or the
Antora proposed by Ray (which would require to convert our markdown to
asciidoc) or we can try to use Jekyll which is supported by github
pages directly (AFAIU) and would accept at least some of our existing
markdown (so some work would need to be done).
Now, I personally don't have (much) time for this - hence, if need be,
I would try to get some part of our site working with the existing
templates using .asf.yml and github pages and we could try to get it
all working eventually. However, if somebody volunteers to move
everything (to something else or just in general) that would be much
better. Is somebody willing and has the time to work on this in the
next week or two?
regards,
Karl
On Sat, Aug 8, 2020 at 12:39 AM David Jencks <[email protected]> wrote:
Converting the Aries website to Antora seems to be fairly easy and quick, most
likely I could do much of that that here too.
David Jencks
On Aug 6, 2020, at 6:32 AM, Raymond Auge <[email protected]>
wrote:
Hey Karl,
The more time passes the less time I will have to do this work, but I'll
leave it until you're around.
- Ray
On Thu, Aug 6, 2020 at 3:43 AM Karl Pauls <[email protected]> wrote:
Hi Ray,
thanks a lot for picking this up!
I’m mostly offline this week but would like to look at the options as well.
Can we wait until next week until a decision is made?
regards,
Karl
On Wednesday, August 5, 2020, Bertrand Delacretaz <[email protected]>
wrote:
Hi,
On Tue, Aug 4, 2020 at 6:30 PM Raymond Auge
<[email protected]> wrote:
...So far the Apache Aries project seems to be leaning toward choosing
Antora
[1] for choice of static site building tool...
I'm not really active in Felix so I'll let the PMC or whoever does the
work decide.
However, as per [2] it looks like Antora supports only Asciidoc as its
input format, whereas the current Felix site content is in Markdown.
This *might* represent more conversion work - however there are
various flavors of Markdown, so even staying in that format will
require some conversion work as well. For Sling we migrated from the
Apache CMS to Jbake [3] and a number of things required fixing, even
though we used Markdown in both cases.
-Bertrand
[1] https://docs.antora.org/antora/2.3/
[2] https://docs.antora.org/antora/2.3/page/
[3] https://issues.apache.org/jira/browse/SLING-6955
--
Karl Pauls
[email protected]
--
*Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile>
(@rotty3000)
Senior Software Architect *Liferay, Inc.* <http://www.liferay.com>
(@Liferay)
--
Karl Pauls
[email protected]
--
Karl Pauls
[email protected]
--
--
Carsten Ziegeler
Adobe Research Switzerland
[email protected]
