to make showig changes from {user}.github.io/choosealicense.com
possible, as suggested by @waldyrious in
https://github.com/github/choosealicense.com/pull/833#issuecomment-860777503
Note links within the site will still break in this scenario, would
need relative_url sprinkled in all internal links to avoid. Non-goal
for now.
Not needed elsewhere eg license view because actual rule is spelled out
and no distinction with other licenses with non-attenuated versions of
the rules is useful for eyeballing
Some visual cue other than .5 opacity might be more useful, eg smaller
or not filled in circle, but this is easy first cut given current sprite
setup
Not certain this is right thing to do, but
https://jekyllrb.com/docs/assets/ says "Note that the sass_dir
becomes the load path for Sass imports, nothing more" so setting
it to `assets/vendor` and changing imports accordingly ought and
seems to work without disturbing other files under `assets/vendor`,
even though the docs continue "This folder should only contain
imports."
and are structured
grant (permissions)
conditioned on (conditions)
with limitations
Permissions coming first combats mistaken but apparently widespread
impression that licenses impose conditions, even such that without
a license, there would be no conditions/work would be in the public
domain.
Requirements->Conditions emphasizes that they are pertinent if one
wants to take advantage of permissions.
Forbiddens->Limitations is more accurate: in most cases licenses
don't give permission to hold licensors liable, in some cases to
use licensors' trademarks or patents, but a licensee does not lose
the permissions granted by the license if the licensee holds licensor
liable, etc. Also emphasizes that there are limitatations on the
license grant, not that the license imposes prohibitions.
The most concise place to see both the rename and reorder is in
_includes/license-overview.html
I did not reorder the appearance of the groups of properties in
license source files (.txt files in _licenses) as those orderings
are not used to render anything on the webiste. Might do so later.
Accurate flash detection is a little more complicated than this. The
current code causes an error on IE 10.
This removes the attempt to detect if flash is available. Instead, it
attempts to initialize ZeroClipboard and sets up the fallback.
ZeroClipboard will be a no-op if flash is not available, in which case
the fallback will already be configured. If flash is available, it will
put a flash object over the button and the fallback will never get
called.
