pulse.js.org#11687
Conversation
|
✅ All validations passed! Please wait for the JS.org maintainers to process your subdomain request. |
|
@razinrayees this somehow looks AI coded and I wonder why the project has your username. Are you planning to switch to portfolio-like content (which we wouldn't allow otherwise)? |
This comment was marked as duplicate.
This comment was marked as duplicate.
There was a problem hiding this comment.
@indus
You're right that I initially chose my username because I thought I might use it more personally in the future. After reviewing the JS.ORG guidelines, I've decided against that approach.
I've since reworked the project, changed the branding to Pulse, and intend to keep it as a JavaScript focused developer resource site.
I also plan to continue developing the project, adding more features and expanding its functionality over time. My goal is to grow it into a more useful resource for developers and the JavaScript community.
If there are any remaining concerns about the project's scope or eligibility, I'd be happy to address them.
https://pulsejs.netlify.app/
Removed 'nova' entry and added 'pulse' entry in the cnames list.
|
I've already added your requested subdomain to JS.ORGs zonefile. You may have to configure your host to accept the custom domain. |
|
Thank you for the update. I've added the domain to Netlify and configured the custom domain there. At the moment, Netlify is showing the domain as "DNS configuration pending", which I believe is because the DNS changes have not fully propagated yet.
|
|
Looks like it is working now. Welcome https://pulse.js.org |
Uh oh!
There was an error while loading. Please reload this page.