Update src/index.qmd

src/index.qmd

@@ -66,7 +66,7 @@ Also, an important insight was observed:
 
 The following PRs represent different dimensions of software engineering: DevOps, API design, documentation enhancement and developer tooling:
 
-1. [Add Optuna + Transformers Integration Example (huggingface/cookbook)](https://github.com/huggingface/cookbook/pull/304)
+1. [Add Optuna + Transformers Integration Example (huggingface/cookbook)](https://github.com/huggingface/cookbook/pull/304){target="_blank"}
 
 **Challenge:** Demonstrating hyperparameter optimization for transformer models with evaluation, observability and storage of trials.
 
@@ -77,7 +77,7 @@ The following PRs represent different dimensions of software engineering: DevOps
 
 **Outcome:** Enabled practitioners to optimize model training 3-5x faster using Auto ML search strategies.
 
-2. [Modernize Python Tooling with pyproject.toml (skorch-dev/skorch)](https://github.com/skorch-dev/skorch/pull/1108)
+2. [Modernize Python Tooling with pyproject.toml (skorch-dev/skorch)](https://github.com/skorch-dev/skorch/pull/1108){target="_blank"}
 
 **Challenge:** Skorch relied on legacy packaging (`setup.py`, `requirements.txt`, `.pylintrc`, `.coveragerc`, `MANIFEST.in`) causing maintenance burden and incompatibility with modern Python tooling.
 
@@ -88,7 +88,7 @@ The following PRs represent different dimensions of software engineering: DevOps
 
 **Outcome:** Simplified maintenance, improved `CI/CD` reliability, aligned with `Python ecosystem standards`.
 
-3. [Reduce CI Flakiness by Configuring HF Token and Caching (PrunaAI/pruna)](https://github.com/PrunaAI/pruna/pull/406)
+3. [Reduce CI Flakiness by Configuring HF Token and Caching (PrunaAI/pruna)](https://github.com/PrunaAI/pruna/pull/406){target="_blank"}
 
 **Challenge:** CI test runs failed due to Hugging Face API rate limits and memory-intensive dataset downloads causing non-deterministic test failures.
 
@@ -99,18 +99,18 @@ The following PRs represent different dimensions of software engineering: DevOps
 
 **Outcome:** Reduced `CI` flakiness from frequent failures to stable test runs, unblocking maintainers and improving development velocity.
 
-4.  [Add Interactive Demo Link to Fast LoRA Inference Blog Post (huggingface/blog)](https://github.com/huggingface/blog/pull/3044)
+4.  [Add Interactive Demo Link to Fast LoRA Inference Blog Post (huggingface/blog)](https://github.com/huggingface/blog/pull/3044){target="_blank"}
 
 **Challenge:** The LoRA inference optimization blog post lacked an interactive component, limiting reader ability to experiment with the concepts.
 
 **Technical Approach:**
 
-- Created an interactive [Replicate](https://replicate.com/paragekbote/flux-fast-lora-hotswap) deployment showcasing PEFT +BnB+ Diffusers integration with LoRA hotswapping.
+- Created an interactive [Replicate](https://replicate.com/paragekbote/flux-fast-lora-hotswap){target="_blank"} deployment showcasing PEFT +BnB+ Diffusers integration with LoRA hotswapping.
 - Embedded the demo link directly in blog post for immediate experimentation and usage.
 
 **Outcome:** Readers can now test `LoRA inference optimizations` interactively, transforming passive reading into active learning. Interactive demos reduce the gap between reading and understanding by 5x.
 
-5. [Extend callback_on_step_end Support for AuraFlow and LuminaText2Img Pipelines (huggingface/diffusers)](https://github.com/huggingface/diffusers/pull/10746)
+5. [Extend callback_on_step_end Support for AuraFlow and LuminaText2Img Pipelines (huggingface/diffusers)](https://github.com/huggingface/diffusers/pull/10746){target="_blank"}
 
 **Challenge:** `AuraFlow` and `LuminaText2Img` pipelines lacked callback support present in other diffusion pipelines, breaking consistency for users.
 
@@ -133,9 +133,9 @@ Note that if you propose breaking changes that affect the public API without dis
 
 2. **Use Programming Language Standards to Improve your Contributions**
 
-There are standards for every major programming language such as the **[PEP Index](https://peps.python.org/) for Python, [Go Programming Language Specification](https://go.dev/ref/spec) for Golang or the [RFC Series](https://www.rfc-editor.org/) for building public APIs**. Try to reference them in your GitHub issues, use methods from them in your PRs and since these standards are widely accepted and adopted by programmers, your contributions are more likely to be accepted sooner. 
+There are standards for every major programming language such as the **[PEP Index](https://peps.python.org/){target="_blank"} for Python, [Go Programming Language Specification](https://go.dev/ref/spec){target="_blank"} for Golang or the [RFC Series](https://www.rfc-editor.org/) for building public APIs**. Try to reference them in your GitHub issues, use methods from them in your PRs and since these standards are widely accepted and adopted by programmers, your contributions are more likely to be accepted sooner. 
 
-Examples can be seen in this [**PR**](https://github.com/skorch-dev/skorch/pull/1108) and this [**issue**](https://github.com/PrunaAI/pruna/issues/225).
+Examples can be seen in this [**PR**](https://github.com/skorch-dev/skorch/pull/1108){target="_blank"} and this [**issue**](https://github.com/PrunaAI/pruna/issues/225){target="_blank"}.
 
 3. **Treat the CI Green Light as Non-Negotiable Before Merging**
 
@@ -179,4 +179,4 @@ If I could summarize this case-study into one actionable insight:
 
 **Small and frequent contributions which are well tested to a focused set of projects compound faster than large, sporadic contributions to many projects.**
 
-The [scripts](https://github.com/ParagEkbote/ParagEkbote.github.io/tree/main/scripts) used for data collection are available for reference and PR links are also included.
+The [scripts](https://github.com/ParagEkbote/ParagEkbote.github.io/tree/main/scripts){target="_blank"} used for data collection are available for reference and PR links are also included.