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

how to support both APIs #24

Closed
maelle opened this issue Jun 29, 2020 · 3 comments
Closed

how to support both APIs #24

maelle opened this issue Jun 29, 2020 · 3 comments

Comments

@maelle
Copy link
Collaborator

maelle commented Jun 29, 2020

@hrbrmstr 👋

  • depend on pressur by @hrbrmstr or use its auth function or? In pressur there are more functions. some of the functionality like wp_about_me() cannot be mirrored with the wordpress dot org API.

  • how to best document the adventure to follow (super important to make that user-friendly and clear)

    • an user needs to choose an API based on their website.
    • an user should add custom CSS for syntax highlighting but you can't do that for a free/cheap wordpress dot com website.
    • an user should add custom JS for MathJax (not all users need that) but you can't do that for a free/cheap wordpress dot com website.
@maelle
Copy link
Collaborator Author

maelle commented Jun 29, 2020

from https://twitter.com/hrbrmstr/status/1276863122440151042

free/cheap http://wordpress.com def has .com API support. (I've just confirmed that for my own test wordpress dot com site)
havne't ever paid for http://wordpress.com so can't speak to biz
self-hosted w/o JetPack => .org api
self-hosted w/JetPack => .com API

@maelle maelle pinned this issue Jun 29, 2020
@mdingemanse
Copy link
Contributor

I think this one's also resolved by the changes on the WordPress side reflected in #39

@maelle
Copy link
Collaborator Author

maelle commented Apr 4, 2023

🎉

@maelle maelle closed this as completed Apr 4, 2023
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