DEV Community

Cover image for I Finally Built the Dev Opportunity Radar Website ❀️

I Finally Built the Dev Opportunity Radar Website ❀️

Hemapriya Kanagala on July 13, 2026

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...
Collapse
 
shubhradev profile image
Shubhra Pokhariya

I smiled when I reached the part where you said most of your time went into making decisions rather than adding features. That part stood out to me because it's usually those small decisions that shape how a project feels to use.

While exploring the website, it felt calm and easy to navigate, and I really liked that. Looking forward to seeing how this grows every Friday.

Collapse
 
hemapriya_kanagala profile image
Hemapriya Kanagala

Thank you so much, Shubhra πŸ’™

That honestly means a lot because that's exactly the experience I was hoping to create.

It's easy to focus on adding more features, but I found myself spending much more time thinking about how everything should feel to use. I'm really happy to hear the website felt calm and easy to navigate.

Thank you for taking the time to explore it and share your thoughts. I hope you'll enjoy watching it grow alongside the weekly editions πŸ˜€

Collapse
 
omarafifi profile image
Omar Afifi

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πŸ™Œ

Collapse
 
hemapriya_kanagala profile image
Hemapriya Kanagala

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.

Collapse
 
javz profile image
Julien Avezou

Amazing! Congratulations! Looking forward to the next edition.

Collapse
 
hemapriya_kanagala profile image
Hemapriya Kanagala • Edited

Thank you so much, Julien πŸ˜€

It really means a lot, especially because you've been supporting Dev Opportunity Radar since the very beginning. You were one of the first people to encourage the project, and I'm really grateful for that.

Looking forward to sharing Edition #8 with you this Friday!

Collapse
 
klaudiagrz profile image
Klaudia Grzondziel

Hi, Hema! First of all, I am very very proud of you and your journey πŸ’› I remember the first Dev Opportunity Radar article you wrote, and I already knew this was the idea coming from a person who deeply cares about the community and wants to share her findings. Since then, I cheered for your series, so seeing you give it a home feels like a personal win! πŸ˜„ I'm super happy for you! πŸ’›

I browsed the website, and I love it! It is visible that you put a lot of heart into it. I always appreciate it when software engineers care about UX, and it's visible that you do care and spent extra time on it. I especially like the possibility to filter the opportunities. One small thing that I noticed is that in Learning Resources, the first opportunities that appear are the closed ones. Maybe it's worth considering dropping the closed opportunities down the list πŸ€”

Good luck with the challenge, Hema! I think you totally nailed it! πŸ’ͺ🏻

PS: I also see DEV challenges as a great source of motivation and a push to follow ideas that anyway were somewhere there in my mind. I think it's even more valuable than any prizes πŸ’›

Collapse
 
hemapriya_kanagala profile image
Hemapriya Kanagala

Hi Klaudia πŸ˜„ Just a small update.

I finally got around to implementing your suggestion on the website. Open opportunities are now displayed first, with closed ones moved further down the list, so it's much easier to browse what's currently available.

Thanks again for pointing that out in the first place. It was a really helpful piece of feedback, and I appreciate you taking the time to share it πŸ’›

Collapse
 
klaudiagrz profile image
Klaudia Grzondziel

Yay, happy to hear that you keep improving the website! Also happy that you found my small suggestion useful. Keep doing your job πŸ’›

Collapse
 
hemapriya_kanagala profile image
Hemapriya Kanagala

Klaudia, thank you so much πŸ’™

Reading this genuinely made me smile. It means a lot coming from someone who's been here since the very first edition. You've always been so supportive of the series, so hearing that the website feels like a personal win for you really means more than I can put into words.

Thank you as well for taking the time to explore the website and for the thoughtful feedback. That's a really good point about the Learning Resources section. I think it makes much more sense to show the active opportunities first and move the closed ones further down the list, so I'll work on improving that.

And I completely agree with your PS. Looking back, I think the biggest thing this challenge gave me wasn't the possibility of winning a prize. It was the push to finally build something I'd been saying "I'll start next week" for far too long. For that alone, I'm really grateful.

Thank you again for always cheering me on and for all your encouragement from the very beginning. It truly means a lot πŸ’™

Collapse
 
buildbasekit profile image
buildbasekit

