-
Notifications
You must be signed in to change notification settings - Fork 205
Conversation
Very useful if you have an array of tags and want to search by them.
Added support for array properties.
Thank you very much :) |
Great! I'm using it right now for a work project :) Also, maybe the search.json should just be a main file? Considering it's just for jekyll it should always be in the project. Plus dependancies tend to be external sources. |
search.json is required for the plugin to work on Jekyll sites.
FYI don't go mad with the rewriting! It works perfectly right now :). |
Interesting, the search.json file could be moved to the example only, in fact.. I'm sorry but I have to rewrite it, because I learned a lot of stuff in the last months and I want to apply them :) The API will change, but not dramatically, I hope |
I wouldn't move it into the example, people who use the plugin will need it? I'd advise putting the example in a gh-pages branch so you can host the example and keep it out of the master branch, which will mean the whole download will be a lot smaller. Well that's ok, as long as the implementation doesn't really change. Was so easy to add into my project 👍 |
Yes I was thinking about a completely separate GH-Pages branch. |
Sounds good. I'd structure it something like this: repo:
|
+1 |
Get it submitted to bower too, "jekyll-search" as a package name hasn't been taken. |
Would you like me to recreate this pull request to match your newly revised project? |
Thanks :) |
Ace! Is it stable and useable right now? Or are you still working on it? |
I would say it's way more stable than the last version, tests pass and rewrote it to be easily maintainable. It's totally usable. The previous version was a nightmare. |
Good to know, I'll close this pull request as I've submitted the file under a new one now. |
I've created a basic bower package install file. You'll obviously need to make your own changes to it, but I tried to put as much info related to your repo in it as I could.
I'd advise some kind of clean up on the repo a little, not that it's a major issue. Using bower to install the plugin means that users, like me, can use gulp and hook into the main bower file to bring only what's needed into the main project files.
I'd make the search.json file a dependancy so people can deal with the file separately to the main plugin.