Skip to content

Guide to formatting lab content

Formatting text elements

These text elements are embedded into the lab instructions, so the formatting is always in-line

Element Treatment Example
Function names monospaced with parenthesis Then, call myFunction() to do something ...
Language keywords monospaced ... insert at the top of the try block ...
Symbols in code (variable, object names etc.) monospaced ... the foo object contains something random ...
File and folder names bold Copy the contents of foo.js into the bar folder
Text on screen enclose in double quotes Now click on the "foo" button

Includes

Content that will be used on multiple pages should be placed in include files in the /docs/includes folder.

Here is the syntax:

--8<-- "all-labs-toc.md"

Here is an example::

Do these labs if you want to build a Custom engine agent with custom AI model and orchestration using Azure OpenAI and Teams AI library

Lab steps

Copilot Camp labs use custom web controls to help students track their progress. You will want to include a <cc-end-step /> element at the end of each lab step. See this test page for details.

Links within the labs can be relative and should open within the current window like this.

Links that go outside the labs, including links to source code in the same repo, should open a new window like this

Admonitions

The documentation for admonitions is here. Here's how to use them in Copilot Developer Camp:

Challenge

Here's something to try on your own

Note

Use this format to emphasize or clarify the instructions

Tip

Use this format to show tips and best practices

Warning

Use this format to warn the student about a common pitfall in completing the labs

Danger

Use this format to warn the student about security issues or stability issues that may arise in a production application

Video briefing

Caption

Video briefing

Caption

More information

Caption 1
Caption 2
Caption 3

TL;DR

Use this format to provide ancillary details that may be of interest but are not essential