Luise freese patch 1

[LuiseFreese]

Category

• Content fix
• New article

Related issues

• fixes Howto - Low Code Teams Provisioning #122

Contents of the Pull Request

Fixed typos and formatting and image references as proposed by @sympmarc

[traya1]

Docs Build status updates of commit b558cfc:

⚠️ Validation status: warnings

File	Status	Preview URL	Details
Community/should-everyone-create-teams.md	⚠️Warning	View	Details
Community/media/should-everyone-create-teams/LuiseFreese-LowCodeTeamsProvisioning-2ndflow-initialize-vars.png	✅Succeeded	View
Community/media/should-everyone-create-teams/LuiseFreese-LowCodeTeamsProvisioning-2ndflow-managers-approval.png	✅Succeeded	View
Community/media/should-everyone-create-teams/LuiseFreese-LowCodeTeamsProvisioning-2ndflow-managers-approvalNO.png	✅Succeeded	View
Community/media/should-everyone-create-teams/LuiseFreese-LowCodeTeamsProvisioning-2ndflow-managers-approvalYES.png	✅Succeeded	View
Community/media/should-everyone-create-teams/LuiseFreese-LowCodeTeamsProvisioning-2ndflowparsejson.png	✅Succeeded	View
Community/media/should-everyone-create-teams/LuiseFreese-LowCodeTeamsProvisioning-2ndflowupdateteam.png	✅Succeeded	View
Community/media/should-everyone-create-teams/LuiseFreese-LowCodeTeamsProvisioning-Application.png	✅Succeeded	View
Community/media/should-everyone-create-teams/LuiseFreese-LowCodeTeamsProvisioning-SP-List-columns.png	✅Succeeded	View
Community/media/should-everyone-create-teams/LuiseFreese-LowCodeTeamsProvisioning-SP-List-results.png	✅Succeeded	View
Community/media/should-everyone-create-teams/LuiseFreese-LowCodeTeamsProvisioning-flow-AC.png	✅Succeeded	View
Community/media/should-everyone-create-teams/LuiseFreese-LowCodeTeamsProvisioning-flow-check-membership.png	✅Succeeded	View
Community/media/should-everyone-create-teams/LuiseFreese-LowCodeTeamsProvisioning-flow-create-item.png	✅Succeeded	View
Community/media/should-everyone-create-teams/LuiseFreese-LowCodeTeamsProvisioning-flow-from-pva.png	✅Succeeded	View
Community/media/should-everyone-create-teams/LuiseFreese-LowCodeTeamsProvisioning-flow-initialize-vars.png	✅Succeeded	View
Community/media/should-everyone-create-teams/LuiseFreese-LowCodeTeamsProvisioning-flow-invite.png	✅Succeeded	View
Community/media/should-everyone-create-teams/LuiseFreese-LowCodeTeamsProvisioning-flow-log-request.png	✅Succeeded	View
Community/media/should-everyone-create-teams/LuiseFreese-LowCodeTeamsProvisioning-flow-session-invitation.png	✅Succeeded	View
Community/media/should-everyone-create-teams/LuiseFreese-LowCodeTeamsProvisioning-get-tested-user.png	✅Succeeded	View
Community/media/should-everyone-create-teams/LuiseFreese-LowCodeTeamsProvisioning-provisioningflow.png	✅Succeeded	View
Community/media/should-everyone-create-teams/LuiseFreese-LowCodeTeamsProvisioning-solution-overview.png	✅Succeeded	View
Community/media/should-everyone-create-teams/provisionbot.gif	✅Succeeded

Community/should-everyone-create-teams.md

• Line 202, Column 1: [Warning-link-out-of-scope] File 'media/should-everyone-create-teams/provisionbot.gif' referenced by link 'media/should-everyone-create-teams/provisionbot.gif' will not be built because it is not included in build scope.
• Line 61, Column 1: [Suggestion-alt-text-bad-value] Alt text 'LuiseFreese-LowCodeTeamsProvisioning-flow-session-invitation' is the same as the image file name. This redundancy adds no value for users of screen readers. For accessibility, add more descriptive alt text. NOTE: This Suggestion will become a Warning in late October, 2020.
• Line 75, Column 1: [Suggestion-alt-text-bad-value] Alt text 'LuiseFreese-LowCodeTeamsProvisioning-SP-List-results' is the same as the image file name. This redundancy adds no value for users of screen readers. For accessibility, add more descriptive alt text. NOTE: This Suggestion will become a Warning in late October, 2020.
• Line 106, Column 1: [Suggestion-alt-text-bad-value] Alt text 'LuiseFreese-LowCodeTeamsProvisioning-flow-from-pva' is the same as the image file name. This redundancy adds no value for users of screen readers. For accessibility, add more descriptive alt text. NOTE: This Suggestion will become a Warning in late October, 2020.
• Line 110, Column 1: [Suggestion-alt-text-bad-value] Alt text 'LuiseFreese-LowCodeTeamsProvisioning-flow-initialize-vars' is the same as the image file name. This redundancy adds no value for users of screen readers. For accessibility, add more descriptive alt text. NOTE: This Suggestion will become a Warning in late October, 2020.
• Line 116, Column 1: [Suggestion-alt-text-bad-value] Alt text 'LuiseFreese-LowCodeTeamsProvisioning-flow-check-membership' is the same as the image file name. This redundancy adds no value for users of screen readers. For accessibility, add more descriptive alt text. NOTE: This Suggestion will become a Warning in late October, 2020.
• Line 122, Column 1: [Suggestion-alt-text-bad-value] Alt text 'LuiseFreese-LowCodeTeamsProvisioning-flow-create-item' is the same as the image file name. This redundancy adds no value for users of screen readers. For accessibility, add more descriptive alt text. NOTE: This Suggestion will become a Warning in late October, 2020.
• Line 125, Column 1: [Suggestion-alt-text-bad-value] Alt text 'LuiseFreese-LowCodeTeamsProvisioning-flow-invite' is the same as the image file name. This redundancy adds no value for users of screen readers. For accessibility, add more descriptive alt text. NOTE: This Suggestion will become a Warning in late October, 2020.
• Line 131, Column 1: [Suggestion-alt-text-bad-value] Alt text 'LuiseFreese-LowCodeTeamsProvisioning-flow-AC' is the same as the image file name. This redundancy adds no value for users of screen readers. For accessibility, add more descriptive alt text. NOTE: This Suggestion will become a Warning in late October, 2020.
• Line 137, Column 1: [Suggestion-alt-text-bad-value] Alt text 'LuiseFreese-LowCodeTeamsProvisioning-get-tested-user' is the same as the image file name. This redundancy adds no value for users of screen readers. For accessibility, add more descriptive alt text. NOTE: This Suggestion will become a Warning in late October, 2020.
• Line 141, Column 1: [Suggestion-alt-text-bad-value] Alt text 'LuiseFreese-LowCodeTeamsProvisioning-flow-log-request' is the same as the image file name. This redundancy adds no value for users of screen readers. For accessibility, add more descriptive alt text. NOTE: This Suggestion will become a Warning in late October, 2020.
• Line 145, Column 83: [Suggestion-alt-text-bad-value] Alt text 'LuiseFreese-LowCodeTeamsProvisioning-provisioningflow' is the same as the image file name. This redundancy adds no value for users of screen readers. For accessibility, add more descriptive alt text. NOTE: This Suggestion will become a Warning in late October, 2020.
• Line 153, Column 1: [Suggestion-alt-text-bad-value] Alt text 'LuiseFreese-LowCodeTeamsProvisioning-Application' is the same as the image file name. This redundancy adds no value for users of screen readers. For accessibility, add more descriptive alt text. NOTE: This Suggestion will become a Warning in late October, 2020.
• Line 163, Column 1: [Suggestion-alt-text-bad-value] Alt text 'LuiseFreese-LowCodeTeamsProvisioning-2ndflow-initialize-vars' is the same as the image file name. This redundancy adds no value for users of screen readers. For accessibility, add more descriptive alt text. NOTE: This Suggestion will become a Warning in late October, 2020.
• Line 174, Column 1: [Suggestion-alt-text-bad-value] Alt text 'LuiseFreese-LowCodeTeamsProvisioning-2ndflow-managers-approval' is the same as the image file name. This redundancy adds no value for users of screen readers. For accessibility, add more descriptive alt text. NOTE: This Suggestion will become a Warning in late October, 2020.
• Line 180, Column 1: [Suggestion-alt-text-bad-value] Alt text 'LuiseFreese-LowCodeTeamsProvisioning-2ndflow-managers-approvalNO' is the same as the image file name. This redundancy adds no value for users of screen readers. For accessibility, add more descriptive alt text. NOTE: This Suggestion will become a Warning in late October, 2020.
• Line 184, Column 1: [Suggestion-alt-text-bad-value] Alt text 'LuiseFreese-LowCodeTeamsProvisioning-2ndflow-managers-approvalYES' is the same as the image file name. This redundancy adds no value for users of screen readers. For accessibility, add more descriptive alt text. NOTE: This Suggestion will become a Warning in late October, 2020.
• Line 188, Column 1: [Suggestion-alt-text-bad-value] Alt text 'LuiseFreese-LowCodeTeamsProvisioning-2ndflowparsejson' is the same as the image file name. This redundancy adds no value for users of screen readers. For accessibility, add more descriptive alt text. NOTE: This Suggestion will become a Warning in late October, 2020.
• Line 192, Column 1: [Suggestion-alt-text-bad-value] Alt text 'LuiseFreese-LowCodeTeamsProvisioning-2ndflowupdateteam' is the same as the image file name. This redundancy adds no value for users of screen readers. For accessibility, add more descriptive alt text. NOTE: This Suggestion will become a Warning in late October, 2020.
• Line 202, Column 1: [Suggestion-alt-text-bad-value] Alt text 'provisionbot' is the same as the image file name. This redundancy adds no value for users of screen readers. For accessibility, add more descriptive alt text. NOTE: This Suggestion will become a Warning in late October, 2020.

For more details, please refer to the build report.

If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

For any questions, please:

• Try searching in the Docs contributor and Admin Guide
• See the frequently asked questions
• Post your question in the Docs support channel

[traya1]

Docs Build status updates of commit dc69731:

⚠️ Validation status: warnings

File	Status	Preview URL	Details
Community/should-everyone-create-teams.md	⚠️Warning	View	Details
Community/media/should-everyone-create-teams/LuiseFreese-LowCodeTeamsProvisioning-2ndflow-initialize-vars.png	✅Succeeded	View
Community/media/should-everyone-create-teams/LuiseFreese-LowCodeTeamsProvisioning-2ndflow-managers-approval.png	✅Succeeded	View
Community/media/should-everyone-create-teams/LuiseFreese-LowCodeTeamsProvisioning-2ndflow-managers-approvalNO.png	✅Succeeded	View
Community/media/should-everyone-create-teams/LuiseFreese-LowCodeTeamsProvisioning-2ndflow-managers-approvalYES.png	✅Succeeded	View
Community/media/should-everyone-create-teams/LuiseFreese-LowCodeTeamsProvisioning-2ndflowparsejson.png	✅Succeeded	View
Community/media/should-everyone-create-teams/LuiseFreese-LowCodeTeamsProvisioning-2ndflowupdateteam.png	✅Succeeded	View
Community/media/should-everyone-create-teams/LuiseFreese-LowCodeTeamsProvisioning-Application.png	✅Succeeded	View
Community/media/should-everyone-create-teams/LuiseFreese-LowCodeTeamsProvisioning-SP-List-columns.png	✅Succeeded	View
Community/media/should-everyone-create-teams/LuiseFreese-LowCodeTeamsProvisioning-SP-List-results.png	✅Succeeded	View
Community/media/should-everyone-create-teams/LuiseFreese-LowCodeTeamsProvisioning-flow-AC.png	✅Succeeded	View
Community/media/should-everyone-create-teams/LuiseFreese-LowCodeTeamsProvisioning-flow-check-membership.png	✅Succeeded	View
Community/media/should-everyone-create-teams/LuiseFreese-LowCodeTeamsProvisioning-flow-create-item.png	✅Succeeded	View
Community/media/should-everyone-create-teams/LuiseFreese-LowCodeTeamsProvisioning-flow-from-pva.png	✅Succeeded	View
Community/media/should-everyone-create-teams/LuiseFreese-LowCodeTeamsProvisioning-flow-initialize-vars.png	✅Succeeded	View
Community/media/should-everyone-create-teams/LuiseFreese-LowCodeTeamsProvisioning-flow-invite.png	✅Succeeded	View
Community/media/should-everyone-create-teams/LuiseFreese-LowCodeTeamsProvisioning-flow-log-request.png	✅Succeeded	View
Community/media/should-everyone-create-teams/LuiseFreese-LowCodeTeamsProvisioning-flow-session-invitation.png	✅Succeeded	View
Community/media/should-everyone-create-teams/LuiseFreese-LowCodeTeamsProvisioning-get-tested-user.png	✅Succeeded	View
Community/media/should-everyone-create-teams/LuiseFreese-LowCodeTeamsProvisioning-provisioningflow.png	✅Succeeded	View
Community/media/should-everyone-create-teams/LuiseFreese-LowCodeTeamsProvisioning-solution-overview.png	✅Succeeded	View
Community/media/should-everyone-create-teams/provisionbot.gif	✅Succeeded

Community/should-everyone-create-teams.md

• Line 202, Column 1: [Warning-link-out-of-scope] File 'media/should-everyone-create-teams/provisionbot.gif' referenced by link 'media/should-everyone-create-teams/provisionbot.gif' will not be built because it is not included in build scope.
• Line 202, Column 1: [Suggestion-alt-text-bad-value] Alt text 'provisionbot' is the same as the image file name. This redundancy adds no value for users of screen readers. For accessibility, add more descriptive alt text. NOTE: This Suggestion will become a Warning in late October, 2020.

For more details, please refer to the build report.

If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

For any questions, please:

• Try searching in the Docs contributor and Admin Guide
• See the frequently asked questions
• Post your question in the Docs support channel

