sitepoint / wp-band-aid Goto Github PK

Excerpt frame should

• be resized to be more readable
• auto-remove [author_more]

In most cases, the default syntax of a post matches its primary category.

Make it so that when a primary category is selected, the syntax switches to that value too, if available.

The syntax value can be additionally changed after the fact, if needed.

From the docs:

Second-level headings should also be in titlecase.
Third-level headings should be in sentencecase.

The error messages that appear in the bottom of the editor are hard to reach when distraction-free mode is on.

It'd be better if the extension detected distraction-free mode, and adjusted the position of the error messages to the top of the editing field when it's on.

The code is more or less browser-agnostic. Basically just copying the JS and CSS into the WP files itself would work. So it should be relatively easy to build this extension for Firefox as well. Anyone up for it?

This may also apply to other non-http links.

One thing that gets really messy and confusing for me when scheduling articles is knowing when the article is scheduled in my local Sydney time. I was thinking it'd be fantastic if when articles are scheduled, WP Band Aid could also show underneath that scheduled time the local time — maybe detected from the user's computer?

It'd still be important to have the actual scheduled time in Pacific Time, so that we can be certain it's set correctly to schedule, but local time is handy when adding the times into Trello cards and just for planning ahead to notify authors... etc.

Thanks :)

Seems like it doesn't work with the PHP category.

Add the ability to select a bit of text and turn it into a "show/hide" block.

Step by step:

1. Select bit of text
2. Click "show/hide"
3. JS selects the first <p> node encompassing the selection.
4. The node is given a .show-hide class, and a data-title attribute (ask for title interactively?)
5. The editor-content loop checker checks to see if there are .show-hide elements in the text, and if there are, makes sure the JS needed to power them is present as well.

Alternatively/additionally, support class-based show/hide - the UI should automatically detect such classes if they come into WP as such, and apply the show/hide mechanism to them.

Sometimes we editors need the permalink of the article that is to be published - we need it before it's actually out, in order to link to it from other places in advance (like other tutorials, newsletters, etc.).

It is currently possible to get it by just copying the slug under the title, and prepending http://sitepoint.com to it, but it would be even simpler if there were a "copy link" button next to "View post", which did this automatically.

Currently, when the title is changed, to rebuild the permalink one must enter the permalink field, empty it, and click OK. A button next to the one for checking subheadings would be better, I think: "Rebuild Permalnik".

Alternatively, maybe have the permalink auto-rebuild on title change? Though some people may want to keep their custom permalink. Maybe make it an option?

Feature request - a pop-up to remind editors to check over the URL slug before saving/scheduling an article. We’ve been having articles go out with a bunch of numbers as the URL slug lately. It’s really tricky to work out what’s going on so a reminder to make sure a slug is correct would be helpful, and would at least rule out human error as a cause. If possible, having the pop-up only appear when a URL is a bunch of numbers would be perfect, but a general one would work as well.

Named anchors should not be considered relative links. Links without href attributes (for custom JS or whatnot) should be ignored also. Likewise, links starting with a slash are fine - they will lead to the SitePoint.com root domain, so such relativity is okay.

Would be nice to have HTML > MD conversion.
This would be useful when asking an author to update a post that is not in the repo (as then you could generate a MD version automatically and have the author work in that).

Due to the extensive number of UI changes the extension does to the default WP UI, perhaps some kind of preloading screen (a cover to hide the main screen until all loading it done) would be better of UX?

Needs discussion - could potentially be more distracting than the jittering itself.

The code is quite messy and hacky right now.

A cleanup would be good. Reducing jQuery dependencies, fewer loops, more caching, etc.

Make it an option to hide the .update-nag frame.

By including this in the extension as an option, admins can leave it off and still see the update warnings, and editors can permanently hide it, while still letting ads be shown on the main sitepoint.com domain (using an adblocker to remove the frame means blocking ads all over SP)

Add a "snippet insert" dropdown/popup for regularly reused bits of content.

For example, in a PHP article, we may say "Install with Composer by running composer require package/something". Rather than repeat "If you're not familiar with Composer blah blah..." we could have a pre-written selectable "Composer explanation" element which, when clicked, gets inserted at the location of the cursor, defaults to "Show/Hide" (see #5) and offers a short explanation on Composer AND a link to our post about it, thus effectively cross-linking posts.

Another idea is "install with Gulp (show me how)" which summons a show/hide frame explaining you need Node, NPM, and sudo or nodeenv to use Gulp, etc, possibly linking to a related post or two as well.

Another regularly reused bit of content might be "This article was peer-reviewed by the following people:" which opens a popup allowing a two-column set of input fields for Name => Twitter pairs which then get inserted into the post and properly formatted without the editor having to do much of it.

Other ideas are welcome...

For the purpose of easier newsletter crafting until Edithor is up and running, add a feature for meta data extractions:

• right click on page offers selection of "Copy meta description" and "Copy meta title"
• right click on link offers selection of "Copy destination meta description" and "Copy destination meta title"

These features would allow easier copy-pasting of meta data into the relevant fields in campaign monitor.

Every now and then an editor will accidentally paste an h1 heading into a post, then accidentally not preview it, and then publish it. Let's make that harder with a warning to take them out if they're not there on purpose. Possibly dismissable in case the editor wants the heading there and doesn't want to be annoyed by them?

Add a reminder to credit people who helped peer review the article?

This is just a small thing, but technically SitePoint always uses "www" in front of its URLs so the "copy link" functionality should do that too. Right now, it copies "http://sitepoint.com" instead of "http://www.sitepoint.com" which just feels so naked! :)