This is a submission for Weekend Challenge: Passion Edition
📌 TL;DR
I found this challenge on the very last day, so I knew I probably wouldn't f...
For further actions, you may consider blocking this person and/or reporting abuse
Congratulations on the launch, @hemapriya_kanagala 🎉
What you’ve managed to build in such a tight timeframe is incredibly inspiring. Turning your weekly editions into a centralized, searchable hub is a massive value-add for the community👏
Looking forward to Edition #8 this Friday🙌
Thank you so much, Omar! That really means a lot 😀
One of the biggest reasons I wanted to build the website was exactly that, to make it much easier for people to rediscover opportunities from previous editions instead of searching through multiple posts. I'm really glad that came across.
And thank you for following the series! Looking forward to sharing Edition #8 with everyone this Friday.
The way you wrote "even if this submission isn't eligible, I'm genuinely grateful" . That's a rough place to build from, finding out on the last day. But you still gave Dev Opportunity Radar a real home instead of letting it wait another few weeks and that's yours regardless of what the judges do with it. Edition #8 this Friday, see you there 💙
Thank you so much, Daniel! That really means a lot 🧡
I won't lie, I was disappointed when I realized I'd found the challenge so late, but looking back I'm actually glad it happened because it finally pushed me to build something I'd been putting off for weeks.
No matter what happens with the challenge, I'm just happy I finally built the website and that it can keep growing alongside the series.
And yes, see you this Friday for Edition #8 😀
👊👊
Congratulations on the launch of Dev Opportunity Radar! 🎉 It's amazing that you built it in such a short time. I hope it will be used by even more people!
Nice work shipping a real home for the series instead of letting it wait another few weeks. A few
pointers from one builder to another if you keep iterating:
"Thanks so much for the detailed feedback and the encouraging words! I really appreciate you taking the time to review the setup. Your pointers on exporting the project from AI Studio to a stable host and tightening the CSP make total sense to avoid long-term risks. I'll definitely look into integrating a static analyzer like SonarCloud or Bandit for future releases too. Thanks for helping make Edition #8 better! 💙"
Cómo corregir la CSP (unsafe-eval y unsafe-inline)El problema principal es que unsafe-inline permite ejecutar cualquier script escrito directamente en el HTML, y unsafe-eval permite crear código desde texto (lo que abre la puerta a inyecciones XSS). Para solucionarlo de forma rápida:Elimina las directivas arriesgadas: Modifica tu configuración de Content Security Policy (CSP) retirando 'unsafe-inline' y 'unsafe-eval' de la sección script-src.Usa Hashes o Nonces: Si necesitas ejecutar algún script en línea imprescindible, añade un hash criptográfico (como sha256-ValorBase64...) o un atributo nonce aleatorio generado por sesión en la etiqueta del script, declarándolo explícitamente en tu CSP.Formato en Meta Tag (Frontend): Si manejas la CSP desde tu HTML estático, el formato corregido debería lucir similar a esto:html
Usa el código con precaución.Formato en Servidor (Recomendado): Lo ideal es inyectarlo directamente como una cabecera HTTP de respuesta desde tu proveedor de alojamiento:httpContent-Security-Policy: default-src 'self'; script-src 'self';
Usa el código con precaución.
Recomendaciones de hospedaje gratuito y establePara migrar tu proyecto fuera de la infraestructura temporal de Google AI Studio y asegurar que el archivo sobreviva a largo plazo, estas opciones son las más fiables, gratuitas y fáciles de integrar con un repositorio de GitHub:Vercel: Excelente si estás utilizando frameworks modernos de frontend (como Vite o Next.js). Ofrece despliegues automáticos al hacer push a tu rama principal, HTTPS nativo y configuraciones de seguridad muy sencillas.Netlify: Una alternativa fantástica a Vercel para proyectos estáticos o aplicaciones web estructuradas en JavaScript. Permite inyectar cabeceras personalizadas de CSP muy fácilmente mediante un archivo netlify.toml.GitHub Pages: Si tu sitio es puramente HTML, CSS y JavaScript estático, alojarlo directamente en el mismo repositorio de GitHub del proyecto comunitario es la opción más transparente para que otros puedan auditar el código fuente y colaborar.
Y en modo oscuro es muy recomendable, porque yo por ejemplo solo me gusta el modo oscuro...para evitar tanto brillo y tanta exposicion a la luz azul. Gracias y felicidades nuevamente. Aloha :)
Thank you so much, Fenix!
I really appreciate you taking the time to explore the website and write such a detailed review. Feedback like this is incredibly helpful, especially since this is only the first version.
You've brought up several good points. I was already planning to move it to its own GitHub repository, and your suggestions around hosting and security have given me a few more things to look into as I continue improving the project.
And thank you for mentioning dark mode too! I was actually working on it today. If I manage to finish it soon, I'll come back and leave another comment under this thread to let you know.
Thanks again for all the thoughtful suggestions and encouragement. It really means a lot. Aloha 😀
:D
I'd love your feedback on the website 💙
Whether it's something you liked, something that felt confusing, or a feature you think would make it more useful, please let me know. This is only the first version, and I'd love to keep improving it with the community's suggestions.
Thanks again for taking the time to check it out!
Amazing! Congratulations! Looking forward to the next edition.