Timeline for Headless implementation of Tridion Docs
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 5, 2020 at 12:50 | answer | added | Rick Pannekoek | timeline score: 2 | |
| May 4, 2020 at 18:00 | history | tweeted | twitter.com/StackTridion/status/1257369452640960513 | ||
| May 4, 2020 at 17:05 | comment | added | Saurabh Gangwar | @Velmurugan I don't want a DITA-XML to XHTML conversion but DITA-XML to JSON. The former conversion assumes that the consuming clients would be web clients. In my case, the clients are not web clients and expect a headless data format like JSON in place of XHTML. | |
| May 4, 2020 at 14:02 | comment | added | Shiva | Having the topicbody as a json opens up endless integration avenues in the web application, in my opinion. I have hit a similar limitation in the past and I do not think that there is any community related work on it. The recommendation is to have a deployer extension and publish to a secondary content store. There are various "open source" DITA OT transforms to JSON but it is too much work and not recommended, since it interferes with the default dynamic delivery pipeline. | |
| May 4, 2020 at 7:00 | comment | added | Velmurugan♦ | AFAIK - Topic content already converded from DITA-XML to XHTML and stored in broker as DD4T/DXA json, title field already processed and stored as separate field, why you need topicbody content as json?, it's rich text values right. I dont understand why you want topic content as json? it's still similar to sites richtext field content. | |
| May 4, 2020 at 4:44 | history | asked | Saurabh Gangwar | CC BY-SA 4.0 |