[
https://issues.apache.org/jira/browse/FINERACT-1253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17224559#comment-17224559
]
Aleksandar Vidakovic commented on FINERACT-1253:
------------------------------------------------
I think we should host at least the latest release docs on fineract.apache.org;
for most people that would be probably the first place they would search. As
for "snapshot" builds from develop I'm not sure what the best place would be
for now.
Ultimately (I'm preparing this in another ticket, let's see if that gets
accepted) I would propose to organize the documentation (and maybe the whole
Fineract Apache site itself) with [https://antora.org|https://antora.org;/]
(kind of a static site generator on top of Asciidoc and Git; I'm simplifying);
the Apache Camel project is doing something similar (they use Asciidoc for most
of their site content, not sure though if they use Antora to manage it); this
would allow to have multiple versions of the docs published and users can
choose with a drop-down which version they want to read (including "latest"
which is built form develop). In this scenario we only need fineract.apache.org.
> Publish the result of the built Fineract doc (and JAR & WAR while we're at
> it?)
> -------------------------------------------------------------------------------
>
> Key: FINERACT-1253
> URL: https://issues.apache.org/jira/browse/FINERACT-1253
> Project: Apache Fineract
> Issue Type: New Feature
> Reporter: Michael Vorburger
> Priority: Major
>
> FINERACT-1191 made me think that it would be great if we could publish the
> result of the built Fineract doc on a site somewhere. Both the PDF and the
> HTM site that Asciidoc presumably builds (I haven't checked it) should be
> "available" somewhere - otherwise that entire effort is not "visible" - which
> would be a shame.
> I'm thinking it could either go to some place like
> https://fineract.apache.org
> or up on https://www.fineract.dev. From a more technical perspective, I guess
> the choices we have is to have it 1. either hosted in a branch of
> https://github.com/apache/fineract, 2. on
> https://github.com/apache/fineract-site (image
> https://fineract.apache.org/docs?), 3. served either from a new Apache Git
> repo (with GitHub pages? Or ASF static page hosting? Need to ask ASF..), 4.
> pushed to a new non-Apache Git repo, 5. no Git repo but just a container with
> static content I can build and run on https://www.fineract.dev as Cloud Run,
> 6. another static CDN.
> We should also make sure that web search crawlers index it by submitting it
> e.g. on G Search Console and have an appropriate robots.txt in it.
> If we do do this, it may be an opportunity to build, keep and HTTP serve the
> {{develop}} version of the JAR & WAR as well while we're at it?
> [~aleks] and [~ptuomola] et al. do chime in.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
