You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The redesigned check tool experience includes snippets of guidance content on the issues details page, to surface the relevant piece of content from the guidance to help users understand how to fix the specific issue that the page highlights:
----
We've previously discussed one approach to implementing this: the so-called "mini-CMS" approach, where guidance content lives closer to the specifications, and can then be fetched by various applications.
This approach is probably too complex for this, though we should consider it alongside any other implementations.
In refinement we discussed the possibility of creating a folder with a series of files that contains the content snippets, with each of those snippets mapped to issues or fields from the specification, and having the application pull the relevant data from there. In reality, this might be a lean first iteration towards the goal of having a mini-CMS.
The scope of this ticket is to spike out possible approaches, and come up with a list of pros and cons, and rough estimations for each approach, to then be played back to the wider team.
The text was updated successfully, but these errors were encountered:
Just some initial thoughts from yesterdays away day: can we use the guidance field in the database? if not why? can we argue for this?
would it suit are needs? is it updatable? specifically by our content designers?
Context:
The redesigned check tool experience includes snippets of guidance content on the issues details page, to surface the relevant piece of content from the guidance to help users understand how to fix the specific issue that the page highlights:
----
The text was updated successfully, but these errors were encountered: