[isis] 46/47: ISIS-2062: fixes xrefs to rgfis

[da...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

danhaywood pushed a commit to branch ISIS-2062-antora
in repository https://gitbox.apache.org/repos/asf/isis.git

commit 1a87fa30b2a887f1986d7659d54068c44587bcb3
Author: danhaywood <da...@haywood-associates.co.uk>
AuthorDate: Sun Jun 2 17:30:09 2019 +0100

    ISIS-2062: fixes xrefs to rgfis
---
 .../presentation-layer/ContentNegotiationService.adoc   |   1 -
 antora/components/rg/modules/svc/pages/intro.adoc       |   2 +-
 .../vro/assets/images/rgfis/service-collaborations.png  | Bin 0 -> 28874 bytes
 .../components/ug/modules/vro/pages/architecture.adoc   |   2 +-
 4 files changed, 2 insertions(+), 3 deletions(-)

diff --git a/antora/components/rg/modules/fis/pages/presentation-layer/ContentNegotiationService.adoc b/antora/components/rg/modules/fis/pages/presentation-layer/ContentNegotiationService.adoc
index 97a0b7e..861453a 100644
--- a/antora/components/rg/modules/fis/pages/presentation-layer/ContentNegotiationService.adoc
+++ b/antora/components/rg/modules/fis/pages/presentation-layer/ContentNegotiationService.adoc
@@ -174,7 +174,6 @@ image::ContentNegotiationService/accept-json.png[width="700px",link="{imagesdir}
 
 
 
-[_rgfis_presentation-layer_ContentNegotiationService_Configuration]]
 == Configuration
 
 The default `ContentNegotiationServiceXRoDomainType` implementation provides a xref:rg:cfg:configuring-core.adoc[configuration property] which controls whether a mapped domain object is pretty-printed (formatted, indented) or not:
diff --git a/antora/components/rg/modules/svc/pages/intro.adoc b/antora/components/rg/modules/svc/pages/intro.adoc
index 0fd3103..17c4ade 100644
--- a/antora/components/rg/modules/svc/pages/intro.adoc
+++ b/antora/components/rg/modules/svc/pages/intro.adoc
@@ -34,7 +34,7 @@ Importantly, this also minimizes the coupling between your code and Apache Isis,
 The framework also defines a number of "internal" services.
 These are not part of the framework's formal API, in that they use classes that are outside of the applib.
 These internal framework services should be thought of as part of the internal design of the framework, and are liable to change from release to release.
-The internal framework services are documented in the xref:rg:fis:rgfis.adoc#[Framework Internal Services] guide.
+The internal framework services are documented in the xref:rg:fis:about.adoc[Framework Internal Services] guide.
 
 
 
diff --git a/antora/components/ug/modules/vro/assets/images/rgfis/service-collaborations.png b/antora/components/ug/modules/vro/assets/images/rgfis/service-collaborations.png
new file mode 100644
index 0000000..859e5dd
Binary files /dev/null and b/antora/components/ug/modules/vro/assets/images/rgfis/service-collaborations.png differ
diff --git a/antora/components/ug/modules/vro/pages/architecture.adoc b/antora/components/ug/modules/vro/pages/architecture.adoc
index d6a6bcf..d61405c 100644
--- a/antora/components/ug/modules/vro/pages/architecture.adoc
+++ b/antora/components/ug/modules/vro/pages/architecture.adoc
@@ -44,7 +44,7 @@ can be many such implementations, each handling a different target domain type.
 
 This diagram shows how these services collaborate:
 
-image::../rgfis/{imagesdir}RepresentationService/service-collaborations.png[width="800px",link="../rgfis/{imagesdir}RepresentationService/service-collaborations.png"]
+image::rgfis/service-collaborations.png[width="800px",link="{imagesdir}/rgfis/service-collaborations.png"]
 
 
 Taken together these domain services offer a lot of flexibility in terms of the representations that can be generated