-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Spike: Investigate how to move the user guide into the service #1296
Comments
Options exploredThe issue of having the user guide external to the service has been raised and suggested it might better reside within the Find MoJ data (fmd) service. This spike has explored and evaluated some potential options to migrate our external user guide into fmd. I’ve looked at the following approaches:
|
Open source CMSLooked at Django CMS and Wagtail They look broadly similar in their offerings but would both add a lot of complexity to our application. I looked into Wagtail in a little more detail as reading around it suggested it was more suited to developer led user guides with Django CMS being tailored more towards a non technical audience. I began attempting to implement a couple of pages as a PoC but it was kind of tricky and i aborted as to not spend too much time on this. You can get a flavour of the complexity added by taking a look at https://medium.com/@shahraizali300/integrate-wagtail-into-existing-django-project-django-blog-app-168f2db6cdfe and https://docs.wagtail.org/en/stable/getting_started/integrating_into_django.html# It still wants to push you towards using a wagtail admin screen and creating and storing all your content via django models and backend database tables These seem much more suited to content that’s intended to be a bit more dynamic and allow user interaction. Pros:
Cons:
A CMS basically seems like overkill for our user case, which is a static user guide. My opinion is it would take a fair bit of time and add a lot of complexity plus maintenance burden compared to what we have with the user guide as is. |
Render markdown user guide pages within FMDThe user guide is currently a collection of markdown files. These are good because they are easy to create, edit and quickly anticipate how the page will look, even if done by a non technical team member. This option is to lift those markdown files into the fmd codebase and then we write some code to parse and render the markdown in one of our gov.uk styled html templates. I mocked up something relatively quickly as a PoC. See draft PR #1354 ![]() Further work would be needed to implement the user guide search functionality and make the side menu more akin to the current user guide. Pros:
Cons:
|
Objective
Explore the feasibility of integrating the user guide directly into the data catalogue service, ensuring that users can access relevant guidance seamlessly within the platform and it can still be updated easily.
Done When:
A summary of findings, including the best approach based on feasibility, usability, and maintenance is completed.
The text was updated successfully, but these errors were encountered: