From c1c9d193cd625b52be6b03c36fedd57aa4ab769a Mon Sep 17 00:00:00 2001 From: Alessio Cimarelli Date: Fri, 23 Jun 2023 15:24:57 +0200 Subject: [PATCH] 163 fix broken links (#172) * refs #163: sparkfabrik who we are is now the manifest page * refs #163: fix internal anchors * refs #163: fix udemy access info * refs #163: fix info for calendar importing * refs #163: fix link typos * refs #163: fix duplicated internal anchors * refs #163: fix footnote anchors * refs #163: update old links * refs #163: fix markdown mistakes Ie. from wrong `()[]` to correct `[]()` --------- Co-authored-by: Alessio Cimarelli --- content/guides/basic-testing-with-behat.md | 2 +- content/guides/drupal-errors-troubleshooting.md | 2 +- content/guides/local-development-environment-configuration.md | 2 +- content/guides/ubuntu-administration.md | 2 +- content/tools-and-policies/online-meetings-policy.md | 4 ++-- 5 files changed, 6 insertions(+), 6 deletions(-) diff --git a/content/guides/basic-testing-with-behat.md b/content/guides/basic-testing-with-behat.md index 04ef0d4..93f5097 100644 --- a/content/guides/basic-testing-with-behat.md +++ b/content/guides/basic-testing-with-behat.md @@ -142,7 +142,7 @@ bin/e bin/behat -dl http://www.slideshare.net/sparkfabrik/behaviour-driven-development-con-behat-drupal -https://behat-drupal-extension.readthedocs.io/en/3.1/ +https://behat-drupal-extension.readthedocs.io/en/v3.4.1/ ## Todo diff --git a/content/guides/drupal-errors-troubleshooting.md b/content/guides/drupal-errors-troubleshooting.md index b03b8ee..ae2956a 100644 --- a/content/guides/drupal-errors-troubleshooting.md +++ b/content/guides/drupal-errors-troubleshooting.md @@ -27,4 +27,4 @@ The following steps should be done before asking for help from one of your colle * The VarDumper Symfony component provides the great `dump()` inspection function: http://symfony.com/doc/current/components/var_dumper.html * XDebug extension for PHP allows for deep digging of your problems: https://xdebug.org/docs/ -In particular backtraces, functions provide you with the context/calls that led to the error: https://xdebug.org/docs/execution_trace \ No newline at end of file +In particular backtraces, functions provide you with the context/calls that led to the error: https://xdebug.org/docs/trace \ No newline at end of file diff --git a/content/guides/local-development-environment-configuration.md b/content/guides/local-development-environment-configuration.md index f94a17f..823df50 100644 --- a/content/guides/local-development-environment-configuration.md +++ b/content/guides/local-development-environment-configuration.md @@ -110,7 +110,7 @@ If you need to re-run `dnsdock` or `dinghy-http-proxy` for some reason (maybe yo 1. `run-dnsdock`: https://github.com/sparkfabrik/sparkdock/blob/master/config/ubuntu/bin/run-dnsdock 2. `run-dinghy-proxy`: https://github.com/sparkfabrik/sparkdock/blob/master/config/ubuntu/bin/run-dinghy-proxy 2. macOS - 3. `run-dinghy-proxy`: https://github.com/sparkfabrik/sparkdock/blob/master/config/macosx/bin/run-dinghy-proxy + 3. `run-dinghy-proxy`: https://github.com/sparkfabrik/sparkdock/blob/master/config/macos/bin/run-dinghy-proxy If you work in SparkFabrik with the provided hardware, those scripts should already be available in your system. In case they're missing: diff --git a/content/guides/ubuntu-administration.md b/content/guides/ubuntu-administration.md index 826610f..1adea39 100644 --- a/content/guides/ubuntu-administration.md +++ b/content/guides/ubuntu-administration.md @@ -6,7 +6,7 @@ on Linux and more specifically on our provisioned Ubuntu stack. > This piece assumes you are running Ubuntu >= 20.04 Once upon a time, it was quite impossible to upgrade the firmware on Linux, now the situation -gets a lot better thanks to the great (Linux Vendor Firmware Service - LVFS)[https://fwupd.org/] project, +gets a lot better thanks to the great [Linux Vendor Firmware Service - LVFS](https://fwupd.org/) project, which allows hardware vendors to upload firmware updates, freeing the users to use Windows just to upgrade their firmware. We mainly use Lenovo machines and guess what, they are fully supported. diff --git a/content/tools-and-policies/online-meetings-policy.md b/content/tools-and-policies/online-meetings-policy.md index 9e58445..b3a80aa 100644 --- a/content/tools-and-policies/online-meetings-policy.md +++ b/content/tools-and-policies/online-meetings-policy.md @@ -32,9 +32,9 @@ Some of the points come from this super cool post from the MIT Media Lab: https: 1. **Designate a facilitator**: We highly recommend having a facilitator who can keep an eye on group dynamics and guide the conversation. It can be the host or to make it simple, a shared role, rolling among the participants. 2. **The key to a good video call is the audio**: Nothing improves the quality of a video meeting as much as a headset and good audio etiquette. Make sure all participants use a headset or a good directional microphone and encourage participants to mute themselves when they are not speaking. If necessary this is one of the areas where it’s ok for the facilitator to get a little heavy-handed if necessary. Bad audio from one or two participants can ruin the meeting for everyone else. In addition, all participants should be in a quiet space when they connect. 3. **Raise your hand/use a speaker queue**: This may sound like we’re back in elementary school, but it’s amazing how well the conversation flows if all participants “raise their hand” to indicate they want to chime in. It’s the facilitator’s job to make sure that people are asked to speak in the order in which they added themselves to the queue. -4. **Use the calendar to set up a meeting**: Most of the tools nowadays allow you to create a meeting from within your calendar tool, you can see here the instructions for [Google Meet](https://support.google.com/meet/answer/9302870?co=GENIE.Platform%3DDesktop&hl=en) and (Zoom)[https://support.zoom.us/hc/en-us/articles/360020187492-Google-Calendar-add-on] +4. **Use the calendar to set up a meeting**: Most of the tools nowadays allow you to create a meeting from within your calendar tool, you can see here the instructions for [Google Meet](https://support.google.com/meet/answer/9302870?co=GENIE.Platform%3DDesktop&hl=en) and [Zoom](https://support.zoom.us/hc/en-us/articles/360020187492-Google-Calendar-add-on) 5. **Make sure you have enough bandwidth**: If you are experiencing connection issues or just using a low-quality connection, you can try to: - * Reduce the used bandwidth of your webcam: (Google Meet)[https://support.google.com/meet/answer/9302964?co=GENIE.Platform%3DDesktop&hl=en] and (Zoom)[https://wiki.millersville.edu/display/instructdocs/Improving+your+Zoom+connection] + * Reduce the used bandwidth of your webcam: [Google Meet](https://support.google.com/meet/answer/9302964?co=GENIE.Platform%3DDesktop&hl=en) and [Zoom](https://wiki.millersville.edu/display/instructdocs/Improving+your+Zoom+connection) * Disable the webcam and ask the other ones to do the same * Connect to the meeting using the landline phone number