Add link to Seqera products in recent blog posts

src/content/blog/2023/community-forum.md

@@ -27,7 +27,7 @@ The community forum offers many exciting new features. Here are some of the thin
 - **Don’t ask the same thing twice:** It’s not always easy to find answers when there’s a lot of content available. The community forum helps you by suggesting similar topics as you write a new post. An upcoming [Discourse AI Bot](https://www.discourse.org/plugins/ai.html) may even allow you to ask questions using natural language in the future!
 - **Stay afloat:** The community forum will ensure developers have a space where they can post without fear that what they write might be drowned out, and where anything that our community finds useful will rise to the top of the list. Discourse will give life to threads with high-quality content that may have otherwise gone unnoticed and lost in a sea of new posts.
 - **Better organized:** The forum model for categories, tags, threads, and quoting forces conversations to be structured. Many questions involve the broader Nextflow ecosystem, tagging with multiple topics will cut through the noise and allow people to participate in targeted and well-labeled discussions. Importantly, maintainers can move miscategorized posts without asking the original author to delete and write again.
-- **Multi-product:** The forum has categories for Nextflow but also Seqera Platform, MultiQC, Wave, and Fusion. Questions that involve multiple Seqera products can now span these boundaries, and content can be shared between posts easily.
+- **Multi-product:** The forum has categories for Nextflow but also [Seqera Platform](https://seqera.io/platform/), [MultiQC](https://seqera.io/multiqc/), [Wave](https://seqera.io/wave/), and [Fusion](https://seqera.io/fusion/). Questions that involve multiple Seqera products can now span these boundaries, and content can be shared between posts easily.
 - **Community recognition:** The community forum will encourage a healthy ecosystem of developers that provides value to everyone involved and rewards the most active users. The new forum encourages positive community behaviors through features such as badges, a trust system, and community moderation. There’s even a [community leaderboard](https://community.seqera.io/leaderboard/)! We plan to gradually introduce additional features over time as adoption grows.
 
 Online discussion platforms have been the beating heart of the Nextflow community from its inception. The first was a Google groups email list, which was followed by the Gitter instant messaging platform, GitHub Discussions, and most recently, Slack. We’re thrilled to embark on this new chapter of the Nextflow community – let us know what you think and ask any questions you might have in the [“Site Feedback” forum category](https://community.seqera.io/c/community/site-feedback/2)! Join us today at [https://community.seqera.io](https://community.seqera.io/) for a new and improved developer experience.

src/content/blog/2024/nextflow-24.04-highlights.md

@@ -47,7 +47,7 @@ Check it out here: [Channels Episode 41](/podcast/2024/ep41_nextflow_2404.html).
 
 ### Seqera Containers
 
-A new flagship community offering was revealed at the Nextflow Summit 2024 Boston - **Seqera Containers**. This is a free-to-use container cache powered by Wave, allowing anyone to request an image with a combination of packages from Conda and PyPI. The image will be built on demand and cached (for at least 5 years after creation). There is a [dedicated blog post](https://seqera.io/blog/introducing-seqera-pipelines-containers/) about this, but it's worth noting that the service can be used directly from Nextflow and not only through [https://seqera.io/containers/](https://seqera.io/containers/)
+A new flagship community offering was revealed at the Nextflow Summit 2024 Boston - **Seqera Containers**. This is a free-to-use container cache powered by [Wave](https://seqera.io/wave/), allowing anyone to request an image with a combination of packages from Conda and PyPI. The image will be built on demand and cached (for at least 5 years after creation). There is a [dedicated blog post](https://seqera.io/blog/introducing-seqera-pipelines-containers/) about this, but it's worth noting that the service can be used directly from Nextflow and not only through [https://seqera.io/containers/](https://seqera.io/containers/)
 
 In order to use Seqera Containers in Nextflow, simply set `wave.freeze` _without_ setting `wave.build.repository` - for example, by using the following config for your pipeline:
 
@@ -249,7 +249,7 @@ To better facilitate community contributions, the nf-ga4gh plugin will soon be m
 
 ## Fusion
 
-Fusion is a distributed virtual file system for cloud-native data pipeline and optimized for Nextflow workloads. Nextflow 24.04 now works with a new release, Fusion 2.3. This brings a few notable quality-of-life improvements:
+[Fusion](https://seqera.io/fusion/) is a distributed virtual file system for cloud-native data pipeline and optimized for Nextflow workloads. Nextflow 24.04 now works with a new release, Fusion 2.3. This brings a few notable quality-of-life improvements:
 
 ### Enhanced Garbage Collection
 

src/content/blog/2024/optimizing-nextflow-for-hpc-and-cloud-at-scale.md

@@ -21,7 +21,7 @@ In this article, we will help you understand how the Nextflow head job works and
 
 ### CPUs
 
-Nextflow uses a thread pool to run native Groovy code (e.g. channel operators, `exec` processes), submit tasks to executors, and publish output files. The number of threads is based on the number of available CPUs, so if you want to provide more compute power to the head job, simply allocate more CPUs and Nextflow will use them. In the Seqera Platform, you can use **Head Job CPUs** or **Head Job submit options** (depending on the compute environment) to allocate more CPUs.
+Nextflow uses a thread pool to run native Groovy code (e.g. channel operators, `exec` processes), submit tasks to executors, and publish output files. The number of threads is based on the number of available CPUs, so if you want to provide more compute power to the head job, simply allocate more CPUs and Nextflow will use them. In the [Seqera Platform](https://seqera.io/platform/), you can use **Head Job CPUs** or **Head Job submit options** (depending on the compute environment) to allocate more CPUs.
 
 ### Memory
 
@@ -98,7 +98,7 @@ Many users have encountered head job errors when running large-scale workloads,
 
 Singularity / Apptainer can download and convert Docker images on the fly, and it uses the head job’s local scratch storage to do so. This is a common pattern in HPC environments, since container images are usually published as Docker images but HPC environments usually require the use of a rootless container runtime like Singularity. In this case, make sure the head job has enough scratch storage to build each image, even if the image is eventually saved to shared storage.
 
-Since Nextflow version [23.10.0](https://github.com/nextflow-io/nextflow/releases/tag/v23.10.0), you can use Wave to build Singularity images for you. Refer to the [Nextflow documentation](https://nextflow.io/docs/latest/wave.html#build-singularity-native-images) for more details.
+Since Nextflow version [23.10.0](https://github.com/nextflow-io/nextflow/releases/tag/v23.10.0), you can use [Wave](https://seqera.io/wave/) to build Singularity images for you. Refer to the [Nextflow documentation](https://nextflow.io/docs/latest/wave.html#build-singularity-native-images) for more details.
 
 Additionally, Nextflow version [23.11.0-edge](https://github.com/nextflow-io/nextflow/releases/tag/v23.11.0-edge) introduced support for [Singularity OCI mode](https://docs.sylabs.io/guides/3.1/user-guide/oci_runtime.html), which allows Singularity / Apptainer to use the OCI container format (the same as Docker) instead of having to build and store a SIF container image locally.