[traya1]

Docs Build status updates of commit 54cd19e:

⚠️ Validation status: warnings

File	Status	Preview URL	Details
Community/should-everyone-create-teams.md	⚠️Warning	View	Details
Community/media/should-everyone-create-teams/LuiseFreese-LowCodeTeamsProvisioning-2ndflow-initialize-vars.png	✅Succeeded	View
Community/media/should-everyone-create-teams/LuiseFreese-LowCodeTeamsProvisioning-2ndflow-managers-approval.png	✅Succeeded	View
Community/media/should-everyone-create-teams/LuiseFreese-LowCodeTeamsProvisioning-2ndflow-managers-approvalNO.png	✅Succeeded	View
Community/media/should-everyone-create-teams/LuiseFreese-LowCodeTeamsProvisioning-2ndflow-managers-approvalYES.png	✅Succeeded	View
Community/media/should-everyone-create-teams/LuiseFreese-LowCodeTeamsProvisioning-2ndflowparsejson.png	✅Succeeded	View
Community/media/should-everyone-create-teams/LuiseFreese-LowCodeTeamsProvisioning-2ndflowupdateteam.png	✅Succeeded	View
Community/media/should-everyone-create-teams/LuiseFreese-LowCodeTeamsProvisioning-Application.png	✅Succeeded	View
Community/media/should-everyone-create-teams/LuiseFreese-LowCodeTeamsProvisioning-SP-List-columns.png	✅Succeeded	View
Community/media/should-everyone-create-teams/LuiseFreese-LowCodeTeamsProvisioning-SP-List-results.png	✅Succeeded	View
Community/media/should-everyone-create-teams/LuiseFreese-LowCodeTeamsProvisioning-flow-AC.png	✅Succeeded	View
Community/media/should-everyone-create-teams/LuiseFreese-LowCodeTeamsProvisioning-flow-check-membership.png	✅Succeeded	View
Community/media/should-everyone-create-teams/LuiseFreese-LowCodeTeamsProvisioning-flow-create-item.png	✅Succeeded	View
Community/media/should-everyone-create-teams/LuiseFreese-LowCodeTeamsProvisioning-flow-from-pva.png	✅Succeeded	View
Community/media/should-everyone-create-teams/LuiseFreese-LowCodeTeamsProvisioning-flow-initialize-vars.png	✅Succeeded	View
Community/media/should-everyone-create-teams/LuiseFreese-LowCodeTeamsProvisioning-flow-invite.png	✅Succeeded	View
Community/media/should-everyone-create-teams/LuiseFreese-LowCodeTeamsProvisioning-flow-log-request.png	✅Succeeded	View
Community/media/should-everyone-create-teams/LuiseFreese-LowCodeTeamsProvisioning-flow-session-invitation.png	✅Succeeded	View
Community/media/should-everyone-create-teams/LuiseFreese-LowCodeTeamsProvisioning-get-tested-user.png	✅Succeeded	View
Community/media/should-everyone-create-teams/LuiseFreese-LowCodeTeamsProvisioning-provisioningflow.png	✅Succeeded	View
Community/media/should-everyone-create-teams/LuiseFreese-LowCodeTeamsProvisioning-solution-overview.png	✅Succeeded	View
Community/media/should-everyone-create-teams/provisionbot.gif	✅Succeeded

Community/should-everyone-create-teams.md

• Line 202, Column 1: [Warning-link-out-of-scope] File 'media/should-everyone-create-teams/provisionbot.gif' referenced by link 'media/should-everyone-create-teams/provisionbot.gif' will not be built because it is not included in build scope.

For more details, please refer to the build report.

If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

For any questions, please:

• Try searching in the Docs contributor and Admin Guide
• See the frequently asked questions
• Post your question in the Docs support channel

[LuiseFreese]

@sympmarc did my very best with a lil help of my dear friends @hugoabernier and @PopWarner . Would love to hear your feedback.

[sympmarc]

I'm trying to figure out what this errors means. I have it in another article, too.

Line 202, Column 1: [Warning-link-out-of-scope] File 'media/should-everyone-create-teams/provisionbot.gif' referenced by link 'media/should-everyone-create-teams/provisionbot.gif' will not be built because it is not included in build scope.

Thanks for the fixes!

[LuiseFreese]

It only occurs with gifs. ¯_(ツ)_/¯

So what is the best step regarding this article?

[sympmarc]

I've asked @JoanneHendrickson about that issue; I'll let you know. I'll also take another pass through as editor - and then publish!

[hugoabernier]

It isn't just for @LuiseFreese 's changes, it happens for all .gif files. I suspect it just says that the build will not process those files, but they don't get excluded.

[sympmarc]

It was indeed a GIF file issue. @JoanneHendrickson has the team fixing things for us...