diff --git a/pages/docs/community-docs/watcloud/development-manual.mdx b/pages/docs/community-docs/watcloud/development-manual.mdx index c5aef3d..11c4c58 100644 --- a/pages/docs/community-docs/watcloud/development-manual.mdx +++ b/pages/docs/community-docs/watcloud/development-manual.mdx @@ -376,9 +376,4 @@ Now, we can run the provisioner as usual. Terraform will use the local provider - https://discuss.hashicorp.com/t/development-overrides-for-providers-under-development/18888/2 - https://developer.hashicorp.com/terraform/cli/config/config-file#development-overrides-for-provider-developers -{ -// Separate footnotes from the main content -} -import { Separator } from "@/components/ui/separator" - diff --git a/pages/docs/community-docs/watcloud/guidelines.mdx b/pages/docs/community-docs/watcloud/guidelines.mdx index 3dd8b34..46d5e69 100644 --- a/pages/docs/community-docs/watcloud/guidelines.mdx +++ b/pages/docs/community-docs/watcloud/guidelines.mdx @@ -155,9 +155,4 @@ we are equipped to quickly identify and resolve issues as they arise. -{ -// Separate footnotes from the main content -} -import { Separator } from "@/components/ui/separator" - diff --git a/pages/docs/community-docs/watcloud/maintenance-manual.mdx b/pages/docs/community-docs/watcloud/maintenance-manual.mdx index 758d7ab..550860f 100644 --- a/pages/docs/community-docs/watcloud/maintenance-manual.mdx +++ b/pages/docs/community-docs/watcloud/maintenance-manual.mdx @@ -212,10 +212,4 @@ This will resume the node `tr-slurm1` (allow new jobs to run on it) and clear th Also remember to delete any unexpired reservations (as outlined in [Creating a reservation](#creating-a-reservation)). -{ -// Separate footnotes from the main content -} -import { Separator } from "@/components/ui/separator" - - diff --git a/pages/docs/community-docs/watcloud/observability.mdx b/pages/docs/community-docs/watcloud/observability.mdx index 7ea0f20..afbce72 100644 --- a/pages/docs/community-docs/watcloud/observability.mdx +++ b/pages/docs/community-docs/watcloud/observability.mdx @@ -103,10 +103,4 @@ An example of tracing is recording the different stages of a CI pipeline (e.g. s Currently, WATcloud does not have a tracing system in place. You can following along [this internal issue](https://github.com/WATonomous/infra-config/issues/1795) for updates on the status of our tracing infrastructure. -{ -// Separate footnotes from the main content -} -import { Separator } from "@/components/ui/separator" - - diff --git a/pages/docs/community-docs/watcloud/proxmox.mdx b/pages/docs/community-docs/watcloud/proxmox.mdx index 7f3aeeb..03fdd6e 100644 --- a/pages/docs/community-docs/watcloud/proxmox.mdx +++ b/pages/docs/community-docs/watcloud/proxmox.mdx @@ -648,10 +648,4 @@ If you haven't already, please open a pull request (PR) and review the changes w -{ -// Separate footnotes from the main content -} -import { Separator } from "@/components/ui/separator" - - diff --git a/pages/docs/community-docs/watcloud/user-requests.mdx b/pages/docs/community-docs/watcloud/user-requests.mdx index c23c1f6..98ce2ec 100644 --- a/pages/docs/community-docs/watcloud/user-requests.mdx +++ b/pages/docs/community-docs/watcloud/user-requests.mdx @@ -48,10 +48,4 @@ then the WATcloud admin can add the software package to the cluster Ansible conf [^ansible-config]: At the time of writing, the Ansible configuration can be found [here](https://github.com/WATonomous/infra-config/blob/7d59786e61ce779f20e7cdb8c29b4864fe1b6c31/ansible/roles/ubuntu_dev_vm/tasks/main.yml#L94-L144). Note that removing software packages is a separate step [here](https://github.com/WATonomous/infra-config/blob/7d59786e61ce779f20e7cdb8c29b4864fe1b6c31/ansible/roles/ubuntu_dev_vm/tasks/main.yml#L27-L65). -{ -// Separate footnotes from the main content -} -import { Separator } from "@/components/ui/separator" - - diff --git a/pages/docs/compute-cluster/firewall.mdx b/pages/docs/compute-cluster/firewall.mdx index dada580..a2d9267 100644 --- a/pages/docs/compute-cluster/firewall.mdx +++ b/pages/docs/compute-cluster/firewall.mdx @@ -70,9 +70,4 @@ in the world. Once you are on the UWaterloo VPN, you can connect to the WATcloud [uw-vpn]: https://uwaterloo.atlassian.net/wiki/spaces/ISTKB/pages/262012980/Virtual+Private+Network+VPN -{ -// Separate footnotes from the main content -} -import { Separator } from "@/components/ui/separator" - diff --git a/pages/docs/compute-cluster/getting-access.mdx b/pages/docs/compute-cluster/getting-access.mdx index a4720ca..8d468f7 100644 --- a/pages/docs/compute-cluster/getting-access.mdx +++ b/pages/docs/compute-cluster/getting-access.mdx @@ -30,9 +30,3 @@ In the mean time, please familiarize yourself with the [Machine Usage Guide](./m -{ -// Separate footnotes from the main content -} -import { Separator } from "@/components/ui/separator" - - \ No newline at end of file diff --git a/pages/docs/compute-cluster/machine-usage-guide.mdx b/pages/docs/compute-cluster/machine-usage-guide.mdx index 8fe3b9c..73bee0c 100644 --- a/pages/docs/compute-cluster/machine-usage-guide.mdx +++ b/pages/docs/compute-cluster/machine-usage-guide.mdx @@ -308,9 +308,4 @@ systemctl --user restart docker-rootless ``` -{ -// Separate footnotes from the main content -} -import { Separator } from "@/components/ui/separator" - diff --git a/pages/docs/compute-cluster/quotas.mdx b/pages/docs/compute-cluster/quotas.mdx index 43018af..7771dce 100644 --- a/pages/docs/compute-cluster/quotas.mdx +++ b/pages/docs/compute-cluster/quotas.mdx @@ -131,9 +131,4 @@ On general-use machines, per-user CPU and memory quotas are enforced to ensure f Unlike disk quotas, we don't allow users to request CPU and memory quota increases. Please use [SLURM](./slurm) to run resource-intensive jobs. -{ -// Separate footnotes from the main content -} -import { Separator } from "@/components/ui/separator" - diff --git a/pages/docs/compute-cluster/slurm.mdx b/pages/docs/compute-cluster/slurm.mdx index a71cdd9..2556433 100644 --- a/pages/docs/compute-cluster/slurm.mdx +++ b/pages/docs/compute-cluster/slurm.mdx @@ -597,9 +597,4 @@ If your affiliation is not registered, please have your group lead fill out the [^legacy-affiliation]: Legacy affiliations have the prefix `[Legacy]`. We don't have sufficient information from these affiliations to support them in the SLURM environment. -{ -// Separate footnotes from the main content -} -import { Separator } from "@/components/ui/separator" - diff --git a/pages/docs/compute-cluster/ssh.mdx b/pages/docs/compute-cluster/ssh.mdx index e5bf93b..dde809e 100644 --- a/pages/docs/compute-cluster/ssh.mdx +++ b/pages/docs/compute-cluster/ssh.mdx @@ -149,9 +149,3 @@ Host derek3-ubuntu2 ```bash copy ssh -v derek3-ubuntu2 ``` - - -{ -// Separate footnotes from the main content -} - diff --git a/pages/docs/index.mdx b/pages/docs/index.mdx index ced77f7..d9b51c6 100644 --- a/pages/docs/index.mdx +++ b/pages/docs/index.mdx @@ -84,9 +84,4 @@ We work in close proximity (e.g. we share the same Discord server and Google Wor WATonomous has access to the same [support resources](/docs/compute-cluster/support-resources) as every other group. -{ -// Separate footnotes from the main content -} -import { Separator } from "@/components/ui/separator" - diff --git a/pages/docs/registered-affiliations.mdx b/pages/docs/registered-affiliations.mdx index 0ac958b..ba9af18 100644 --- a/pages/docs/registered-affiliations.mdx +++ b/pages/docs/registered-affiliations.mdx @@ -20,9 +20,4 @@ When WATcloud first opened up access to non-WATonomous groups, we asked group le To address these challenges, we created a new system for managing access to WATcloud services, which we call "Registered Affiliations." The system provides access to and trains a few members from each group to manage WATcloud services for their group. They become the point of contact for their members and have visibility into the provisioning process. This new approach allows us to scale up the number of groups with minimal overhead. -{ -// Separate footnotes from the main content -} -import { Separator } from "@/components/ui/separator" - diff --git a/pages/docs/services.mdx b/pages/docs/services.mdx index 7a49a18..c199ba2 100644 --- a/pages/docs/services.mdx +++ b/pages/docs/services.mdx @@ -51,9 +51,3 @@ export function ServiceDescriptions() { -{ -// Separate footnotes from the main content -} -import { Separator } from "@/components/ui/separator" - - \ No newline at end of file diff --git a/pages/docs/utilities/assets.mdx b/pages/docs/utilities/assets.mdx index fcfbe62..fe1174c 100644 --- a/pages/docs/utilities/assets.mdx +++ b/pages/docs/utilities/assets.mdx @@ -24,10 +24,4 @@ The uploader is a tool for uploading assets. -{ -// Separate footnotes from the main content -} -import { Separator } from "@/components/ui/separator" - - diff --git a/pages/docs/utilities/onboarding-form.mdx b/pages/docs/utilities/onboarding-form.mdx index c624bbf..0df99fb 100644 --- a/pages/docs/utilities/onboarding-form.mdx +++ b/pages/docs/utilities/onboarding-form.mdx @@ -16,9 +16,4 @@ import OnboardingForm from '@/components/onboarding-form'; -{ -// Separate footnotes from the main content -} -import { Separator } from "@/components/ui/separator" - diff --git a/pages/get-involved/join.mdx b/pages/get-involved/join.mdx index 77a873f..eabdf8d 100644 --- a/pages/get-involved/join.mdx +++ b/pages/get-involved/join.mdx @@ -199,9 +199,4 @@ At WATcloud, we use [Ansible](https://www.ansible.com/) for provisioning machine [^ansible-user-linear]: Ansible issues a separate command for each action for each user. Even with the [pipelining](https://docs.ansible.com/ansible/latest/reference_appendices/config.html#ansible-pipelining) feature, the provisioning pipeline is unbearably slow. -{ -// Separate footnotes from the main content -} -import { Separator } from "@/components/ui/separator" - diff --git a/pages/get-involved/sponsor.mdx b/pages/get-involved/sponsor.mdx index 9190c53..f0c2cde 100644 --- a/pages/get-involved/sponsor.mdx +++ b/pages/get-involved/sponsor.mdx @@ -43,9 +43,3 @@ We would like to thank the following organizations and individuals for their gen [^wato-funding]: Almost all of WATcloud's funding is obtained as a part of WATonomous's funding efforts. -{ -// Separate footnotes from the main content -} -import { Separator } from "@/components/ui/separator" - - \ No newline at end of file diff --git a/styles/global.css b/styles/global.css index 8576adb..67846f1 100644 --- a/styles/global.css +++ b/styles/global.css @@ -132,3 +132,12 @@ li > ul.first\:nx-mt-0:first-of-type, li > ol.first\:nx-mt-0:first-of-type { margin-top: 0; } + +/* +section.footnotes is created by the remark-gfm plugin: +- https: //github.com/remarkjs/remark-gfm/blob/d8e110edf0799741e0954a92dd22fc143b803bdb/readme.md +- https://github.com/micromark/micromark-extension-gfm-footnote/blob/533e041238c15e7995afbffa7721b0e8d427f68e/readme.md +*/ +section.footnotes { + @apply border-t mt-6; +} \ No newline at end of file