Low code workflow naming standard

[ARobinson26]

Is this pull request a content or a code change? (Please fill in the relevant section and delete the other)

Code change

I can confirm:

Accessibility considerations

• [ ] Please review the accessibility checks for layout changes.

• [x] This change will not change layouts, page structures or anything else that might impact accessibility

or

• [ ] This change might impact accessibility, automated aXe tests cover the impact

or

• [ ] This change might impact accessibility and is not covered by automated aXe tests - manual testing has been performed (If the change might impact accessibility then please add some further information here)

Content change

• [ ] Please review the accessibility checks for content changes.

I can confirm:

• [x] Content does not include any code or configuration changes (excluding frontmatter information)
• [x] Content meets the content standards e.g. Writing a principle and Writing a standard
• [x] Content is suitable to open source, i.e.:
  • Content does not relate to unreleased gov policy
  • Content does not refer to anti-fraud mechanisms
  • Content does not include sensitive business logic
• [x] Last updated date for content is correct

[ARobinson26]

I'm unsure on whether we want to tag individual tools on standards. I feel like it would be a good idea to help find standards specific to the stack you're working with but appreciate it'd be difficult to keep maintained. Open to thoughts!

[edhamiltonHO]

I'm unsure on whether we want to tag individual tools on standards. I feel like it would be a good idea to help find standards specific to the stack you're working with but appreciate it'd be difficult to keep maintained. Open to thoughts!

Good question this, would be good to solidify a position on it. Some thoughts:

They are only tags, don't think we want to be too prescriptive on how they are used as long as they work and are useful. We should try to avoid hanging much site functionality off them

Tags should provide links between different content articles that relate to the same topic, 1 to many. Therefore I wouldn't expect us to create tags for things that would likely only relate to one content article (not that that is necessarily the case here, but might be).

The site search will pick up on all text in in a page, you don't need to create tags for that to work. You could instead refer to the tools in a list in the content body itself, this could lead to duplication though - e.g. you wouldn't want to be listing tools/stack in every low code standard.

[jeff-horton-ho-sas]

The site search will pick up on all text in in a page, you don't need to create tags for that to work. You could instead refer to the tools in a list in the content body itself, this could lead to duplication though - e.g. you wouldn't want to be listing tools/stack in every low code standard.

If we found content was being added just to optimise search, we could add support for a searchTerms list in the page front matter and append it to the page content when generating the search index https://github.com/UKHomeOffice/engineering-guidance-and-standards/blob/main/_includes/layouts/search-index.njk#L9

[edhamiltonHO]

The site search will pick up on all text in in a page, you don't need to create tags for that to work. You could instead refer to the tools in a list in the content body itself, this could lead to duplication though - e.g. you wouldn't want to be listing tools/stack in every low code standard.

If we found content was being added just to optimise search, we could add support for a searchTerms list in the page front matter and append it to the page content when generating the search index https://github.com/UKHomeOffice/engineering-guidance-and-standards/blob/main/_includes/layouts/search-index.njk#L9

Yes, we did this with the standard id field in frontmatter, so people could search for content by that, e.g. SEGAS-00001 or 00001

[ARobinson26]

Addressed comments above from @edhamiltonHO. I've also removed the tech stacks from the tags for now. 👍🏼

[edhamiltonHO]

Rebased in order to verify commits and nudge checks to complete