Add references (#115)

* update link style to be more prominent

* add references

_blogs/docker-nginx-reverse-proxy-local-dev.md

@@ -250,3 +250,14 @@ This request should return the response from one of the backend services. Since
 By combining Docker and NGINX, you can efficiently replicate a complex backend environment for local development. Docker Compose simplifies managing multi-service setups, while NGINX handles traffic routing and load balancing across services. This architecture not only mirrors production environments but also streamlines testing and scaling.
 
 Whether you’re developing microservices or handling a monolithic backend, this approach provides flexibility and scalability. By following these steps, you can create a local environment that closely resembles your production setup, improving both your workflow and your deployment pipeline.
+
+---
+
+## References
+
+- [Docker](https://www.docker.com/)
+- [Docker Docs](https://docs.docker.com/)
+- [Docker Compose](https://docs.docker.com/compose/)
+- [NGINX](https://www.nginx.com/)
+- [NGINX Docs](https://docs.nginx.com/)
+- [NGINX Docker Image](https://hub.docker.com/_/nginx/)

_blogs/github-codeowners.md

@@ -230,3 +230,6 @@ The `CODEOWNERS` file is an essential tool for managing large projects with mult
 By setting up a well-structured `CODEOWNERS` file, you’ll ensure that your repository scales effectively while maintaining high code quality.
 
 ---
+
+## References
+- [Official Documentation](https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners)

src/styles/markdown-styles.module.css

@@ -26,7 +26,7 @@
 }
 
 .markdown a {
-  color: text-blue-400;
+  color: #0070f3;
   display: inline-block;
   position: relative;
   font-weight: bold;
@@ -39,7 +39,7 @@
   bottom: 0;
   width: 0;
   height: 1px;
-  background-color: rgb(0, 0, 0);
+  background-color: #0070f3;
   transform: translateX(-50%);
   transition: width 1s;
 }