package name "templ" is not searchable

[k-x7]

Hi all,

I really like this package and how it makes everything easier, but I have an issue with the name.

The package name is really hard to search for issues, guides, etc...., when I try to search "temple" or "golang templ" all results are related to the std packages or some random package, and guides.

I think It will be great if we have a unique name for the package before it is becoming hard to change it.

[a-h]

Agree! I don't like that it's connected to my username since people like @joerdav do a lot of work on templ.

So, I set up a Github organisation, and have started to move anything that I can there, e.g. https://github.com/templ-go/templ-vscode

From my Google results, at least, it looks good:

However, I don't think I can move templ itself without breaking Go import paths as per the "Sirupsen" to "sirupsen" change from a few years back.

I haven't done any research on whether there's a way in modern Go modules to move names without breaking anything. If you want to, and could report what you find, that would be great!

[joerdav]

duckduckgo results are good too:

I think this is acceptable. I think striving for the search templ to work is a tough ask, and not common with other tools... have you tried searching "gorilla" or "buffalo" ;)

[k-x7]

Thank you both for the replies.

Let me start by clarifying what I mean by not searchable, it is how fast/easy you can find the package, guide, issue fix in stackoverflow, reddit or github or even templ.guide it self.

The first time I found about templ is by listening to Go podcast, and I try to search for the pacakge "golang templ" in Google later on without any luck, and I forget about it since until I see someone posting HTMX with templ in twitter.

Here are some examples using Google search with a private session:

Search: golang templ static html

Search: golang templ css style

Search: issue with html closing tags

All the search queries above have answers in templ.guide, If the package have a unique name like templx and this is just an example, the search engin will be more accurate about the results and can find what the user searching for.

Another example when you search for "golang pq" and "golang pqx" Google will show you what you're looking for:

@a-h sometime ago the same question has been asked in reddit maybe it can help, another example is redis client which they change the organization and the package name.

@joerdav gorilla or buffalo are unique keyword within go/golang ecosystem and the search engin will find anything releate to what you'er looking for in github, reddit or stackoverflow or blogs.

[joerdav]

Yes I think I understand now, it's about specific searches rather than searching to find templ at all.

I wonder if this is a fault of the name, or if it's the difference between a tool which has been around for a while or not. The spike in adoption of templ was quite recent so it makes sense that there are fewer articles out there in search engines that match.

[jolheiser]

@a-h wrt moving templ to the org: One solution could be to move this repo to the org (in order to transfer issues/PRs etc.) and then to push a copy to your namespace and archive it. The goproxy would also have cached templ, but this way it would also still work for any direct users.

You could also deprecate the copy in your namespace with instructions to use the new namespace.

When go geting, users would at least see a message, but importantly would still allow them to use your current namespace until they can migrate:
Example repo: https://github.com/jolheiser/deprecated

go: module github.com/jolheiser/deprecated is deprecated: use github.com/jolheiser/cursed instead.
go: added github.com/jolheiser/deprecated v0.0.2

[joerdav]

Templs SEO seems to have come a long way now. It's the first result with the search "templ"