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

API Sites: Support for custom types #54

Open
scottgonzalez opened this issue Jun 23, 2014 · 4 comments
Open

API Sites: Support for custom types #54

scottgonzalez opened this issue Jun 23, 2014 · 4 comments

Comments

@scottgonzalez
Copy link
Member

Determine if there's a sane way to have custom types or if we should just include the custom types in the standard Types page, even though they're not really relevant to jQuery Core.

See qunitjs/api.qunitjs.com#55

@jzaefferer
Copy link
Member

This could also be used in the jQuery UI (and Mobile) API docs for the new instance method. Currently we have to document that as returning Object. With custom types we could be more specific.

@jzaefferer
Copy link
Member

Any idea how to approach this?

@scottgonzalez
Copy link
Member Author

I think there are really only two choices. 1) We put all types on api.jquery.com, even if they have nothing to do with jQuery. 2) We duplicate the types page on each site, allowing each site to add whatever they need.

@jzaefferer
Copy link
Member

Maybe we can go with 2) while maintaining a template in this repo, with a copy of the file from api.jquery.com. Then other sites can extend that template instead of duplicating everything.

If that's too much effort, going with 1) seems okay. We can have a header that groups "outsiders" together, with links to their respective sites.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants