-
Notifications
You must be signed in to change notification settings - Fork 35
Added community guide links for Azure Static Web Apps hosting #92
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -109,3 +109,10 @@ Your documentation is now published under `<username>.gitlab.io/<repository>`. | |
| [site_dir]: setup/basics.md#site_dir | ||
| [default branch]: https://docs.gitlab.com/ee/user/project/repository/branches/default.html | ||
|
|
||
| ## Other | ||
|
|
||
| We cannot document every hosting provider here. The following community guides | ||
| describe how to deploy a Zensical site elsewhere: | ||
|
|
||
| * [Azure Static Web Apps with GitHub](https://zensical-guides.hypercat.net/azure-static-web-app-github/) | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Should this be "GitHub Actions", so it is clear what the "GitHub" part does here? |
||
| * [Azure Static Web Apps with Azure DevOps](https://zensical-guides.hypercat.net/azure-static-web-app-devops/) | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Would it help us to have links to the issue tracker here - or should there be a link in the guide itself? I know the repository is linked in the header but a note on reporting issues in the right place might still be a good idea. We could make a policy decision that we only link to guides that clearly indicate where issues should be reported. This may seem like a relatively minor issue but I think we save ourselves a lot of trouble if we are as clear about it as possible. |
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would like this to be more explicit, stating that we do not maintain these guides and that if people find issues they should contact the respective maintainers. How about:
"...site elsewhere. If you find an issue with one of these guides, please contact the author."
This loses the colon just before the list but I think that is ok.