alphaparticlecode / wp-scratchpad Goto Github PK

Seems to work on localhost, but since the new design has been implemented, the Chrome Extension doesn't seem to be picking up the display name (user_login still appears to be saved in local storage) and the user avatar (saved correctly in local storage but not loaded correctly as the background image).

This would just apply to button colors, as well as the favicon/main icon for the extension. The icon would have to be regenerated at all the various sizes as well.

This is just a double check to make sure we're not introducing any potential vulnerabilities.

OG tags have been included, but are not visible in public/index.html, meaning that many parsers can't grab them.

This should probably wait until more sites transition to Gutenberg just so we can be relatively sure we're not jamming blocks into the Classic Editor somewhere.

Also, this is a mostly crazy idea and would be more of a case of "just because we can".

Use concepts from https://twitter.com/i/events/994601867987619840?lang=en and potentially concepts from material design to make the below wireframes look ✨ ✨ ✨

Logged Out View:

Login View:

Draft View:

Currently the extension kind of breaks if you try to log in with the users endpoints blocked. The avatar doesn't show up and the Log In button is still displayed. The fix for this should likely be two-fold:

1. Show a warning when the user puts in their Site URL that the users endpoint is blocked and might not make the avatars display properly.

2. Handle the case where the JWT is gotten properly but the extension can't fetch the avatar, maybe just display the user's login rather than their display name/avatar.

User should see an error if they try to enter a URL that is not HTTPS

When local storage updates with site URL or JWT, the visibility should also update so a page reload doesn't have to occur after pasting login credentials or updating the site URL.

If Gutenberg is enabled on a site, inserted post content should be wrapped in a paragraph block so it displays more natively in the Block Editor

A pairing for Montserrat from https://fontpair.co/, search for Montserrat in the header.

API key and API secret should be temporarily saved to local storage so that the fields don't clear. These local storage entries should be deleted when login is successful.

• New icon
• Readme that includes documentation previously generated
• AP Google Developer Account

Currently waiting on designs

Record a quick screencast showing how the extension works, basically covering the same ground as is in README.md

This button removes the current URL from local storage, allowing the user to "start over" with more of a blank slate. This should remove the JWTs from local storage as well.

Add Getting Started documentation that details installing the JWT plugin on the WordPress side, creating API keys and secrets for users, installing the Chrome extension, and creating a first draft post.

This button should be visible when a user has already provided credentials and will clear both the access_token and refresh_token from localStorage.