New Name & better tags

[willmot]

Whilst the current name does decribe the plugin I think it could be more user friendly.

I have a couple of issues with the current name:

• Do people know what TOC means?
• Content is mentioned twice.

Here's some suggestions

• Inline Table of Contents
• Table of Contents by Human Made
• Digest
• Compendium

Here's some other plugins that show up when searching for Table of Contents: https://wordpress.org/plugins/search.php?q=table+of+contents

[dashaluna]

@willmot good points!

How about HM Table of Contents that's @johnbillion suggested? Or is it better to avoid acronyms in the title all together?

I've got some questions that's related to renaming:

1. The domain will stay the same hm-content-toc as well as the main plugin file name due to how things work with WP plugin repo?
2. Shall we review the tags used by the plugin here as well? I've added a separate comment below - would be great to do it as well!
3. The translations will have to reflect the rename changes?
4. Would I need to change a name of the shortcode? I guess this means backwards compatibility .. not sure if yes, and if so how to handle that?

/cc @johnbillion

[dashaluna]

Current Tags:
TOC, TOC shortcode, shortcode, content TOC, post TOC, page TOC, TOC for content, table of content, table of contents, HM, Human Made

Other plugins tags:

• category listing, cms, indexes, list, options, page listing, sitemap, table of contents, toc
• table of contents, toc
• automatic, category, class, cms, definitions, hints, html, index, indexes, list, listing, pages, posts, shortcode, table of content, table of contents, tag, toc, wordpress
• content, plugin, table of content, toc
• category listing, cms, list, options, page listing, sitemap, table of contents, toc

Proposed New Tags:

• table of contents, table of content, toc, shortcode

[dashaluna]

@johnbillion wanted to know your opinion re my questions ^. :) Thanks!

[dashaluna]

@willmot @johnbillion sorry to bugging you guys, just wanted to proceed with this :) Let me know your thoughts and advice. Thanks!

[johnbillion]

The domain will stay the same hm-content-toc as well as the main plugin file name due to how things work with WP plugin repo?

Yes, the text domain and plugin file name will stay the same.

Shall we review the tags used by the plugin here as well? I've added a separate comment below - would be great to do it as well!

I wouldn't worry quite so much about the tags, but your proposed new tags look good.

The translations will have to reflect the rename changes?

You'll need to get new translations for the plugin name, yes, but the rest of the translations won't be affected.

Would I need to change a name of the shortcode? I guess this means backwards compatibility .. not sure if yes, and if so how to handle that?

You can add another shortcode and leave the current one in place for back-compat. Just add another instance of add_shortcode() like there is here:

hm-content-toc/includes/class-content-toc.php

Line 39 in 020d61f

add_shortcode( 'hm_content_toc', array( $this, 'shortcode' ) );

. Using [toc] for the shortcode might be a good idea.

[dashaluna]

Renaming the following:

1. Actual plugin name
2. Namespace
3. Shortcode tag/name
4. Labels on shortcake screen
5. Labels on settings screen
6. readme file

WAAAAAAAAAAAAAAA rename all the things, but keep the old shortcode name for some backwards compatibility.

[willmot]

👍

[dashaluna]

After looking at it again, I've decided to rename only user facing bits and leave everything else as is for backwards compatibility.

Renaming the following:

• plugin name
• admin text - plugin settings page
• admin text - shortcode UI integration
• add new/main shortcode [toc]
• update readme file
• update pot file
• update translations - RU
• update translations - IT
• update translations - PT
• update unit tests
• update screenshots