-
Notifications
You must be signed in to change notification settings - Fork 48
Lab Writer's Guide
We should assume that students already have an application and don’t want to start all over again. We should respect that our ISV’s may already have an established business model and are likely to continue to serve non-Microsoft 365 customers. We should also recognize that ISV’s usually already have their own development toolchain, devops, build process, etc. and not prescribe these things. The strategy is to teach the development tasks that are specific to building a monetized Teams app, and help students understand these tasks well enough to adapt them to their own application and process.
App Camp uses MkDocs to generate a static web site that contains the labs and other instructions. The labs themselves are written in MkDocs Markdown. Whatever markdown files are in the docs folder in the main branch will be compiled by github and posted at https://microsoft.github.io/app-camp/.
Lab editors should fork the app-camp repo or, if permitted, work within a branch named with the developer's initials such as "BG-SDKv2Update". When your edits are complete, submit a pull request to the main branch.
For local testing, you can install mkdocs on your computer and view the pages locally, even as you are working in a branch:
- Follow the instructions to install mkdocs: https://www.mkdocs.org/user-guide/installation/
- Install material for mkdocs: https://squidfunk.github.io/mkdocs-material/getting-started/
- At the root of the app-camp repo, run
mkdocs serve - Navigate to http://localhost:8000 to view the instructions; the browser will refresh automatically when you save your file