Skip to content

Missing dash in TITLE metadata #1188

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
zjalexander opened this issue May 2, 2017 · 9 comments
Closed

Missing dash in TITLE metadata #1188

zjalexander opened this issue May 2, 2017 · 9 comments

Comments

@zjalexander
Copy link
Contributor

Originally reported by Chrissy LeMaire:

I find it disconcerting that searching for PowerShell commands returns pages with titles that are missing the dash.

For example:
bug1

The page itself has a proper title

bug2

Can this be fixed? The reason it's an issue is because I initially scan over it. I assume others may too. My brain is trained to look for the dash, otherwise, it lumps the result in with ads or rando blog posts.

In the end, I end up having to fight my natural response that tells me to click on SS64.com.

bug3


If you look at the raw markdown, you will see a bunch of tags, including:
title: Get AuthenticodeSignature

That title tag is what we use to generate the page title, which is what search engines pick up, and it is missing the dash.

So, not an infrastructure problem! Just a metadata problem that we need to fix. Now we need to see how many items are missing the dash in the title….

@juanpablojofre
Copy link
Contributor

The other similar problem we're facing is the casing in the filenames.
We have put some effort in making sure cmdlets are documented using Pascal casing; and, at the same time, we made all reference filenames lowercase (forgetting the UX community, where names are case sensitive).
I'm working on finding and fixing all metadata titles that don't match the exact cmdlet name (with casing and dash).

@zjalexander
Copy link
Contributor Author

@juanpablojofre your comments about casing are in reference to #1175, is that accurate?

@juanpablojofre
Copy link
Contributor

It seems, this issue was part of the migration process.
Almost all topics have the same problem.
I have identified 1769 topics with this issue.
I'm ready to fix; expect a large PR for you to review.

@juanpablojofre
Copy link
Contributor

PR #1190 should fix this issue (#1188)

@zjalexander
Copy link
Contributor Author

oops.... this impacts at LEAST psget as well. @juanpablojofre would you mind re-running your amazing script against the different directories? we should also keep an eye out for underscores in page title.
https://msdn.microsoft.com/en-us/powershell/gallery/psget/module/psget_find-module
image
image

@juanpablojofre
Copy link
Contributor

@zjalexander, @bmanikm

I think we need define better our reference strategy for the Gallery.
I feel it is confusing for all PowerShell users to find duplicate content for PowerShell Get.
Some content exists as versioned content under PowerShell X.Y reference and other content exists under Gallery/PSGET.
What do you think about this, Zach, Manik?

@bmanikm
Copy link
Contributor

bmanikm commented May 16, 2017

@JKeithB please take a look at above concern. I agree with @juanpablojofre to unify the PowerShellGet content under single location.

@juanpablojofre
Copy link
Contributor

Updating Title metadata tag as requested by @zjalexander

@ghost ghost added the reference label May 23, 2017
@juanpablojofre
Copy link
Contributor

Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants