Is something like that possible somehow?
The use case would be a corporate app in which some user groups would see more content than others.
your response to this question is more then one year old now. Did the entitlement of articles got added to the feature set?
We have the requirement to entitle articles on top-level. The goal is to see the article in the navigation but only if you are entitled to.
Article-level entitlement isn't on the roadmap. Without knowing more about your app, it's difficult to make recommendations. When you say you want to add entitlement articles on top-level, are you referring to the "home" collection or the top-level collection? If you need to add entitlement articles to the home collection, one possibility is to add them to a restricted (or entitled) collection, and then create banners on your home collection that use navto links that jump to the restricted articles. Users would then tap the banner card and sign in to view the restricted article.
thanks a lot for getting back so quickly.
Your banner approach sounds interesting but it's more about having two articles as children of the root collection "default". The content structure would be something like:
-- Collection 1
--- Article 1 [article]
--- Article 2 [article]
-- Collection 2
-- Article 3
-- Article 4
The goal is to have the following entitled entries in the menu:- Collection 1
- Collection 2
- Article 3
- Article 4
Can this also be achieved with the banner approach?
The banner approach wouldn't work in that case. I can't think of a way to added entitled articles to the top-level collection in a way that would be a good user experience. If you try a workaround such as creating a single-article collection set to Content View, that still wouldn't work when you add that collection to the app menu, because launching a collection from the top level always displays the browse page, even if Content View is selected. It seems like the best approach is to add articles 3-4 to an entitled/restricted collection and add that parent collection to the top-level.
yes, I played around with Browse Page and Content View mode of collections and came to the same conclusion: It needs an entitled collection to hold the article. No good UX, indeed.
How about the product's feature road map?
Are entitled articles going to be supported by AEM Mobile sooner or later?
Thanks for this idea. But I'm afraid I don't quite understand. Please provide more details.
When you say "cordova enabled article" do you mean the property "Enable extensibility features" on articles? We enabled this.
What do you mean with "generic collections can be restricted"?