This is an automated email from the ASF dual-hosted git repository.
bdelacretaz pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/sling-whiteboard.git
The following commit(s) were added to refs/heads/master by this push:
new b1c42be Update Status
b1c42be is described below
commit b1c42be20567b1f49aed9f39dd12917a38bb73ea
Author: Bertrand Delacretaz <[email protected]>
AuthorDate: Thu Nov 26 15:29:57 2020 +0100
Update Status
---
remote-content-api/README.md | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/remote-content-api/README.md b/remote-content-api/README.md
index e4fbdd5..f8a0183 100644
--- a/remote-content-api/README.md
+++ b/remote-content-api/README.md
@@ -3,6 +3,8 @@
This is an _early days_ experiment to implement a document-oriented
Remote Content Access HTTP API for Sling content.
+**STATUS** as of November 26th 2020: a simple way of converting Sling
Resources to tree-like structures is implemented and used to generate a
navigable HTTP API. The next step is to inject the [Sling Type
System](https://cwiki.apache.org/confluence/display/SLING/Sling+Type+System%3A+motivation+and+requirements)
ideas as a declarative way to customize the Resource conversions, define which
Resource properties are useful for navigation, which ones can be ignored, how
deep to recurse to bui [...]
+
_Document-oriented_ means that the API exposes higher level objects than
Sling resources, typically documents which represent website pages and
similar content objects.
@@ -63,4 +65,4 @@ the edge-side rendering code.
The test content uses `com.adobe.aem.guides:aem-guides-wknd.ui.content.sample`
which is MIT
licensed. Minimal "fake" JCR nodetype definitions are used to allow this
content to load, as
-we don't really care about the details of these node types besides their names.
\ No newline at end of file
+we don't really care about the details of these node types besides their names.
