This toolkit helps create well-designed Power App experiences on the web & mobile. It contains a component library; PCF controls and other utilities that increase developer productivity. All components utilize the Fluent UI framework to provide consistent and industry-leading user interface design to create optimal user experiences for your custom business applications.
The Creator Kit is a Power Platform managed solution file that contains the following components:
- Reference Canvas App
- Template Starter Apps (Canvas & Model Driven App Custom Page)
- Canvas Component Library
- PCF Components
- Fluent Design Theme Editor
The Creator Kit GitHub Repo contains the source, releases, issues and backlog items of all components that are part of the Creator Kit.
Source code for the Code Components can be found here: https://github.com/Microsoft/powercat-code-components
The latest shipped version is available via Releases. From there, you can download the latest version of all managed solutions that have been tested and are ready for use.
Stay up to date with our releases by subscribing to them:
- Select Watch
- Select Custom > Releases > Apply to receive notifications about our releases
Have you found a bug in the Creator Kit or do you want to suggest a new feature? Either way, please let us now by filing an issue while observing the following guidelines
Before submitting your issue please search the issues to ensure your issue has not already been reported
If your bug or feature request has already been reported, join the conversation by commenting and adding your reaction. Please use reactions to vote and not "+1" comments.
- 👍 - upvote
- 👎 - downvote
Select the Issue template that matches the solution for which you want to submit an issue.
File a single issue per problem and feature request. Do not enumerate multiple bugs or feature requests in the same issue.
Do not add your issue as a comment to an existing issue unless it's for the identical input. Many issues look similar, but have different causes.
The more information you can provide, the more likely someone will be successful at reproducing the issue and finding a fix.
Observe the inline guidelines of the Issue template.
Please find all information on how to install and use the kit on https://docs.microsoft.com/power-platform/guidance/creator-kit/overview
This project has adopted the Microsoft Open Source Code of Conduct.
Resources:
- Microsoft Open Source Code of Conduct
- Microsoft Code of Conduct FAQ
- Contact opencode@microsoft.com with questions or concerns
This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.
Microsoft takes the security of our software products and services seriously, which includes all source code repositories managed through our GitHub organizations, which include Microsoft, Azure, DotNet, AspNet, Xamarin, and our GitHub organizations.
If you believe you have found a security vulnerability in any Microsoft-owned repository that meets Microsoft's Microsoft's definition of a security vulnerability, please report it to us as described below.
Please do not report security vulnerabilities through public GitHub issues.
Instead, please report them to the Microsoft Security Response Center (MSRC) at https://msrc.microsoft.com/create-report.
If you prefer to submit without logging in, send email to secure@microsoft.com. If possible, encrypt your message with our PGP key; please download it from the the Microsoft Security Response Center PGP Key page.
You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Additional information can be found at microsoft.com/msrc.
Please include the requested information listed below (as much as you can provide) to help us better understand the nature and scope of the possible issue:
- Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.)
- Full paths of source file(s) related to the manifestation of the issue
- The location of the affected source code (tag/branch/commit or direct URL)
- Any special configuration required to reproduce the issue
- Step-by-step instructions to reproduce the issue
- Proof-of-concept or exploit code (if possible)
- Impact of the issue, including how an attacker might exploit the issue
This information will help us triage your report more quickly.
If you are reporting for a bug bounty, more complete reports can contribute to a higher bounty award. Please visit our Microsoft Bug Bounty Program page for more details about our active programs.
We prefer all communications to be in English.
Microsoft follows the principle of Coordinated Vulnerability Disclosure.