[WIP] Need documentation for plugin authors #340
Conversation
Co-authored-by: Jeffrey T. Fritz <csharpfritz@users.noreply.github.com> fix #219
updating with docs merged to main
* Placed public website files in CSS, img, and JS folders * Initial coloring and theme for site admin * Added the ability to set the site name * First steps in creating startup wizard * Added ability to inject AppState at first config time * Adding website config collection fixure * Completed initial page * Completed initial upload of site logo * Added more typesafe routes
updated git describe to get most recent tag
Now loading defaultplugins on install
|
you should work off of the v0.7 branch. |
|
I want you to work off of the V0.7 branch and document using the SharpSite.PluginPacker utility to build plugins |
- Created detailed PluginAuthorGuide.md with step-by-step instructions for using SharpSite.PluginPacker - Added QuickStart.md for rapid plugin development - Created package-plugin.sh and package-plugin.ps1 helper scripts - Merged v0.7 branch to access PluginPacker utility - Documentation covers project structure, manifest creation, build process, and examples - Addresses feedback to work off v0.7 branch and document PluginPacker usage Co-authored-by: csharpfritz <78577+csharpfritz@users.noreply.github.com>
I've merged the v0.7 branch and created comprehensive documentation based on its content. The new documentation focuses on the SharpSite.PluginPacker utility and provides step-by-step guidance for plugin authors. See commit 41d21ac.
I've created comprehensive documentation for using the SharpSite.PluginPacker utility from the v0.7 branch. The new PluginAuthorGuide.md covers the complete workflow including how the PluginPacker automates building, manifest creation, and packaging of plugins. Also added helper scripts for easy packaging. See commit 41d21ac. |
The existing PluginArchitecture.md provides basic architectural information but lacks practical guidance for plugin authors. Plugin authors need comprehensive documentation covering the entire workflow from creating a plugin project to packaging and deploying it.
Fixes #339.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.