A few additional places where the news and press pages were not
properly menu integrated. This fixes various inconsistencies and
missing category and submenu markings in menus.
ourcoverage.html was a reasonable minimal start but not really ready
for production. Make changes necessary to put this into production,
as follows:
* Rename ourcoverage.html to vizio-coverage.html. This is just
Vizio coverage for now.
* Order articles by most in-depth/interesting. Verified this
ordering by consensus with Conservancy staff.
* mailto: link for press coverage on the main inthenews page, but
don't use that on Vizio page; it's unlikely we'll miss any of the
Vizio coverage.
* use — instead of -
* put quotes around article titles.
* Add missing PR Web article
* Switch from <p>'s to <li>'s in vizio-coverage.html
* Fix menu issues. 09a4b02 outlined the issues regarding how to
add items to menu; it does require a CSS change as explained
therein; merely using the right `base_` is not enough
* Improve menu integration. Per PR people's recommendation, the
Vizio stuff that also goes in other areas needs to be placed in
multiple menus.
During the recent improvements made on the website, the menus and
submenu highlighting for selected menus fell into disarray.
Correction requires changes to the CSS and templates both, because
Django doesn't really have a convenient way to set variables in
templates to use to solve this.
There are still a few submenu items highlighting not working even
after this commit. More work needs to be done.
Due to the varying types of layouts used and the short time-frame the best
option seems to set a max-width etc. around the "outercontent" block. For now
this means we can't do "full bleed" body content, but that's not currently used
anyway.
Uses a combination of CSS changes and Tachyons classes to implement the design.
Adds the non-minified Tachyons CSS library itself and SVG icons from Font Awesome.
* Put more common donation methods higher up.
* Delist Flattr.
* Update the list of foreign currency accounts we hold.
* Update the section about donating to member projects.
* Wordsmith throughout, primarily to avoid accounting jargon and
abbreviations, and use fewer exclamation marks.
When one sponsor has a logo, and the next one doesn't, it looks like
the textual name of that sponsor is the sponsor above it. This bit
of CSS corrects that problem.
The expandable sections can be expanded either one-by-one, or with
the “Expand All” button. Add a counter for each expandable
section (which requires their div's to have 'id' attributes, lest
they be counted in the '__global' section of expandables).
The __global counter will work as advertised if you have no 'id'
attributes on any of your 'expandable-section'-classed div's, but if
you mix a __global without an id with ones that *do* have an id, it's
likely this particular code won't work for that.
Finally, add some documentation which is probably over-documenting
for someone who knows Javascript and jQuery well, but it took me a
while to figure out this code so I felt throwing some notes in there
might be helpful.
I pulled this from the `blog-left` style I used to use in blog posts
and created a new style called picture-small. On smaller screen
real estate, Tony's picture was ultimately too big.
I wrap the entire section that has material that can be expanded in a
div with class `expandable-section`. Once doing so, if you provide an
anchor with the class of `expander`, that anchor will be created with
text in the `data-expand-link-text` attribute.
I've also added some CSS to make the link look a certain way, for
good measure.
The copyleft-compliance/about.html page doubles as the introduction
page to our compliance work. This is a start at the rewrite of that
page to link off to the new items and have new text to inspire
interest in the project.
This rewrite should improve the stand-alone nature of these documents
and allow for better integration with other summary text and
announcements on the website.
Note that they have now drifted heavily from the original formulation
of the items as grant proposals.
This rewrite should improve the stand-alone nature of these documents
and allow for better integration with other summary text and
announcements on the website.
Note that they have now drifted heavily from the original formulation
of the items as grant proposals.
These are mostly minor edits (typo fixes, etc.) to the enforcement
strategy and firmware liberation pages that were just added.
The one large change was to replace the first paragraph of the
enforcement strategy page with the full Conservancy description used
previously. The glue text used to shorten it appeared unsalvageable
and it wasn't immediately obvious how to replace it with something
better, so we used the full description instead.
These two new documents are based on grant proposals for this work.
We are preparing to announce the work publicly soon. This is a first
draft of both documents.
This page had much out of date material, particularly the timeline
and the types of projects we seek, but also the FAQ section did not
include standard information that we're now regularly giving projects
during intake.
This update attempts to address many of those issues.
