[DOCU-2432] Move or rename API page content Created: 14/Apr/22 Updated: 11/May/22 Resolved: 10/May/22 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Mikaël Geljić | Assignee: | Martin Drápela |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Documentation page URL: | https://docs.magnolia-cms.com/product-docs/6.2/Developing/API.html |
| Reporter Name: | Mikaël Geljić |
| Email: | mikael.geljic@magnolia-cms.com |
| Description |
|
By now most developers understand API as Web/HTTP/REST API. Whereas the whole content of this API page is backend Java APIs. We did a good job cleaning up and reordering the sub-pages recently, shall we move content to the sub-page Java Server APIs? Instead the top-level API page would be expected to give an overview of the web APIs we've got (Delivery, GraphQL, etc.), primarily, maybe point to Java APIs at the end for unleashing full steam flexibility, backend integrations & customizations. |