Skip to content
This repository was archived by the owner on Aug 6, 2026. It is now read-only.
This repository was archived by the owner on Aug 6, 2026. It is now read-only.

Make department publishing plans printer friendly #11

Description

@jasonlally

Currently the publishing plans are not very printer friendly. It hits the good enough marker, but we want department's to be able to easily print off a clean copy for use in meetings as necessary. We'd like the printed versions to feel more like an "official" report. A couple of things we're imagining changing:

  • Develop a simple, beautiful header that only shows up when printing
  • Incorporate the City and County of SF seal at the top of the report, incorporate elements that link the report to the broader DataSF program
  • Hide the elements "Department Publishing Plans" and the drop down in favor of this clean printable header
  • Make the metrics and charts more printable (chart colors need to change, and the layout should be a little different
  • Add a "page break" between the narrative and metrics, add header above metrics that only shows up printer to make the report easier to consume in printed form (read: skimmable)
  • Expand the data table to show all records when printing, repeat table headers at top of each page and remove,
  • Remove navigation and footer elements that are not useful in the printed form (navigation links, icons linking to github, etc.)

Why go through this when we took the pains to get it on the web? Because some of our users won't have web enabled conference rooms, and sometimes the printed report is just easier to work off of, mark up, etc. The digital future is near, but we still need to meet our users in the departments where they are.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions