Updates to 2 blog posts (#2144)

* v1 of Produce Dataverse Table Schema Documentation from Metadata Spreadsheet

* Remove double space in title

* PNP changed to PnP in last paragraph

* Thumbnail added

* Thumbnail added to metadata

* Changed section headers to be H2

* Changed instructions to be in bold

* Instructions changed to be in bold

* Further 'cell' instruction changed to bold

* Update index.md

minor formatting changes

* Initial commit

* Adding flow details

* Adding more content

* More content and images

* Added outputs

* DevOps and acknowledgement and more images

* Added table of contents, solution details, images

* v1 for sending for review

* Last changes

* Making 3 minor content changes

* Update index.md

* Initial commit

* Adding Power Automate Management comment

* Added more on the Power Automate Management connector

* Correcting two typos

* Adding thumbnail

* Updated thumbnail

* Added thumbnail to metadata

* Added Power Automate tag

* Correcting typo, minor improvements, update date

* Added HTML content and alternative flow

* Added horrizonal line as section break

* Initial commit

* Added thumbnail and content changes

* Update index.md

updated date to bump up the article

* Commit for short blog post

* UPdated initial paragraph

* Updated publish date/time

* Improving choices post and adding icons post

* Setting date for draft post to 2025

* Setting date to 6 Feb

* Moving first post date to 7Feb

* Update for 1st post, making 2nd in year in future

* Updating date and minor correction

* Updating content, images and publish date

* Fixing lint issues

* New blog post

* Commit of new post

* Update index.md

bumps up scheduling date

* Updates to two blog posts

* updated image as Microsoft changed a button label in Teams

---------

Co-authored-by: Luise Freese <[email protected]>

Author: alex-mcla

content/post/preparing-for-dark-mode-model-driven-app-icons/index.md

@@ -14,6 +14,10 @@ tags: [Power Apps]
 type: "regular"
 ---
 
+## UPDATE
+
+Although the content below is still valid, there's a better, and easier way of doing it: [Preparing for Model-Driven Apps Dark Mode Icons - Improved](https://pnp.github.io/blog/post/preparing-for-dark-mode-model-driven-app-icons-improved/).
+
 ## Dark Mode
 
 Dark mode has become increasingly popular in software applications, providing a sleek and eye-friendly alternative to the traditional light theme. While it’s not officially available for model-driven apps, you can experiment with it by adding a simple URL flag. In this post, we’ll delve into the impact of dark mode on icons in model-driven apps.

content/post/traceability-between-workshops-and-user-stories/images/open-in-stream.png

@@ -25,6 +25,19 @@ Link workshop transcripts to User Stories by:
 
 ---
 
+## Contents
+
+- [TL;DR](#tldr)
+- [Contents](#contents)
+- [Introduction](#introduction)
+- [Step 1: Record the Workshop, then Annotate in Stream](#step-1-record-the-workshop-then-annotate-in-stream)
+- [Step 2: Add New User Stories in DevOps](#step-2-add-new-user-stories-in-devops)
+- [Step 3: Create DevOps Wiki Page](#step-3-create-devops-wiki-page)
+- [Tracing from the User Story to the Recording](#tracing-from-the-user-story-to-the-recording)
+- [Postscript](#postscript)
+
+---
+
 ## Introduction
 
 This post provides guidance on how to achieve effective traceability between workshop recordings and the corresponding Azure DevOps User Stories. This approach enables users to reference the exact part of a workshop where a user story was discussed, facilitating clarification if needed at a later time.
@@ -33,11 +46,11 @@ This post assumes Teams is used for workshops and Azure DevOps for backlog manag
 
 ---
 
-## Step 1: Record and Annotate in Stream
+## Step 1: Record the Workshop, then Annotate in Stream
 
 Record the workshop (preferably with transcription turned on, even better with access to Copilot).
 
-Once the recording has been saved, move from Teams to Stream.
+Once the recording has been saved, move from Teams to Stream using the 'Watch in browser' button.
 
 ![Open recording in Stream](images/open-in-stream.png)
 
@@ -90,3 +103,23 @@ This then allows you to trace back from the User Story, via the Wiki page, to th
 ![User story, showing link to the Wiki page](images/user-story-link.png)
 
 NOTE: if you have Copilot available in Teams or Stream, the reviewed and edited version of the summary can be used as well.
+
+---
+
+## Postscript
+
+Following the initial posting of this, I had the following conversation on LinkedIn with Microsoft MVP [Hamish Shield](https://www.linkedin.com/in/hamishsheild/):
+
+Hamish:
+
+    Alex McLachlan nice one. I don’t do this as it seems like a lot of work! But I can see how it would be super helpful. I often refer back to workshop recordings. One thing I have been thinking about is how might an AI agent do something like this for us…
+
+Alex:
+
+    Hamish Sheild that's a very valid point / comment about agents. There are three level to consider here.
+
+    Firstly, your comment about it being a lot of work is very true, but I find I get 2-3 times more value from listening to the workshop recording than just going on memory / notes / Miro board. This enables the resulting user stories to be more complete and more accurate, reducing bugs and re-work. To some extent whether this is appropriate on a project depends on the availability of the SMEs (but have you ever worked on a project where they are as available as you'd like?)
+
+    Secondly, you could use Copilot's summary, together with a prompt along the lines of "extract the requirements from this workshop and express them in the form AS A ... giving links to the start of where they are mentioned". This could be added as wiki content and (after careful review) add them to DevOps.
+
+    Lastly, it would be possible to write an agent to do the second option and add the user stories to DevOps for review there. Personally, I wouldn't currently go for this option at the moment given the level of hallucination in gen AI and the lack of it's ability to have a memory model of what the system is needing to do and context of the rest of the backlog.