-
Notifications
You must be signed in to change notification settings - Fork 232
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
Migrate all wiki information to user.js/README, doc improvements #225
Merged
Conversation
This file contains 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
…fox-autoconnections unshorten links Part of #220
…E, improve README: * contributing: use 80-char line width, add RSS feed recommendation * use #-style markdown headers * references section: sort and update/improve links, add rss feeds, remove duplicate links Part of #220
unshorten links clarify some descriptions add mozilla privacy principles to references Part of #220
…to user.js: rename section to HTML5/DOM APIs improve descriptions Part of #220
improve/reorder caching section: improve descriptions, some reordering/prefs grouping Part of #220
…to user.js improve descriptions part of #220
improve descriptions part of #220
* migrate wiki page Firefox-exploits-&-vulnerabilities to user.js/README * contributing: add RSS feed recommendation * change 1st level title to user.js * reorder, reword short description * (temporarily) remove obsolete Table of Contents * reword installation section headers * split long lines to 80-char width * further hardening: add reminder to update plugins * migrate wiki FAQ page to README * move beef link to references, improve Part of #220
minor cosmetic fix
references: disambiguate headers (explicit anchor links)
The last 5 commits add a few fixes and reordering. The first-level table of contents is now
|
fix headers hierarchy for upcoming table of contents
Looks good! Should we move the FAQ part into a separate file? |
pyllyukko
reviewed
Mar 1, 2017
|
||
# How to use the user.js file | ||
|
||
TODO insert toc |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should either re-add it, or remove the TODO from here and reopen #126 or create new issue about the TOC.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Ref #220
Each separate commit should be self-explanatory.
The latest README version from this branch is viewable here: https://github.com/nodiscc/user.js/blob/wiki-migration/README.md