[MGNLRESTUI-33] Relocate and update the magnoliaDocumentation search result supplier definition Created: 28/Jul/20 Updated: 08/Sep/23 Resolved: 08/Sep/23 |
|
| Status: | Closed |
| Project: | Magnolia REST Client UI |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Martin Drápela | Assignee: | Unassigned |
| Resolution: | Obsolete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Date of First Response: | |
| Epic Link: | RESTClient 2024 |
| Team: |
| Description |
|
1) To make Magnolia docs more readily available directly from the DX Core Find bar, move (and convert) to 2) Enable the supplier and update the DOCS value specifying the Confluence space that is to be queried. Currently there's "DOCS60", which is EoL: The universal DOCS cannot be used as value though. It is just a redirect on Apache, no such space exists. So, as a temporary workaround, for each major Magnolia branch and rest-ui module we could introduce these values:
and so on. Note: Once our docs-as-code is functional, the supplier will have to be either rewritten or scratched altogether, the latter being more likely. |
| Comments |
| Comment by Christopher Zimmermann [ 08/Sep/23 ] |
|
Is this still relevant mdrapela ? |