storybooker.js.org

[GuptaSiddhant]

• There is reasonable content on the page (see: No Content)
• I have read and accepted the Terms and Conditions
• The site content can be seen at guptasiddhant.github.io/storybooker

The site content is documentation for a tool to host/manage StoryBooks using own infra/cloud. The tool is called StoryBooker.

[GuptaSiddhant]

Hi @indus , for some reason the CI check is failing for a non-associated domain entry. Could you help me fix this?

[indus]

@GuptaSiddhant

it looks like your PR is changing "sticksy": "kovart.github.io/sticksy", to "sticksy": "kovart.r.io/sticksy",. You just have to revert that change to make the CI check work...

[indus]

@GuptaSiddhant I've just seen you are currently using guptasiddhant.com would you dismiss that with a js.org domain - or what is you plan on this?

[GuptaSiddhant]

@indus , sorry for the rookie mistake. I fixed it.
As for guptasiddhant.com, it should not matter. I previously did the same with https://react-table-ui.js.org and that worked well.

[indus]

@indus , sorry for the rookie mistake. I fixed it.

No problem. I've just added your requested subdomain to JS.ORGs zonefile. But because you are using a workflow to deploy the page, additional steps may be required to make the CNAME work.
FYI: #7853 (comment) / #8532 (comment)

As for guptasiddhant.com, it should not matter. I previously did the same with https://react-table-ui.js.org and that worked well.

As long as the js.org subdomain is in active use, presenting the content and not just redirecting to your domain, thats fine. A automatic redirect would raise questions in our yearly cleanup process as it would violate our "reasonable content" requirement.

[GuptaSiddhant]

@indus, the workaround worked: https://storybooker.js.org. And removed guptasiddhant.com from custom domain in GitHub.

[indus]

Welcome https://storybooker.js.org