Hi Warren_Brill No Way to get it using APIs as no such node exists in API results. But you can use "Node Detailed Description" OOB component as a work around.
Unfortunately, using the OOB "Node Detailed Description" isn't an option, because
1) There is no place to put the component on the page quilts
2) The content in the Description (on the page, under the node title) is intended (and written) for users. This content also propagates to the "Description" meta-tag, which is not logical, since readers and search engines have different content needs. Therefore, if we did use the OOB component, we have two descriptions on the page, with conflicting content.
Hi Warren_Brill
1. You can place anywhere on the page i.e. header sidebar etc.
It seems this OOB component does not work in wrapper section but you can keep it anywhere on the page. Alternatively, you can include the below component in common page header.
<component id="common.widget.node-description"/>
But it would be displayed on specific pages i.e. Blog, Forum, TKB, Idea Exchange, Group etc as all these ask users about the detailed description at creation time.
2. There are two different component as below so make sure you did not add both.
<component id="common.widget.node-information"/> // Node Description <component id="common.widget.node-description"/> // Node detailed description
It would display single description if you add only one component.
I'm trying to put the "Detailed Description" into the source code but not display it anywhere on the page. I wasn't clear - I want to expose the contents of the Detailed Description only to search engines. The contents of the normal "Description" - which is already displayed, essentially in the "sub-heading" position - by virtue of the fact that it is for readers' consumption, often cannot be optimized for SEO.
I still find it very counter-intuitive that the "Detailed Description" does not generate a named text string.
