1. Great stuff :) Thanks Philip! Now our blog posts will look so much better

  1. Congratulations, Philip! Great plugin with good APIs!

  2. I’ve been running something similar on my own blog for a quite a while. I basically use the same method, except with a lot less code. It’s nice to see someone wrap this up in a plugin for others to use though.

    1. Justin, could you opensource your approach? Perhaps Philip would improve his plugin = everybody wins ;)

      1. The plugins do the same thing. His is just better for being a public plugin since the code is more rounded out. I’ll look more into it and shoot any GitHub tickets his way though if I see anything that’s different between the two.

  3. Sweet!
    An important point left out (that it’s in the repository)…

    1. Jim Walker – It was just approved for the repo – not an important point left out ;)

  4. @Jim, the plugin sees to have multiple CSS and JS files, will it impact loading time? Also, the CSS class for subtitle seems to be “entry-subtitle”, wouldn’t an h2 class suit better?

    1. H2s are not suitable for subtitles. Please read the documentation for why:

      * 5. The reason that are being used is because HTML does not have a dedicated mechanism for
      * marking up subheadings, alternative titles, or taglines. There are suggested alternatives from
      * the World Wide Web Consortium (W3C); among them are spans, which work well for what we're trying
      * to do with titles in WordPress. See the linked documentation for more information.

      See the W3C for more information.

      If you’re concerned about the markup of the output, you can also filter it to your liking.

      There is only one CSS file output to the front end of the site. The other files are for the back end of your site. There’s one CSS file to style the input, one JS file to manage the input interactions, and one CSS file for a sensible style default for your subtitles.

      Any additional concerns you may have I’ll be happy to answer on GitHub or on WordPress.org.

    2. Rahul, one more thing. Please feel free to read through the inline developer documentation to understand more about the design decisions in this plugin: https://github.com/philiparthurmoore/Subtitles/blob/master/subtitles.php.

      In short, no, SEO shouldn’t suffer. Yes, you can totally change the output of how subtitles appear on your site. 1 CSS gets loaded to your site – I could certainly see a case for inlining this styling to avoid the extra server request and will consider it in a later version. The other 2 resources (1 CSS and 1 JS file) are needed for sensible usability in the back end.


      1. Hey Philip! Is there anyway to integrate this with Noah Kagan’s Headlines (by KingSumo, the sister company of AppSumo)? I find that it generates a second subtitle on the archive, based on the WooThemes’ SuperStore theme.

        If yes, it’ll be amazing, because Headlines’ is indeed an amazing idea :)

        1. If you open an issue on GitHub and explain to me exactly the steps that I can take to reproduce your error then I’ll be happy to either add integration directly into the plugin or tell you how to fix it on your own. I don’t have access to the theme that you’re referring to, but my hunch is that this may boil down to a very simple solution. We can discuss it directly on GitHub. Thanks.

  5. badsandy

    Love this. Thank you!

  6. mtibesar

    A very nice plugin – should be part of Core. It works on my Themify theme. Thank you Philip and Sarah!

    One recommendation would be the capability of populating all Post subtitles with existing excerpts. All of my excerpts play off of the Post titles.

  7. Kevin Cheng

    Sarah – Thanks for posting this! Philip – Thanks for providing us this much-needed functionality in a plugin! You just made my day – this is just what I’m looking for.

  8. N.E. Montgomery

    It also works great in ElegantThemes’ Divi, which quite doesn’t play well with some plugins. Nice post and nice plugin!

Comments are closed.