Closed jaydson closed 9 years ago
Metalsmith uses:
"keywords": [
"static",
"file",
"site",
"website",
"blog",
"generator",
"markdown",
"jekyll",
"wintersmith",
"blacksmith"
]
Docpad uses:
"keywords": [
"document management system",
"dms",
"content management system",
"cms",
"static site generator",
"generator",
"static file server",
"server",
"web",
"web framework",
"framework",
"web development",
"development",
"dev",
"build and deployment",
"builder",
"build",
"compiler",
"compile",
"parser",
"parse",
"renderer",
"render",
"templating",
"templates",
"language agnostic",
"website",
"blog",
"cli",
"tool",
"utility",
"scaffold"
],
Oh damn, I didn't realize we didn't have keywords in the package.json
.
I guess we can use a good part of those keywords above. =]
I think a good set of keywords would be:
"keywords": [
"ssg",
"generator",
"blog",
"scaffold",
"markdown",
"website",
"static",
"static generator",
"static site generator",
"ES6",
"ES7",
]
Perhaps add ES2015/ES2016 as well? I'd also add jekyll
, seeing as people often search for similar/alternatives tools using another tool's name.
I'll add ES2015/ES2016.
About jekyll
, i don't know. This seems to be like "stealing the game"? Don't you think?
I just don't know if it is a like Google search, you know. When doing something like this is considered bad.
Not technically bad, but seen as bad by the community.
I see your point. I was just thinking about searchability, e.g. people who may use "jekyll" to search for static site generators because they may not know a more generic term. But yeah, we can live without that keyword, so it is probably better this way. :+1:
Issue solved then.
Oh, you committed to the keywords
branch instead of master, let's wait for the merge to close this then.
@UltCombo now we have to update on npm, right?
Done.
:+1: