Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

semantic-api.js.org #8410

Closed
wants to merge 1 commit into from
Closed

semantic-api.js.org #8410

wants to merge 1 commit into from

Conversation

minenwerfer
Copy link
Contributor

@MattIPv4 MattIPv4 changed the title Update cnames_active.js semantic-api.js.org Jul 29, 2023
Copy link
Member

@MattIPv4 MattIPv4 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi there!

❌ Before we can accept your js.org domain request, your site must have reasonable content.
Based on semantic-api.github.io/docs your site currently does not contain what we would consider to be reasonable content to grant a request.

Please see the wiki article: https://github.com/js-org/js.org/wiki/No-Content 📖

@MattIPv4 MattIPv4 added the no content This PR has a target that contains no valid content for a request label Jul 29, 2023
@indus indus closed this Jul 29, 2023
@minenwerfer
Copy link
Contributor Author

@MattIPv4 there's a whole API reference there. The page was refused because the index page doesn't lead to any content yet or because the documentation is in TypeScript?

I'm using Vitepress SSG, it's pretty common to have a index page like that. See Vite homepage for example. Would it be accepted?

@MattIPv4
Copy link
Member

I hadn't noticed that there was an API reference buried there -- the homepage had lorem ipsum content on it, and linked to a guide that was completely empty...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
no content This PR has a target that contains no valid content for a request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants