refactor(breadcrumb): replace 'strong' with 'breadcrumb' tags

[escii]

solves issue FusionAuth/fusionauth-issues#2572

[tonyblank]

LGTM - so many breadcrumbs, I feel like a duck!

[Aaron-Ritter]

thanks for the review @tonyblank while merging the latest updates i found a mistake in a few changes we did where it should have been replaced with <UIelement></UIelement> instead.

[Aaron-Ritter]

@alex-fusionauth I've merged the latest changes and updated some newly introduced <strong> tags and we are ready to merge. As discussed, while reviewing for any other changes the single step navigation instructions. I've update all these accordingly as well with the <Breadcrumb> tag.

The few ones unclear right now are the ones where it refers to navigate to a section rather a full page/tab.

[Aaron-Ritter]

@alex-fusionauth defined the sections as a <InlineUIElement>

[andrewpai]

Here is a file of lines that in most cases need <Breadcrumb> instead of some other styling. A few need <InlineUIElement>.
breadcrumbs-needed.txt

[Aaron-Ritter]

Here is a file of lines that in most cases need <Breadcrumb> instead of some other styling. A few need <InlineUIElement>. breadcrumbs-needed.txt

@andrewpai Working on this at the moment, and wanted to clarify, we will not only change the site content but all blog posts too with the same concept. And according to that i will update the blog section in DocsDevREADME.md with that guideline too.

[andrewpai]

Here is a file of lines that in most cases need <Breadcrumb> instead of some other styling. A few need <InlineUIElement>. breadcrumbs-needed.txt

@andrewpai Working on this at the moment, and wanted to clarify, we will not only change the site content but all blog posts too with the same concept. And according to that i will update the blog section in DocsDevREADME.md with that guideline too.

Correct, we should make our docs consistent across /docs, /blog, and /articles.

[Aaron-Ritter]

Thanks @andrewpai,

We will go ahead and define a read-only form field as InlineField as it is still a form field.

fusionauth-site/DocsDevREADME.md

Line 42 in d73546e

- If you are referencing a field in a form or JSON API doc, use the [InlineField](astro/src/components/InlineField.astro) component: `<InlineField>Issuer</InlineField>`.

If it comes to the field input, we go ahead and use the <strong> tag everywhere unless you want to create a custom tag.

@andrewpai We discovered the issue that linting will complain about the usage of <strong> tags in mdx files:

> [email protected] lint
> eslint src/content/blog/swift-sdk-beta.mdx src/content/docs/sdks/android-sdk.mdx src/content/docs/sdks/swift-sdk.mdx src/content/quickstarts/quickstart-swift-ios-native-appauth.mdx src/content/quickstarts/quickstart-swift-ios-native.mdx


/home/runner/work/fusionauth-site/fusionauth-site/astro/src/content/quickstarts/quickstart-swift-ios-native.mdx
  63:56   error  Unexpected HTML tag [strong], use markdown instead  remark-lint-no-html
  63:139  error  Unexpected HTML tag [strong], use markdown instead  remark-lint-no-html

[Aaron-Ritter]

@synedra @andrewpai @mooreds I would like to get this PR merged, after spending another 5 hours on it getting everything merged from main, and all strong, Breadcrumb, InlineField or InlineUIElement eslint errors fixed.

On the eslint topic: I've run a check on all changed files and created a fix for the pr-linting #3600.

The part which is still outstanding on how to handle the input in to InlineField as we cant use strong we need an additional definition for that e.g. InlineFieldInput. But I would suggest since we’re already having 311 files changed that we do this in a second iteration.

[Aaron-Ritter]

@andrewpai as discussed I merged the latest changes, updated all the newly added old-style breadcrumbs. In addition, I fixed some of the obvious link errors throughout the documents modified in this PR.

Chatted with him in slack.