Unify project name as "Liquid Prompt" in docs (spelled as two words)

[ottok]

On the front page README.md the project name is spelled "Liquid Prompt" as two words. This PR suggests to use that spelling across all project documentation.

[Rycieos]

In my opinion, I think it makes sense as one word. The project ID is also one word; if it was two words, I would think it would be liquid-prompt. I would rather see any instances of "Liquid prompt" changed to "Liquidprompt" than this.

But @nojhan named it originally, so what would you like to see?

[augmentedfourth]

Also note that the package name in homebrew (and I think other distribution mechanisms) is a single word, un-capitalized... just like the file name of the script itself. I'll defer to @nojhan as well, but as someone who's used this tool for over a decade "Liquid Prompt" just looks jarring.

[nojhan]

That's a though question. Do someone have access to some SEO tools to check which name leads to the largest search engine share (out of existing hits)?

[Rycieos]

Do someone have access to some SEO tools to check which name leads to the largest search engine share

I'm no SEO expert, but some quick digging leads to the following:

1. "Liquid prompt" has more than 10 times the "hits" than "Liquidprompt" does, but that is not a fair comparison. The space means it is two separate search terms, and you get a ton of false positive hits.
2. "Liquid prompt" hits mostly on blog posts about the project (so many blog posts, wow).
3. "Liquidprompt" hits mostly on documentation and packaging indexes.
4. "Liquidprompt" hits on pages with only the string "Liquid prompt" in the page.

Based on this, I think:

• Because of 4, searching with the string "liquidprompt" will hit both forms, while "liquid prompt" won't always.
• Documentation is probably the first thing we want users to find.
• Because of 1, we don't want users to find unrelated pages.

I think that "Liquidprompt" is better for SEO.

[nojhan]

Seems like a good point to me :)

…

On Mon, Jun 28, 2021 at 6:31 PM Mark Vander Stel ***@***.***> wrote: Do someone have access to some SEO tools to check which name leads to the largest search engine share I'm no SEO expert, but some quick digging leads to the following: 1. "Liquid prompt" has more than 10 times the "hits" than "Liquidprompt" does, but that is not a fair comparison. The space means it is two separate search terms, and you get a ton of false positive hits. 2. "Liquid prompt" hits mostly on blog posts about the project (so many blog posts, wow). 3. "Liquidprompt" hits mostly on documentation and packaging indexes. 4. "Liquidprompt" hits on pages with only the string "Liquid prompt" in the page. Based on this, I think: - Because of 4, searching with the string "liquidprompt" will hit both forms, while "liquid prompt" won't always. - Documentation is probably the first thing we want users to find. - Because of 1, we don't want users to find unrelated pages. I think that "Liquidprompt" is better for SEO. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#677 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACFSULFQ3O5TVIFXFJZE4LTVCPW3ANCNFSM47NH6NYA> .

[ottok]

I'll wait for a week for further feedback and if this is the decision, I'll revert the PR to do the change for all current Liquid Prompt into Liquidprompt.

[dolmen]

As someone who has contributed to this mess, my preference was Liquid Prompt as the project name and liquidprompt as the command to invoke it.

But as a former maintainer, consider my vote as neutral if votes are involved.

[ottok]

When looking at pages that Google finds on "liquidprompt" they are all pages that reference the package name, not the project name. As soon as you start to get results about blog posts that decribe the project, everybody seem to write about "Liquid Prompt" – two separate words, and both capitalized. I agree with that and I think it is also better English (though I am not a native speaker). One of the search results with "liquidprompt" even yields "Liquid Prompt", because that blog post is so popular.

Thus, I leave my PR leaning on "Liquid Prompt".

vs

[ottok]

I also checked Google Trends. The name "Liquid Prompt" is more popular than spelled together, but the search volume is so low that the difference is not significant.

[Rycieos]

Sorry for the radio silence on this. I'm not sure what the path forward should be, since we have a few on each side of the camp, and @nojhan seems to be fine either way. Ideally we would get some other opinions on this, but I realize that leaving this sitting open forever is not ideal either.

[ottok]

Don't worry, leaving the issue open is fine to me, no hurry here :) In this case taking some time to collect feedback and think about it is a good thing.

…

[nojhan]

Looking at the search engine results, I think "Liquid Prompt" would better match what the actual users are using to refer to the project.

This is a key point in my opinion, because we are facing competitors that have less interesting features and design, and still surprisingly seem to be more popular. We definitely need to reach the users in their own words.

Also, it emphasizes one of the key feature of the design, which is to actually be liquid. It is probably worth it to use the adjective as a keyword, and I think having it separated helps. One could even use "the Liquid Prompt", so as to emphasize even more.

It doesn't seem like a big deal to have the command/repository keeping the one-word version, I think most of people would understand, especially if the official website use the two-words version.

[Rycieos]

Ok, sounds like a close enough consensus then. I agree, let's unify the name.

@ottok, if you could fix these small issues I've pointed out, and maybe squash and rebase, I'll merge this in.

[ottok]

Sure, I can refresh to use "Liquid Prompt" everywhere as agreed today.

[ottok]

Fixed all items commented and rebased on latest master.

[Rycieos]

Thanks @ottok!