[
https://issues.apache.org/jira/browse/FINERACT-1253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Jakech updated FINERACT-1253:
------------------------------------
Labels: Roadmap2022 (was: )
> 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
> Labels: Roadmap2022
>
> 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.20.10#820010)