This is a great example of solving a problem that grows with consistency. Weekly posts are valuable, but having a searchable home for everything makes the project much more useful over time. Also loved your point that most of the work was making decisions, not writing code. That's something every builder realizes sooner or later. Looking forward to seeing how Dev Opportunity Radar evolves!

Collapse
 
hemapriya_kanagala profile image
Hemapriya Kanagala

Thank you so much!

You're absolutely right. After a few editions, I started realizing that while the weekly posts were helpful, it was becoming harder for people to go back and find something they'd seen before. That's really what led me to build the website.

And I completely agree about the decisions. Looking back, I think I spent far more time thinking about the experience than actually building it, but I also think that's what made the project so enjoyable.

Thanks again for the thoughtful comment, and I hope the website continues to grow into something that's genuinely useful for the community πŸ˜€

Collapse
 
magopredator profile image
Fenix

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:

- The site is currently a Google AI Studio prototype on a *.ai.studio domain. That subdomain is
Google's, not yours, so it can disappear if they retire the project β€” consider exporting it and hosting
it on your own repo + a stable host so the archive survives long-term.
- The deployed page sends script-src 'self' 'unsafe-inline' 'unsafe-eval'. The unsafe-eval +
unsafe-inline combo is risky: if any curated content ever gets a script injected, the browser will
happily run it. Tightening that CSP (drop unsafe-eval, use hashes/nonces) is a quick, high-value
hardening step.
- I didn't see a public repo linked. For a community project it helps a lot to publish the source so
others can audit what the AI generated and contribute fixes.

On that last point: it's worth running the code through a static analyzer before each release. Free
options like SonarCloud (quality + security gates) or Bandit (for Python) catch whole classes of issues
automatically. Tools like Repomapper can also scan a repo for weaknesses. None of it replaces review, but
it catches the boring stuff fast. Keep going β€” Edition #8 πŸ’™
Enter fullscreen mode Exit fullscreen mode

"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! πŸ’™"

  1. 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.

  2. 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.

Collapse
 
magopredator profile image
Fenix

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 :)

Collapse
 
hemapriya_kanagala profile image
Hemapriya Kanagala

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 πŸ˜€

Thread Thread
 
magopredator profile image
Fenix

:D

Thread Thread
 
hemapriya_kanagala profile image
Hemapriya Kanagala

Hi again, Fenix! As promised, I'm back with an update.

I've now added a dark mode to the website, so you can switch between light and dark themes depending on your preference.

Thanks again for suggesting it. Your comment gave me the extra push to finish it sooner. I hope you enjoy using it, and if you notice anything that could be improved, I'd love to hear your thoughts.

Aloha πŸ˜€

Thread Thread
 
magopredator profile image
Fenix • Edited

Te ha quedado perfecto, tienes una web perfectamente funcional para continuar con la divulgacion de oportunidades para desarrolladores, es un escalon mas en ese tema que te simplifica el trabajo en el futuro, y ofrece una exploracion mas fluida a los usuarios, te ha quedado perfecta. Felicidades, y gracias nuevamente.

Aloha Hema :)

Collapse
 
dannwaneri profile image
Daniel Nwaneri

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 πŸ’™

Collapse
 
hemapriya_kanagala profile image
Hemapriya Kanagala

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 πŸ˜€

Collapse
 
dannwaneri profile image
Daniel Nwaneri

πŸ‘ŠπŸ‘Š

Collapse
 
anhmtk profile image
anhmtk

Huge congratulations on launching the website, Hemapriya! πŸ’™

"A lot of my time wasn't spent adding features. It was spent making decisions" β€” this hits so close to home. The challenge isn't the code anymore; it's the architecture of information.

Moving your weekly radar from disconnected articles into a structured, central home at devopportunityradar.ai.studio is a massive upgrade for your readers. You aren't just making it easier for humans to browse; by structuring the archive by categories, you are essentially making these valuable developer opportunities machine-readable and discoverable for the future web too!

Kudos to you for leveraging AI Studio to beat procrastination and deliver real utility to the community. Can't wait for Edition #8 this Friday!

Collapse
 
hemapriya_kanagala profile image
Hemapriya Kanagala

Thank you so much πŸ’™

I'm really glad that line resonated with you because that's honestly how this project felt. The code was only one part of it. Most of the time went into thinking about how everything should be organized so people could actually find what they were looking for without feeling overwhelmed.

I'm also really happy I finally stopped putting it off and built it. I think it'll make the series much easier to explore as more editions are published.

Thank you again for taking the time to read the post and leave such a thoughtful comment.

And yes, see you this Friday for Edition #8 πŸ˜€

Collapse
 
webdeveloperhyper profile image
Web Developer Hyper

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!

Collapse
 
hemapriya_kanagala profile image
Hemapriya Kanagala

Thank you so much! That really means a lot, especially because you've been supporting Dev Opportunity Radar since the very beginning.

I'm really happy I finally built the website, and I hope it makes discovering opportunities even easier as the series continues to grow.

I'm so grateful you've been part of this journey from the start πŸ˜€

Collapse
 
hemapriya_kanagala profile image
Hemapriya Kanagala • Edited

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 πŸ˜€

Collapse
 
glnurltn profile image
gulnur

Wow, you've made such a useful tool πŸ™‚ I'll definitely check it out.

Collapse
 
hemapriya_kanagala profile image
Hemapriya Kanagala

Thank you so much, Gulnur!

I really hope you find it useful. If you get a chance to explore it, I'd genuinely love to hear any feedback or ideas you have. I'll keep improving it over time, so every suggestion really helps πŸ˜€

Thanks again for taking the time to check it out!

Collapse
 
ammaraaamer profile image
ammara aamer • Edited

Huge congratulations on launching the Dev Opportunity Radar! Building a platform entirely from scratch is a tough journey. Balancing the database architecture with the frontend designing phase requires a lot of patience, and you pulled it off beautifully. Tools like this are exactly what our community needs to navigate the job market right now.

One thing I have learned from building custom tools is that the learning cycle never stops. Every time you refine a feature, you inevitably discover a cleaner way to write your code. For anyone feeling inspired by this launch and looking to build their own platforms, staying updated with modern standards is key. Learning the best web development practices by following the technical resources that experienced professionals read daily makes a massive difference in how easily your projects scale.

Collapse
 
hemapriya_kanagala profile image
Hemapriya Kanagala

Thank you so much, Ammara!

You're absolutely right that the learning never really stops. Even while building this first version, I kept finding better ways to organize things and improve the experience. I'm sure I'll look back a few months from now and think of even more improvements, and honestly, I think that's part of the fun of building.

Thank you again for taking the time to share your thoughts. I really appreciate it, and I'm excited to keep improving Dev Opportunity Radar over time!

Collapse
 
akash_yadav_03c587d791345 profile image
akash yadav

**Congratulations on launching your project! Building and publishing a website is a significant milestone, especially when you've taken it from an idea to a live product.

One thing I'd recommend now is focusing on visibility, because even a great website won't attract users if people can't find it. Here are a few next steps:

  • Optimize your pages for SEO by using descriptive titles, meta descriptions, and relevant keywords.
  • Ensure the site loads quickly and works well on mobile devices.
  • Submit your sitemap to Google Search Console and monitor indexing.
  • Share the project on developer communities, social media, GitHub, Reddit, and Product Hunt to gather feedback.
  • Regularly publish useful content or updates to keep the site active and improve search rankings.

If you're looking for professional help with growing your website's online presence, agencies like Aqva Marketing offer services such as SEO, content marketing, and online reputation management that can help increase organic traffic and improve brand visibility. Whether you handle marketing yourself or work with an agency, consistently improving content and user experience is key to long-term success.

Best of luck with your Dev Opportunity Radar websiteβ€”I hope it continues to grow and attract the developer community you're targeting!
**

Collapse
 
hemapriya_kanagala profile image
Hemapriya Kanagala

Thank you so much, Akash!

I really appreciate you taking the time to write such detailed suggestions.

Those are all great points, especially around SEO, performance, and making the website easier for people to discover. Since this is only the first version, there's still a lot I'd like to improve, and those are definitely areas I'll be spending more time on.

Collapse
 
hightech89 profile image
Josh Cox

Great job! cannot wait to check this out!

Collapse
 
hemapriya_kanagala profile image
Hemapriya Kanagala

Thank you so much, Josh!

