Add more clear instructions on serving the ACE in the workbench

[rabwill]

Add more clear instructions on serving the ACE in the workbench

I ran gulp serve -l --nobrowser command as per instruction but did not get my webpart to show up in https://{tenant}.sharepoint.com/_layouts/15/workbench.aspx
I had to manually open https://localhost:4321 and accept to proceed in my browser. Once this was done, the webpart showed up in the list of webparts in the local webserver.
This needs to be captured in the document.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 010f798c-ec19-8cc1-b9d3-84ca31cb6e62
• Version Independent ID: d76b36f9-620d-f82c-7122-7cd2a468dc6d
• Content: Build your first SharePoint Adaptive Card Extension
• Content Source: docs/spfx/viva/get-started/build-first-sharepoint-adaptive-card-extension.md
• Product: sharepoint
• Technology: sharepoint-framework
• GitHub Login: @VesaJuvonen
• Microsoft Alias: vesaj

Thank you for reporting this issue. We will be triaging your incoming issue as soon as possible.

[waldekmastykarz]

Have you trusted the dev certificate as mentioned in the setup instructions?

[rabwill]

@waldekmastykarz that makes sense with the assumption that the developer started this journey from
https://docs.microsoft.com/en-us/sharepoint/dev/spfx/viva/overview-viva-connections
If they come to page https://docs.microsoft.com/en-us/sharepoint/dev/spfx/viva/get-started/build-first-sharepoint-adaptive-card-extension to Build your first SharePoint Adaptive Card Extension would this be the case assuming that those folks are new to this? I felt like had to jump to three links before I could start.
Would it help if we give minimum perquisites.

• Node 12 LTS
• Gulp
• Yoeman
  And before the serve script, may be ask to trust the dev cetificate?
  Happy to help too if this looks like an improvements.

[waldekmastykarz]

Good idea! What if linked to the existing setup steps and prerequisites so that we can keep them in one place and when they change we'd update them consistently throughout the docs?

[github-actions]

Thank you for taking the time to file an issue. We periodically archive older or inactive issues as part of our issue management process, which automatically closes them once they are archived.

If you’d like to understand more about why and how we handle archived (closed) issues, please see Our approach to closed issues.

We appreciate your contribution and if this is still an active issue with the latest SPFx versions, please do resubmit the details. We needed to perform a cleanup, so that we can start with a clean table with a new process. We apologize for the inconvenience this might cause.