-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Add generator meta #649
Add generator meta #649
Conversation
Thanks for the contribution. I never realize such meta tag before. Could you please also add Hexo version on it? |
Many other applications use this meta tag, too. e.g. jekyll, hugo, etc. I could add the semver, but we have to update the version number manually when Hexo update next time. I wonder if Hexo has exposed an API that we can get the version number (this would be the best solution). |
Yeah, |
I tried by setup a fresh hexo instance via
Or maybe, I think we could implement the |
@h404bi Have you tried
You can check some swig examples at https://github.com/node-swig/swig-templates/tree/master/examples/express/views. |
Yes, I tried, It's not the template syntax problem, It's because hexo.version is not accessible, hexo is undefined. Your PR works, by extending hexo helper. Look my comment left on your PR. |
Oh, I mean @NoahDragon 's PR. #650 |
@h404bi Thanks for the confirmation. I have made the change as you suggested. If you could review that change, it would be really appreciated. |
@NoahDragon Your PR LGTM. I will close mine. |
@h404bi Thank you. This is a really neat feature, we always like to know how many sites are using Hexo. |
Yes. But as I said, this is only available on https://hexo.io. I think Hexo should implement the I created the 'Add Hexo detection' Pull Request a month ago. And I added the meta tag into my blog instance. But till now, Wappalyzer doesn't have data available for Hexo yet. Because currently there are rarely sites can be detected. Thank you, too. Hope Hexo becomes greater! |
@h404bi You are right, I will try to implement this feature into Hexo core, which every site using Hexo will automatically add this line in the head. |
The Agolia team has requested that we add <meta name="generator"> (#754) tags to identify pages generated by MarkBind. Since this tag is part of HTML5 [1] and can be used by other external providers to identify MarkBind generated sites, we can include this tag in all MarkBind pages. We can also include the version number to allow tracking the use of different MarkBind versions, as other projects have done [2, 3]. Let's include the <meta name="generator"> tag to identify MarkBind pages, as well as including the version number to track the use of different MarkBind versions. [1]: https://www.w3.org/TR/html5/document-metadata.html#generator [2]: hexojs/site#649 [3]: gatsbyjs/gatsby#8221
This allow Wappalyzer to Identify the site is built with Hexo.