Added support for ExpressionEngine #22
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Uses google "im feeling lucky" feature to search the EE user guide for a given keyword, and go directly to the top result. Not perfect but it will get you to the right page most of the time, and improving this would likely require EE user guide to be reorganized around predictable URLs for each keyword.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added support for ExpressionEngine documentation.
Unfortunately the EE docs are not normalized with predictable URLs for each keyword. Also unfortunately, the docs have no native search form. They rely on Google to index the docs.
My approach uses google "im feeling lucky" feature to search the EE user guide for
a given keyword, and go directly to the top result. Not perfect but it
will get you to the right page most of the time, and improving this
would likely require EE user guide to be reorganized around predictable
URLs for each keyword.