feat: update guidance for adding new HTML and markdown pages; remove obsolete prompts

Author: Brigit Murtaugh

.github/copilot-instructions.md

@@ -1,3 +1,9 @@
-Every code change needs to be tested before it's committed. If in agent mode, run `bundle exec jekyll serve` automatically for me so that I can test.
+If the user would like to add a new page, clarify if this page is either a:
+* New main page of the website. This will be a .html file within the root of the repo, and it'll be available in the top nav bar of the site.
+* New page of the specification. This will be a .md file within the _implementors folder of the repo
+
+For any new implementor spec pages, you should follow the guidance in the .github/prompts/new-page.prompt.md file.
+
+Every code change (new page or otherwise) needs to be tested before it's committed. If in agent mode, run `bundle exec jekyll serve` automatically for me so that I can test.
 
 End every response with "Happy Build!" on a new line.

.github/instructions/new-html-page.instructions.md

@@ -1,9 +1,18 @@
 ---
 applyTo: '**/*.html'
 ---
+## Guidance for new HTML website pages
 
-## Project coding standards for new HTML pages of the website
-
-Every new HTML page should have a search bar added, similar to the search bar that's available on the features.html, templates.html, and collections.html pages.
+### Layout
+- Every new HTML page should have information like the following at the top, where the title is updated appropriately:
+```
+---
+layout: singlePage
+title: Dev Container Guides
+---
+```
+- The layout should come from the _layouts folder in the repo. Pages should default to `layout: singlePage`.
 
-Any new page should also be added to the end (far right) of the top nav bar of the website.
+### Content
+- Every new HTML page should have a search bar added toward the top, similar to the search bar that's available on the features.html, templates.html, and collections.html pages.
+- Make all headings clickable links.

.github/instructions/new-md-page.instructions.md

@@ -2,6 +2,21 @@
 applyTo: '**/*.md'
 ---
 
-## Project coding standards for new pages of the specification
+## Guidance for new markdown specification pages
 
-Every new specification page should be added to the _implementors folder, just like the pages in that folder already (like spec.md and features.md).
+### Layout
+- Any new page should have information like the following at the top, where the title, shortTitle, and index are updated appropriately:
+```
+---
+layout: implementors
+title:  "Dev Container Templates distribution and discovery"
+shortTitle: "Templates distribution"
+author: Microsoft
+index: 8
+---
+```
+- The layout comes from the _layouts folder in the repo and will always be `layout: implementors` for pages of this type.
+
+### Content
+- Add an emoji key before any paragraphs or tables using emojis 
+- Make all headings clickable links

.github/prompts/html-page.prompt.md

@@ -0,0 +1,12 @@
+---
+mode: 'agent'
+---
+Your goal is to generate a new page for the website. The page should be similar to the existing pages in terms of layout and design.
+
+If I don't specify initial content, generate some placeholder text.
+
+Any new page should also be added to the end (far right) of the top nav bar of the website.
+
+Any new implementor .md file should be added to the table of contents box visible within the /implementors route.
+
+Every new page needs to be tested before it's committed. Run `bundle exec jekyll serve` automatically for me so that I can test.