I hope you enjoy exploring it! And if you have any feedback or ideas after you've had a chance to look around, I'd genuinely love to hear them. I'm always looking for ways to make the website even better.

Thanks again for the encouragement πŸ˜€

Collapse
 
hoseinmdev profile image
Hosein Mahmoudi

This is Great project thanks :)))😍

Collapse
 
hemapriya_kanagala profile image
Hemapriya Kanagala

Thank you so much, Hosein!

Collapse
 
phoenix_2011 profile image
Hima Kartikeya Naidu Ch

Congratulations akka! I hope this would help many people around... Good work! πŸ‘πŸ™πŸ™Œ I wish you would also come up with more enhancements & upgrades! ❀️

Collapse
 
hemapriya_kanagala profile image
Hemapriya Kanagala

Thank you so much, Kartikeya! That really means a lot.

And yes, this is only the beginning. I already have a lot of ideas for improving the website, and I'll keep adding features that genuinely make it more useful for everyone over time.

Thank you again for your kind words and encouragement πŸ˜€

Collapse
 
technogamerz profile image
π“π‘πž π‹πšπ³π² 𝐆𝐒𝐫π₯

Congratulations Hema ❀️🎊

Collapse
 
hemapriya_kanagala profile image
Hemapriya Kanagala

Thank you so much, Divyanshi πŸ’™

Collapse
 
mbendjeddou1 profile image
Mohamed Bendjeddou

Neatly beautiful, simply inspiring. Congratulations on the great work (both the Radar and its new home).

I'm new here, and as a beginner web dev, a good reason I came is to find opportunities for real practice and exposure, after I did quite a lot of theory and only some toy exercises. And I think I found something valuable in addition to the finds and opportunities: the website and repository serve as a great resource for that real practice I was looking for, particularly as the project has just launched, and I can tell you I've already learned quite a bit from those commit messages...

It also struck me how the central focus was the content, language, and user experience. From my humble theoretical knowledge (from the whole discipline called content design), putting the user first is one of the most important features of successful apps and websites. I do look forward to seeing this one evolve.

Last note: I explored the comments and exchanges here as well, and I got to see what it's like to take part in such welcoming and supportive community, with all the encouragement and constructive feedback. And if nothing else, that simple thank-you is never out of style.

Collapse
 
hemapriya_kanagala profile image
Hemapriya Kanagala

Thank you so much, Mohamed!

It means a lot to hear that you found value not only in the opportunities but also in the website, the repository, and even the commit history. I never imagined someone might learn from those too, so that was a lovely surprise to read.

I'm also really happy you noticed the focus on the content and user experience. I spent a lot of time thinking about how someone new would experience the website because I wanted it to feel simple, welcoming, and respectful of people's time.

And thank you for your kind words about the community as well. One of my favorite parts of this series has been seeing people encourage one another, share opportunities, and offer thoughtful feedback. I hope that continues as the project grows.

Wishing you all the best on your web development journey, and I hope Dev Opportunity Radar helps you discover some exciting opportunities along the way. Welcome to the community πŸ˜€

Collapse
 
thenameisdevair profile image
Devair

Good build really.
would love to add, that the font-size is reallly small, found it hard to read, even after increasing my screen brightness

Collapse
 
hemapriya_kanagala profile image
Hemapriya Kanagala

Thank you so much, Devair! I really appreciate you taking the time to try the website and share that feedback.

That's definitely something I want to improve. If you're comfortable sharing, was it across the entire website or were there specific pages or sections where the text felt too small? That would really help me know where to start and make sure I fix the right areas.

Thanks again for pointing it out. Feedback like this really helps improve the experience for everyone πŸ˜€

Collapse
 
thenameisdevair profile image
Devair

So persoanally, i feel like its pretty much across the whole site. Currently the site looks like its centralized(when viewed with a labtop), so if it fills the screen instead, then, it will be bolder and better.

Thread Thread
 
hemapriya_kanagala profile image
Hemapriya Kanagala

Thanks for letting me know, Devair!

That helps a lot. I can see what you mean about the layout feeling a bit too centralized on larger screens. I'll take another look at both the layout and the typography to make the content more comfortable to read.

I really appreciate you taking the time to explain it. Thanks again for the helpful feedback!