├── .github ├── FUNDING.yml ├── PULL_REQUEST_TEMPLATE.md ├── ISSUE_TEMPLATE.md ├── SECURITY.md ├── CODE_OF_CONDUCT.md ├── SUPPORT.md └── CONTRIBUTING.md ├── icons ├── icon16.png ├── icon48.png ├── favicon.png ├── icon128.png ├── icon256.png ├── icon256.xcf ├── screenshot.png ├── large-promo-tile.png ├── small-promo-tile.png ├── marguee-promo-tile.png └── wireframe-icon.svg ├── css ├── images │ ├── background-image.jpg │ ├── background-image.xcf │ └── image.svg ├── fonts │ └── redacted │ │ ├── redacted-regular.eot │ │ ├── redacted-regular.ttf │ │ ├── redacted-regular.woff │ │ ├── redacted-regular.woff2 │ │ ├── redacted-script-bold.eot │ │ ├── redacted-script-bold.ttf │ │ ├── redacted-script-bold.woff │ │ ├── redacted-script-light.eot │ │ ├── redacted-script-light.ttf │ │ ├── redacted-script-bold.woff2 │ │ ├── redacted-script-light.woff │ │ ├── redacted-script-light.woff2 │ │ ├── redacted-script-regular.eot │ │ ├── redacted-script-regular.ttf │ │ ├── redacted-script-regular.woff │ │ ├── redacted-script-regular.woff2 │ │ ├── redacted-regular.svg │ │ └── redacted-script-regular.svg ├── inject.js └── styles.css ├── _locales └── en_US │ └── messages.json ├── background.js ├── manifest.json ├── readme.md └── LICENSE /.github/FUNDING.yml: -------------------------------------------------------------------------------- 1 | custom: https://paypal.me/ao5357 2 | -------------------------------------------------------------------------------- /icons/icon16.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ao5357/page-to-wireframe/HEAD/icons/icon16.png -------------------------------------------------------------------------------- /icons/icon48.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ao5357/page-to-wireframe/HEAD/icons/icon48.png -------------------------------------------------------------------------------- /icons/favicon.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ao5357/page-to-wireframe/HEAD/icons/favicon.png -------------------------------------------------------------------------------- /icons/icon128.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ao5357/page-to-wireframe/HEAD/icons/icon128.png -------------------------------------------------------------------------------- /icons/icon256.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ao5357/page-to-wireframe/HEAD/icons/icon256.png -------------------------------------------------------------------------------- /icons/icon256.xcf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ao5357/page-to-wireframe/HEAD/icons/icon256.xcf -------------------------------------------------------------------------------- /icons/screenshot.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ao5357/page-to-wireframe/HEAD/icons/screenshot.png -------------------------------------------------------------------------------- /icons/large-promo-tile.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ao5357/page-to-wireframe/HEAD/icons/large-promo-tile.png -------------------------------------------------------------------------------- /icons/small-promo-tile.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ao5357/page-to-wireframe/HEAD/icons/small-promo-tile.png -------------------------------------------------------------------------------- /icons/marguee-promo-tile.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ao5357/page-to-wireframe/HEAD/icons/marguee-promo-tile.png -------------------------------------------------------------------------------- /css/images/background-image.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ao5357/page-to-wireframe/HEAD/css/images/background-image.jpg -------------------------------------------------------------------------------- /css/images/background-image.xcf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ao5357/page-to-wireframe/HEAD/css/images/background-image.xcf -------------------------------------------------------------------------------- /css/fonts/redacted/redacted-regular.eot: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ao5357/page-to-wireframe/HEAD/css/fonts/redacted/redacted-regular.eot -------------------------------------------------------------------------------- /css/fonts/redacted/redacted-regular.ttf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ao5357/page-to-wireframe/HEAD/css/fonts/redacted/redacted-regular.ttf -------------------------------------------------------------------------------- /css/fonts/redacted/redacted-regular.woff: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ao5357/page-to-wireframe/HEAD/css/fonts/redacted/redacted-regular.woff -------------------------------------------------------------------------------- /css/fonts/redacted/redacted-regular.woff2: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ao5357/page-to-wireframe/HEAD/css/fonts/redacted/redacted-regular.woff2 -------------------------------------------------------------------------------- /css/fonts/redacted/redacted-script-bold.eot: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ao5357/page-to-wireframe/HEAD/css/fonts/redacted/redacted-script-bold.eot -------------------------------------------------------------------------------- /css/fonts/redacted/redacted-script-bold.ttf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ao5357/page-to-wireframe/HEAD/css/fonts/redacted/redacted-script-bold.ttf -------------------------------------------------------------------------------- /css/fonts/redacted/redacted-script-bold.woff: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ao5357/page-to-wireframe/HEAD/css/fonts/redacted/redacted-script-bold.woff -------------------------------------------------------------------------------- /css/fonts/redacted/redacted-script-light.eot: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ao5357/page-to-wireframe/HEAD/css/fonts/redacted/redacted-script-light.eot -------------------------------------------------------------------------------- /css/fonts/redacted/redacted-script-light.ttf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ao5357/page-to-wireframe/HEAD/css/fonts/redacted/redacted-script-light.ttf -------------------------------------------------------------------------------- /css/fonts/redacted/redacted-script-bold.woff2: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ao5357/page-to-wireframe/HEAD/css/fonts/redacted/redacted-script-bold.woff2 -------------------------------------------------------------------------------- /css/fonts/redacted/redacted-script-light.woff: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ao5357/page-to-wireframe/HEAD/css/fonts/redacted/redacted-script-light.woff -------------------------------------------------------------------------------- /css/fonts/redacted/redacted-script-light.woff2: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ao5357/page-to-wireframe/HEAD/css/fonts/redacted/redacted-script-light.woff2 -------------------------------------------------------------------------------- /css/fonts/redacted/redacted-script-regular.eot: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ao5357/page-to-wireframe/HEAD/css/fonts/redacted/redacted-script-regular.eot -------------------------------------------------------------------------------- /css/fonts/redacted/redacted-script-regular.ttf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ao5357/page-to-wireframe/HEAD/css/fonts/redacted/redacted-script-regular.ttf -------------------------------------------------------------------------------- /css/fonts/redacted/redacted-script-regular.woff: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ao5357/page-to-wireframe/HEAD/css/fonts/redacted/redacted-script-regular.woff -------------------------------------------------------------------------------- /css/fonts/redacted/redacted-script-regular.woff2: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ao5357/page-to-wireframe/HEAD/css/fonts/redacted/redacted-script-regular.woff2 -------------------------------------------------------------------------------- /_locales/en_US/messages.json: -------------------------------------------------------------------------------- 1 | { 2 | "extensionName": {"message": "Page to wireframe"}, 3 | "extensionDescription": {"message": "Click an icon and turn the page you're on into a wireframe."}, 4 | "browserActionDefaultTitle": {"message": "Turn page into wire"} 5 | } -------------------------------------------------------------------------------- /.github/PULL_REQUEST_TEMPLATE.md: -------------------------------------------------------------------------------- 1 | 2 | Please include the following: 3 | 4 | * If this PR applies to a particular issue, please reference the issue by number (typing `#` will show issues) 5 | * Describe in more detail than you had expected exactly what your pull request does 6 | * Give just a little more detail before submitting :-) 7 | -------------------------------------------------------------------------------- /background.js: -------------------------------------------------------------------------------- 1 | /** 2 | * @file 3 | * The background js for the extension. 4 | */ 5 | 6 | /** 7 | * Event listener for when the extension icon is pressed. 8 | */ 9 | chrome.browserAction.onClicked.addListener(function(tab) { 10 | chrome.tabs.insertCSS({ 11 | file: 'css/styles.css' 12 | }); 13 | chrome.tabs.executeScript({ 14 | file: 'css/inject.js' 15 | }); 16 | }); 17 | -------------------------------------------------------------------------------- /css/images/image.svg: -------------------------------------------------------------------------------- 1 | 02 -------------------------------------------------------------------------------- /css/inject.js: -------------------------------------------------------------------------------- 1 | /** 2 | * @file 3 | * Injected JavaScript to perform operations that cannot be accomplished with 4 | * CSS alone. 5 | */ 6 | 7 | "use strict"; 8 | 9 | const srcChecker = /url\(\s*?['"]?\s*?(\S+?)\s*?["']?\s*?\)/i; 10 | 11 | /** 12 | * Add a class to all elements that have a background image. 13 | * 14 | * We will use CSS to override the image to a medium grey generic bg image. 15 | */ 16 | Array.from(document.querySelectorAll('[id],[class],[style]')).forEach(function(node){ 17 | let prop = window.getComputedStyle(node, null) 18 | .getPropertyValue('background-image'); 19 | 20 | let match = srcChecker.exec(prop); 21 | if (match) { 22 | node.classList.add('has-background-image'); 23 | } 24 | }); 25 | -------------------------------------------------------------------------------- /manifest.json: -------------------------------------------------------------------------------- 1 | { 2 | "author": "Brad Czerniak", 3 | "name": "__MSG_extensionName__", 4 | "short_name": "p2wire", 5 | "description": "__MSG_extensionDescription__", 6 | "version": "1.0.0", 7 | "default_locale": "en_US", 8 | "background": { 9 | "scripts": ["background.js"], 10 | "persistent": false 11 | }, 12 | "browser_action": { 13 | "default_title": "__MSG_browserActionDefaultTitle__" 14 | }, 15 | "homepage_url": "https://github.com/ao5357/page-to-wireframe", 16 | "icons": { 17 | "16": "icons/icon16.png", 18 | "48": "icons/icon48.png", 19 | "128": "icons/icon128.png", 20 | "256": "icons/icon256.png" 21 | }, 22 | "manifest_version": 2, 23 | "permissions": [ 24 | "activeTab" 25 | ], 26 | "web_accessible_resources": [ 27 | "css/fonts/*.woff2", 28 | "css/images/*.jpg", 29 | "css/images/*.svg" 30 | ] 31 | } 32 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE.md: -------------------------------------------------------------------------------- 1 | # Before opening an issue: 2 | 3 | * Search for duplicate or closed issues 4 | * Check our SUPPORT.md file for details 5 | 6 | # For bug reports: 7 | 8 | 1. Which OS/Browser/stack and other applicable technologies are you using? 9 | 2. What steps (URLs are great here whenever possible) can you follow (given 1) to replicate the problem? 10 | 3. What is the expected result of following step 2? 11 | 4. What happens instead? 12 | 5. Are you willing to try and fix it yourself as a contributor? 13 | 14 | Please tag bug reports with the 'Bug' label. 15 | 16 | # For enhancement requests 17 | 18 | * What exactly should the enhancement be? 19 | * Why should this be an enhancement to this project rather than the userspace? 20 | * What other projects have similar functionality or content? What makes these implementations cool? 21 | * Who benefits from this enhancement? 22 | * What documentation needs follow from this enhancement? 23 | * Is backwards-compatibility a concern? 24 | * Is additional test coverage required? 25 | * Are you willing to try and create the enhancement yourself as a contributor? 26 | 27 | Please tag enhancement requests with the 'Enhancement' label. 28 | 29 | # For support requests 30 | 31 | Please tag support requests with the 'Support' label. 32 | -------------------------------------------------------------------------------- /readme.md: -------------------------------------------------------------------------------- 1 | # Page to wireframe 2 | 3 | A chrome extension to take a live webpage and make it look like a wireframe. [Available in the Chrome web store](https://chrome.google.com/webstore/detail/page-to-wireframe/djbpbelpckcfamdlkfhipkkadnanmkci) 4 | 5 | ![What a github page looks like wireframed](https://github.com/ao5357/page-to-wireframe/raw/master/icons/screenshot.png) 6 | 7 | ## Why 8 | 9 | I make websites, and sometimes I want to make a site first, then demonstrate its micro-IA separately, without showing a 10 | huge level of detail or design fidelity. 11 | 12 | This extension lets you click a button and have everything on the page appear low-fidelity. You can then 13 | take screenshots and perform other operations in order to export your wires. 14 | 15 | ## How 16 | 17 | It's written to be as asynchronous, event-driven, and resource-light as possible. 18 | 19 | ## Development 20 | 21 | If you'd like to fix bugs, add features, improve performance, or otherwise contribute to the project, 22 | I'm very open to pull requests. 23 | 24 | ### Install (unpacked) 25 | 26 | To install the development version of the extension, either clone the repo or use the ZIP download. 27 | At chrome://extensions make sure to check the "Developer mode" checkbox in the upper right-hand corner. 28 | After that, there will be a button to load an unpacked extension. Click that and select the folder 29 | containing the extension. It should then be ready to go! 30 | 31 | Thank you for your interest in Page to wireframe! 32 | -------------------------------------------------------------------------------- /icons/wireframe-icon.svg: -------------------------------------------------------------------------------- 1 | -------------------------------------------------------------------------------- /.github/SECURITY.md: -------------------------------------------------------------------------------- 1 | # Security Policy 2 | 3 | We take security seriously, and are committed to resolving security problems in a timely and responsible manner. 4 | 5 | Our security protocol for reported vulnerabilities follows the common industry best practices: 6 | 7 | * Allow confidential, non-public reporting of vulnerabilities so they may be resolved prior to public disclosure 8 | * Resolve reported vulnerabilities within 90 days, acknowledging that any un-resolved vulnerabilities may be responsibly 9 | disclosed to the public by the original reporter following 90 days, and that the reporter is within their rights to 10 | note in their disclosure that we did not resolve the vulnerability in the stated window 11 | * Disclose all reported vulnerabilities in a central place in a uniform fashion, and further communicate the resolution 12 | to potentially-affected third parties whenever possible 13 | * Especially when time is a factor, provide a quick patch or other method of resolving the vulnerability for community use 14 | 15 | We unfortunately do not have a bug bounty program at this time, but will do our best to acknowledge and otherwise-support 16 | any project contributor. 17 | 18 | ## Support 19 | 20 | For non-security bugs, requesting new features, etc., see [our Support docs](SUPPORT.md). 21 | 22 | ## Reporting a Vulnerability 23 | 24 | The project team and community take security seriously. We appreciate your efforts to responsibly disclose your findings, 25 | and will make every effort to acknowledge your contributions. 26 | 27 | To report a security issue, email [ao5357@gmail.com](mailto:ao5357@gmail.com) and format the subject line like so: 28 | 29 | ``` 30 | [SECURITY: severity: project-name] Short description of vulnerability 31 | ``` 32 | 33 | The maintainer will reply quickly to acknowledge receipt of the report. Within 24 hours they will follow up with more information 34 | about how the report will be handled and disclosed, with an estimate of the turnaround time. As we work on fixes and disclosures, 35 | we will keep you informed of our progress, and may reach out with requests for additional information if you are willing to 36 | volunteer it. 37 | 38 | Please report third-party vulnerabilities to the applicable third party. 39 | 40 | ## How we will handle a report 41 | 42 | When we receive a vulnerability report, we will assign it to a primary handler. This person will coordinate the fix and 43 | release process, involving the following steps: 44 | 45 | 1. Confirm the problem and determine the affected versions. 46 | 2. Audit code to find any potential similar problems. 47 | 3. Prepare fixes to apply to master, as well as quick patches as applicable 48 | 4. Communicate progress to reporter 49 | 5. Prepare for public disclosure 50 | 51 | ## Security disclosures 52 | 53 | The following vulnerabilities were reported to us on the dates in question, and their resolution within the window is noted. 54 | 55 | * (1970-01-01): \[no CVE#] -- Example vulnerability reported via email by "Fake Person" to maintainer. Codebase required 56 | a modification to the sample example section. Vulnerability is completely resolved as of version 0.0.x, with no mitigating 57 | factors. 58 | -------------------------------------------------------------------------------- /.github/CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 1 | # Code of Conduct 2 | 3 | ## Our Pledge 4 | 5 | In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making 6 | participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, 7 | differing ability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, 8 | race, religion, or sexual identity and orientation. 9 | 10 | ## Our Standards 11 | 12 | Examples of behavior that contributes to creating a positive environment include: 13 | 14 | * Using welcoming and inclusive language 15 | * Being respectful of differing viewpoints and experiences 16 | * Gracefully accepting constructive criticism 17 | * Focusing on what is best for the community 18 | * Showing empathy towards other community members 19 | 20 | Examples of unacceptable behavior by participants include: 21 | 22 | * The use of sexualized language or imagery and unwelcome sexual attention or advances 23 | * Trolling, insulting/derogatory comments, and personal or political attacks 24 | * Public or private harassment 25 | * Publishing others' private information, such as a physical or electronic address, without explicit permission 26 | * Other conduct which could reasonably be considered inappropriate in a professional setting 27 | 28 | ## Our Responsibilities 29 | 30 | Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate 31 | and fair corrective action in response to any instances of unacceptable behavior. 32 | 33 | Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, 34 | and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor 35 | for other behaviors that they deem inappropriate, threatening, offensive, or harmful. 36 | 37 | ## Scope 38 | 39 | This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project 40 | or its community. Examples of representing a project or community include using an official project e-mail address, posting 41 | via an official social media account, or acting as an appointed representative at an online or offline event. Representation 42 | of a project may be further defined and clarified by project maintainers. 43 | 44 | ## Enforcement 45 | 46 | Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at 47 | [ao5357@gmail.com](mailto:ao5357@gmail.com). The project team will review and investigate all complaints, and will respond 48 | in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with 49 | regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately. 50 | 51 | Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent 52 | repercussions as determined by other members of the project's leadership. 53 | 54 | ## Attribution 55 | 56 | This Code of Conduct is adapted from the [Contributor Covenant](http://contributor-covenant.org), version 1.4, available 57 | at [http://contributor-covenant.org/version/1/4](http://contributor-covenant.org/version/1/4/) 58 | -------------------------------------------------------------------------------- /.github/SUPPORT.md: -------------------------------------------------------------------------------- 1 | # Support 2 | 3 | Thank you for your interest in this project! What follows are some instructions for getting project support. 4 | 5 | For both bug reports and feature requests, the main guidelines for submitting are in the [issue template](ISSUE_TEMPLATE.md), 6 | so this document is mostly extra detail as applicable. 7 | 8 | We will _thank everyone who submits an issue_ to the project queue, and are likely to throw in some emoji reacts too. Beyond 9 | that, we reserve the right to close and reject any issue. In the vast majority of cases we will provide reasoning for closing 10 | in the comment thread before doing so. 11 | 12 | Our target for an initial response to an issue is within 24 hours. Once an issue is open, the turn-around target for comments 13 | and pull requests goes to the one-week standard as outlined in [the contributing documentation](CONTRIBUTING.md). 14 | 15 | ## Security note 16 | 17 | If you find a serious security vulnerability ("zero day"), please contact the project maintainer directly 18 | rather than submitting an issue into the queue. We take all security issues seriously, and will address and disclose all 19 | reports within 90 days. More information about security can be found in our [security documentation](SECURITY.md). 20 | 21 | ## Code of conduct 22 | 23 | All support requests and communication surrounding them is subject to [our code of conduct](CODE_OF_CONDUCT.md). We're 24 | nice folks that will be nice to you by default. 25 | 26 | ## Before submitting an issue... 27 | 28 | Please search the issues before submitting a new issue, in case there's already a report/request that's the same or similar 29 | to the one you're looking to open. 30 | 31 | If you do submit a duplicate issue, no worries; we will likely close your issue and provide a link to the existing one for 32 | continuing the thread. 33 | 34 | ## Issue types 35 | 36 | The issues we accept and seek fall into three categories, outlined below: bug reports, enhancement requests, and support 37 | requests. 38 | 39 | ### Bug reports 40 | 41 | A _bug report_ is an issue submitted to the project issue queue that a) explains how the project can be reasonably expected 42 | to behave, and b) demonstrates that the project does not behave that way. 43 | 44 | Resolution of a bug report can be either a fix that makes the project work in the expected manner, or additional documentation 45 | within the project that explains why the reported behavior occurs, what to do if it's problematic, and ideally why it stays 46 | the way it is. 47 | 48 | A _good_ bug report issue should include the following: 49 | 50 | 1. Which OS/Browser/stack and other applicable technologies are you using? 51 | 2. What steps (URLs are great here whenever possible) can you follow (given 1) to replicate the problem? 52 | 3. What is the expected result of following step 2? 53 | 4. What happens instead? 54 | 5. Are you willing to try and fix it yourself as a contributor? 55 | 56 | Please tag bug reports with the 'Bug' label. 57 | 58 | ### Enhancement requests 59 | 60 | An _enhancement request_ differs from a bug report in that it's an issue in the queue where a) the project does not have 61 | functionality or content to solve a particular user problem, but b) could in the future with some additional community work. 62 | 63 | Resolution of an enhancement request can be a pull request that adds the new functionality or content, thereby completing 64 | the enhancing of the project. On the other hand, an enhancement outside of the project's agreed-upon scope or otherwise 65 | outside of the project's desired range of acceptability may be rejected with a note reflecting such. 66 | 67 | When requesting an enhancement to the project, please provide some semblance of the following: 68 | 69 | * What exactly should the enhancement be? 70 | * Why should this be an enhancement to this project rather than the userspace? 71 | * What other projects have similar functionality or content? What makes these implementations cool? 72 | * Who benefits from this enhancement? 73 | * What documentation needs follow from this enhancement? 74 | * Is backwards-compatibility a concern? 75 | * Is additional test coverage required? 76 | * Are you willing to try and create the enhancement yourself as a contributor? 77 | 78 | Please tag enhancement requests with the 'Enhancement' label. 79 | 80 | ### Support requests 81 | 82 | In contrast to other open source projects, we're happy to field your questions and requests for general support in our issue 83 | queue! 84 | 85 | A _support request_ differs from both bug reports and enhancement requests in that a) the person reporting the issue is unable 86 | to make the project do a particular thing, but b) believes that the community can give them guidance to solve their problem. 87 | 88 | Support requests are resolved when the user's question is answered. Ideally, the request also yields improvements to the 89 | project documentation so that future users have a source for solving their issue without having to ask. 90 | 91 | **Note**: since support requests can take a lot of time and get repetitive, we cannot provide time guarantees for responses. 92 | We are also more likely to close support requests without necessarily resolving them, though we always strive to document the 93 | reason behind closing issues before doing so. 94 | 95 | Please tag support requests with the 'Support' label. 96 | -------------------------------------------------------------------------------- /css/styles.css: -------------------------------------------------------------------------------- 1 | /** 2 | * @file 3 | * Styles to make the page look like a wireframe. 4 | */ 5 | 6 | /** 7 | * CSS Custom properties for colors and other variables. 8 | */ 9 | :root { 10 | --color--black: #282829; 11 | --color--grey-dark: #58595B; 12 | --color--grey: #58595B; 13 | --color--grey-light: #f5f5f5; 14 | --color--white: #fff; 15 | } 16 | 17 | /** 18 | * Fonts imported early and directly. 19 | * 20 | * Only include fonts that are known to be used, since each is an asset to load. 21 | * font-display: swap; is used to prevent text from being hidden on load. 22 | * We list src in preference order: local, woff2, then woff 23 | * 24 | * @see https://google-webfonts-helper.herokuapp.com/fonts 25 | */ 26 | @font-face { 27 | font-display: swap; 28 | font-family: 'Redacted script'; 29 | font-style: normal; 30 | font-weight: 300; 31 | src: local('Redacted script'), 32 | url('chrome-extension://__MSG_@@extension_id__/css/fonts/redacted/redacted-script-light.woff2') format('woff2'); 33 | } 34 | @font-face { 35 | font-display: swap; 36 | font-family: 'Redacted script'; 37 | font-style: normal; 38 | font-weight: 400; 39 | src: local('Redacted script'), 40 | url('chrome-extension://__MSG_@@extension_id__/css/fonts/redacted/redacted-script-regular.woff2') format('woff2'); 41 | } 42 | @font-face { 43 | font-display: swap; 44 | font-family: 'Redacted script'; 45 | font-style: normal; 46 | font-weight: 500; 47 | src: local('Redacted script'), 48 | url('chrome-extension://__MSG_@@extension_id__/css/fonts/redacted/redacted-script-bold.woff2') format('woff2'); 49 | } 50 | 51 | /** 52 | * Font family declarations, all in one place and early. 53 | * 54 | * Let's keep all font-family calls right here, so it's manageable. Even classes 55 | * if necessary. 56 | */ 57 | html, 58 | button, 59 | input, 60 | select, 61 | textarea { 62 | font-family: "Redacted script", Arial, sans-serif !important; 63 | } 64 | 65 | body, 66 | .font-family--primary, 67 | *, 68 | html body * { 69 | font-family: "Redacted script", Arial, sans-serif !important; 70 | } 71 | 72 | /** 73 | * Often the headings and other sparing elements take a second font family. 74 | * 75 | * CSSLint and other tools might squawk at double-declaring tags, but this 76 | * puts all the font-family declarations in one place, which feels good. 77 | */ 78 | h1, 79 | h2, 80 | h3, 81 | h4, 82 | h5, 83 | h6, 84 | label, 85 | th, 86 | .font-family--secondary, 87 | .menu--main { 88 | font-family: "Redacted script", Arial, Helvetica, sans-serif !important; 89 | } 90 | 91 | /** 92 | * Some sites have Monospace text for code samples and the like. 93 | */ 94 | code, 95 | kbd, 96 | pre, 97 | samp, 98 | .font-family--monospace { 99 | font-family: "courier new", monospace; 100 | } 101 | 102 | /** 103 | * Declarations for all elements. 104 | */ 105 | * { 106 | 107 | } 108 | 109 | /** 110 | * HTML root element. Doesn't take all styles. 111 | */ 112 | html, body { 113 | background: #fff; 114 | color: #333; 115 | filter: grayscale(1); 116 | } 117 | 118 | /** 119 | * The body tag should take the site's universal styles. 120 | * 121 | * rem is based on this font-size dec, so only change if you're sure about the 122 | * type scale. 123 | * The body line-height should be one of only a handful of [unitless] line-height 124 | * declarations in the CSS codebase. 125 | */ 126 | body { 127 | background: #fff; 128 | color: var(--color--grey-dark); 129 | scroll-behavior: smooth; 130 | } 131 | body > * { 132 | font-size: 1.35em; 133 | } 134 | 135 | a { 136 | text-decoration: underline !important; 137 | } 138 | 139 | h1:before { 140 | content: '

: '; 141 | font-family: Arial, Helvetica, sans-serif !important; 142 | font-size: 1rem; 143 | font-weight: bold; 144 | } 145 | h2:before { 146 | content: '

: '; 147 | font-family: Arial, Helvetica, sans-serif !important; 148 | font-size: 1rem; 149 | font-weight: bold; 150 | } 151 | h3:before { 152 | content: '

: '; 153 | font-family: Arial, Helvetica, sans-serif !important; 154 | font-size: 1rem; 155 | font-weight: bold; 156 | } 157 | h4:before { 158 | content: '

: '; 159 | font-family: Arial, Helvetica, sans-serif !important; 160 | font-size: 1rem; 161 | font-weight: bold; 162 | } 163 | h5:before { 164 | content: '

: '; 165 | font-family: Arial, Helvetica, sans-serif !important; 166 | font-size: 1rem; 167 | font-weight: bold; 168 | } 169 | h6:before { 170 | content: '
: '; 171 | font-family: Arial, Helvetica, sans-serif !important; 172 | font-size: 1rem; 173 | font-weight: bold; 174 | } 175 | 176 | /** 177 | * iframes. 178 | * 179 | * Let's put borders on 'em, unless they don't need them in the theme. 180 | */ 181 | iframe { 182 | border: 1px solid var(--color--grey-light); 183 | } 184 | 185 | /** 186 | * Images. 187 | * 188 | * Since they have a max-width of 100%, the height: auto is truly important. 189 | * There's a render prop for old version of IE. 190 | * And the display and line-height props are normalize-ish for spacing. 191 | */ 192 | img { 193 | border: 2px var(--color--grey) solid; 194 | -ms-interpolation-mode: bicubic; 195 | display: inline-block; 196 | filter: grayscale(1) blur(3px); 197 | position: relative; 198 | } 199 | 200 | .has-background-image { 201 | background-image: url('chrome-extension://__MSG_@@extension_id__/css/images/background-image.jpg') !important; 202 | background-size: cover !important; 203 | } -------------------------------------------------------------------------------- /.github/CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | # Contributing 2 | 3 | ## Introduction 4 | 5 | Thank you for being part of this project's contributor community! We need the support of people like you in order to keep 6 | this open source movement alive. 7 | 8 | If you're looking for information about reporting bugs, requesting new features, etc., see [our Support docs](SUPPORT.md). 9 | 10 | Following these guidelines helps to communicate that you respect the time of the developers managing and developing this 11 | open source project. In return, they should reciprocate that respect in addressing your issue, assessing changes, and helping 12 | you finalize your pull requests. 13 | 14 | ## Contributions 15 | 16 | We are open to this project growing and adapting to meet its core user group's needs. As such, we are not specifically calling 17 | out which types of contributions we accept and which we are not seeking. Instead, here is a list of "perennial favorites"; 18 | areas that are appreciated on any project: 19 | 20 | * Code style and formatting improvements 21 | * Documentation 22 | * Addition of new functionality 23 | * Enhancement of existing functionality 24 | * Better test coverage 25 | * Bugs as reported in the issue queue 26 | * Content, as applicable 27 | 28 | ## Code of conduct 29 | 30 | All contributions and communication surrounding contributing is subject to [our code of conduct](CODE_OF_CONDUCT.md). We're 31 | nice folks that will be nice to you by default. 32 | 33 | ## Code guidelines 34 | 35 | The following are considerations, rather than hard-and-fast rules, about the kinds of code changes this community values: 36 | 37 | * We prefer 'vanilla' solutions and remaining dependency-free by default 38 | * We get very happy when people want to improve _accessibility_ and front-end performance in the project 39 | * We like solutions that allow writing information once and using it in multiple places/contexts 40 | * We _love_ generalized documentation that can be used on this but also any other similar project 41 | * We **love** "just in time" documentation; notes that appear in the place you need them 42 | 43 | ## Pull requests 44 | 45 | Here's the nuts and bolts of it: 46 | 47 | 1. [Fork the repository](https://help.github.com/en/github/getting-started-with-github/fork-a-repo) 48 | 2. [Clone your fork to your machine](https://help.github.com/en/github/creating-cloning-and-archiving-repositories/cloning-a-repository) 49 | 3. (Optional, but [recommended](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/about-branches)) 50 | `git branch new-branch-name` and `git checkout new-branch-name` 51 | 4. Set up a development version, per the [README](../readme.md) 52 | 5. **Your work here** 53 | 6. `git commit -m "Brief description of the changes made"` 54 | 7. `git push origin new-branch-name` 55 | 8. [Make a pull request](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request) 56 | on this repository 57 | 9. Feel the praise and accolades pour in! 58 | 59 | Here are some things you may be wondering about: 60 | 61 | * You don't have to sign anything to participate 62 | * We appreciate all PRs and assess them all. You **don't need an existing issue** to submit a pull request 63 | * We don't care about commit message formatting, as long as the message is pretty good at describing the changes 64 | * We have a pull request template you will see, but are otherwise not concerned with pull request formatting as long as you 65 | give us the information we need 66 | * If you can do your work via GitHub's edit interface, we won't bat an eye accepting 100%-web changes. All the cloning, branching, 67 | and setting up a development environment in the PR instructions is there for most developers, not to tell you how to do 68 | good work 69 | * Don't worry about squashing or rebase-ing your commits, unless that's a thing you personally prefer 70 | * If you're working on a PR based on an issue, please be sure to refer to the issue where applicable (PR definitely, commit message maybe) 71 | * PR reviewers will assess things like code-style adherence and other things, and will offer to fix that for you if you'd prefer. 72 | You are allowed to decide how active you are in the approval process. If we don't hear from you inside of a week, we may 73 | move ahead with changes without you 74 | * We're all about those emoji reactions, so hit the button liberally 75 | * Our threshold for giving contributors access to merge PRs, commit to master, etc. is relatively low, so if you would like 76 | to become a maintainer for this project just make a few PRs and ask nicely! 77 | 78 | ## Beginners 79 | 80 | Contributing to open source is both exciting and quite daunting! Here are some resources about what's going on, if this is 81 | your first open source project contribution on GitHub: 82 | 83 | * [How to contribute to open source](https://opensource.guide/how-to-contribute/) at Open Source Guides 84 | * [GitHub Guides](https://guides.github.com/) 85 | * ["Make a pull request"](http://makeapullrequest.com/) 86 | * [First timers only](https://www.firsttimersonly.com/) 87 | 88 | ## Review process 89 | 90 | When a pull request is submitted, the following happens: 91 | 92 | 1. The first maintainer to see the PR will thank the contributor in a comment and get happy with the emojis 93 | 2. The maintainer will assign themselves or another (subject matter expert) maintainer to shepherd it to merge 94 | 3. Anybody in the whole world is welcome to comment on the PR as long as they abide by the code of conduct. Reasonable 95 | feedback will always be seriously considered 96 | 4. The assigned party will review the purpose, formatting, and other characteristics of the PR, and provide feedback to the 97 | submitter as pertinent. If changes are required, the maintainer will offer to let the submitter do them, or to perform them 98 | on their own. The submitter has a week to respond with their choice 99 | 5. Once changes are applied, the PR is tested prior to merge. Additional testing and community review may be requested at 100 | the maintainer's discretion 101 | 6. The PR is ultimately **merged**, or in rare cases rejected 102 | 103 | Our target for any turn-around (communications and code changes) is one week. If a particular person in the PR thread is 104 | supposed to do something and they haven't responded in a week, other parties in the project community may pick up and carry the 105 | PR to closure. 106 | 107 | Here are some reasons that a pull request might be rejected rather than shepherded to merge: 108 | 109 | * **PR is a feature-request-in-disguise**: a small commit that requires most of the work still to be done 110 | * **Obvious intellectual property infringement**: we don't lie, nor do we steal 111 | * **Code of conduct violation**: if the submitter is mean, we'll give them fair warning. Repeated abuses will lead to rejection 112 | * **Lack of permissions**: if a submitter doesn't allow maintainer changes and goes incommunicado, we have no choice 113 | * **Big/fundamental changes**: big changes will be assessed and reviewed by the community to ensure they don't change the 114 | nature of the project in a way most of the community doesn't support 115 | 116 | ## Thanks again 117 | 118 | We really appreciate your willingness to contribute! 119 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | 2 | Apache License 3 | Version 2.0, January 2004 4 | http://www.apache.org/licenses/ 5 | 6 | TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 7 | 8 | 1. Definitions. 9 | 10 | "License" shall mean the terms and conditions for use, reproduction, 11 | and distribution as defined by Sections 1 through 9 of this document. 12 | 13 | "Licensor" shall mean the copyright owner or entity authorized by 14 | the copyright owner that is granting the License. 15 | 16 | "Legal Entity" shall mean the union of the acting entity and all 17 | other entities that control, are controlled by, or are under common 18 | control with that entity. For the purposes of this definition, 19 | "control" means (i) the power, direct or indirect, to cause the 20 | direction or management of such entity, whether by contract or 21 | otherwise, or (ii) ownership of fifty percent (50%) or more of the 22 | outstanding shares, or (iii) beneficial ownership of such entity. 23 | 24 | "You" (or "Your") shall mean an individual or Legal Entity 25 | exercising permissions granted by this License. 26 | 27 | "Source" form shall mean the preferred form for making modifications, 28 | including but not limited to software source code, documentation 29 | source, and configuration files. 30 | 31 | "Object" form shall mean any form resulting from mechanical 32 | transformation or translation of a Source form, including but 33 | not limited to compiled object code, generated documentation, 34 | and conversions to other media types. 35 | 36 | "Work" shall mean the work of authorship, whether in Source or 37 | Object form, made available under the License, as indicated by a 38 | copyright notice that is included in or attached to the work 39 | (an example is provided in the Appendix below). 40 | 41 | "Derivative Works" shall mean any work, whether in Source or Object 42 | form, that is based on (or derived from) the Work and for which the 43 | editorial revisions, annotations, elaborations, or other modifications 44 | represent, as a whole, an original work of authorship. For the purposes 45 | of this License, Derivative Works shall not include works that remain 46 | separable from, or merely link (or bind by name) to the interfaces of, 47 | the Work and Derivative Works thereof. 48 | 49 | "Contribution" shall mean any work of authorship, including 50 | the original version of the Work and any modifications or additions 51 | to that Work or Derivative Works thereof, that is intentionally 52 | submitted to Licensor for inclusion in the Work by the copyright owner 53 | or by an individual or Legal Entity authorized to submit on behalf of 54 | the copyright owner. For the purposes of this definition, "submitted" 55 | means any form of electronic, verbal, or written communication sent 56 | to the Licensor or its representatives, including but not limited to 57 | communication on electronic mailing lists, source code control systems, 58 | and issue tracking systems that are managed by, or on behalf of, the 59 | Licensor for the purpose of discussing and improving the Work, but 60 | excluding communication that is conspicuously marked or otherwise 61 | designated in writing by the copyright owner as "Not a Contribution." 62 | 63 | "Contributor" shall mean Licensor and any individual or Legal Entity 64 | on behalf of whom a Contribution has been received by Licensor and 65 | subsequently incorporated within the Work. 66 | 67 | 2. Grant of Copyright License. Subject to the terms and conditions of 68 | this License, each Contributor hereby grants to You a perpetual, 69 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 70 | copyright license to reproduce, prepare Derivative Works of, 71 | publicly display, publicly perform, sublicense, and distribute the 72 | Work and such Derivative Works in Source or Object form. 73 | 74 | 3. Grant of Patent License. Subject to the terms and conditions of 75 | this License, each Contributor hereby grants to You a perpetual, 76 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 77 | (except as stated in this section) patent license to make, have made, 78 | use, offer to sell, sell, import, and otherwise transfer the Work, 79 | where such license applies only to those patent claims licensable 80 | by such Contributor that are necessarily infringed by their 81 | Contribution(s) alone or by combination of their Contribution(s) 82 | with the Work to which such Contribution(s) was submitted. If You 83 | institute patent litigation against any entity (including a 84 | cross-claim or counterclaim in a lawsuit) alleging that the Work 85 | or a Contribution incorporated within the Work constitutes direct 86 | or contributory patent infringement, then any patent licenses 87 | granted to You under this License for that Work shall terminate 88 | as of the date such litigation is filed. 89 | 90 | 4. Redistribution. You may reproduce and distribute copies of the 91 | Work or Derivative Works thereof in any medium, with or without 92 | modifications, and in Source or Object form, provided that You 93 | meet the following conditions: 94 | 95 | (a) You must give any other recipients of the Work or 96 | Derivative Works a copy of this License; and 97 | 98 | (b) You must cause any modified files to carry prominent notices 99 | stating that You changed the files; and 100 | 101 | (c) You must retain, in the Source form of any Derivative Works 102 | that You distribute, all copyright, patent, trademark, and 103 | attribution notices from the Source form of the Work, 104 | excluding those notices that do not pertain to any part of 105 | the Derivative Works; and 106 | 107 | (d) If the Work includes a "NOTICE" text file as part of its 108 | distribution, then any Derivative Works that You distribute must 109 | include a readable copy of the attribution notices contained 110 | within such NOTICE file, excluding those notices that do not 111 | pertain to any part of the Derivative Works, in at least one 112 | of the following places: within a NOTICE text file distributed 113 | as part of the Derivative Works; within the Source form or 114 | documentation, if provided along with the Derivative Works; or, 115 | within a display generated by the Derivative Works, if and 116 | wherever such third-party notices normally appear. The contents 117 | of the NOTICE file are for informational purposes only and 118 | do not modify the License. You may add Your own attribution 119 | notices within Derivative Works that You distribute, alongside 120 | or as an addendum to the NOTICE text from the Work, provided 121 | that such additional attribution notices cannot be construed 122 | as modifying the License. 123 | 124 | You may add Your own copyright statement to Your modifications and 125 | may provide additional or different license terms and conditions 126 | for use, reproduction, or distribution of Your modifications, or 127 | for any such Derivative Works as a whole, provided Your use, 128 | reproduction, and distribution of the Work otherwise complies with 129 | the conditions stated in this License. 130 | 131 | 5. Submission of Contributions. Unless You explicitly state otherwise, 132 | any Contribution intentionally submitted for inclusion in the Work 133 | by You to the Licensor shall be under the terms and conditions of 134 | this License, without any additional terms or conditions. 135 | Notwithstanding the above, nothing herein shall supersede or modify 136 | the terms of any separate license agreement you may have executed 137 | with Licensor regarding such Contributions. 138 | 139 | 6. Trademarks. This License does not grant permission to use the trade 140 | names, trademarks, service marks, or product names of the Licensor, 141 | except as required for reasonable and customary use in describing the 142 | origin of the Work and reproducing the content of the NOTICE file. 143 | 144 | 7. Disclaimer of Warranty. Unless required by applicable law or 145 | agreed to in writing, Licensor provides the Work (and each 146 | Contributor provides its Contributions) on an "AS IS" BASIS, 147 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or 148 | implied, including, without limitation, any warranties or conditions 149 | of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A 150 | PARTICULAR PURPOSE. You are solely responsible for determining the 151 | appropriateness of using or redistributing the Work and assume any 152 | risks associated with Your exercise of permissions under this License. 153 | 154 | 8. Limitation of Liability. In no event and under no legal theory, 155 | whether in tort (including negligence), contract, or otherwise, 156 | unless required by applicable law (such as deliberate and grossly 157 | negligent acts) or agreed to in writing, shall any Contributor be 158 | liable to You for damages, including any direct, indirect, special, 159 | incidental, or consequential damages of any character arising as a 160 | result of this License or out of the use or inability to use the 161 | Work (including but not limited to damages for loss of goodwill, 162 | work stoppage, computer failure or malfunction, or any and all 163 | other commercial damages or losses), even if such Contributor 164 | has been advised of the possibility of such damages. 165 | 166 | 9. Accepting Warranty or Additional Liability. While redistributing 167 | the Work or Derivative Works thereof, You may choose to offer, 168 | and charge a fee for, acceptance of support, warranty, indemnity, 169 | or other liability obligations and/or rights consistent with this 170 | License. However, in accepting such obligations, You may act only 171 | on Your own behalf and on Your sole responsibility, not on behalf 172 | of any other Contributor, and only if You agree to indemnify, 173 | defend, and hold each Contributor harmless for any liability 174 | incurred by, or claims asserted against, such Contributor by reason 175 | of your accepting any such warranty or additional liability. 176 | 177 | END OF TERMS AND CONDITIONS 178 | 179 | APPENDIX: How to apply the Apache License to your work. 180 | 181 | To apply the Apache License to your work, attach the following 182 | boilerplate notice, with the fields enclosed by brackets "[]" 183 | replaced with your own identifying information. (Don't include 184 | the brackets!) The text should be enclosed in the appropriate 185 | comment syntax for the file format. We also recommend that a 186 | file or class name and description of purpose be included on the 187 | same "printed page" as the copyright notice for easier 188 | identification within third-party archives. 189 | 190 | Copyright [yyyy] [name of copyright owner] 191 | 192 | Licensed under the Apache License, Version 2.0 (the "License"); 193 | you may not use this file except in compliance with the License. 194 | You may obtain a copy of the License at 195 | 196 | http://www.apache.org/licenses/LICENSE-2.0 197 | 198 | Unless required by applicable law or agreed to in writing, software 199 | distributed under the License is distributed on an "AS IS" BASIS, 200 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 201 | See the License for the specific language governing permissions and 202 | limitations under the License. 203 | -------------------------------------------------------------------------------- /css/fonts/redacted/redacted-regular.svg: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 | 34 | 35 | 36 | 37 | 38 | 39 | 40 | 41 | 42 | 43 | 44 | 45 | 46 | 47 | 48 | 49 | 50 | 51 | 52 | 53 | 54 | 55 | 56 | 57 | 58 | 59 | 60 | 61 | 62 | 63 | 64 | 65 | 66 | 67 | 68 | 69 | 70 | 71 | 72 | 73 | 74 | 75 | 76 | 77 | 78 | 79 | 80 | 81 | 82 | 83 | 84 | 85 | 86 | 87 | 88 | 89 | 90 | 91 | 92 | 93 | 94 | 95 | 96 | 97 | 98 | 99 | 100 | 101 | 102 | 103 | 104 | 105 | 106 | 107 | 108 | 109 | 110 | 111 | 112 | 113 | 114 | 115 | 116 | 117 | 118 | 119 | 120 | 121 | 122 | 123 | 124 | 125 | 126 | 127 | 128 | 129 | 130 | 131 | 132 | 133 | 134 | 135 | 136 | 137 | 138 | 139 | 140 | 141 | 142 | 143 | 144 | 145 | 146 | 147 | 148 | 149 | 150 | 151 | 152 | 153 | 154 | 155 | 156 | 157 | 158 | 159 | 160 | 161 | 162 | 163 | 164 | 165 | 166 | 167 | 168 | 169 | 170 | 171 | 172 | 173 | 174 | 175 | 176 | 177 | 178 | 179 | 180 | 181 | 182 | 183 | 184 | 185 | 186 | 187 | 188 | 189 | 190 | 191 | 192 | 193 | 194 | 195 | 196 | 197 | 198 | 199 | 200 | 201 | 202 | 203 | 204 | 205 | 206 | 207 | 208 | 209 | 210 | 211 | 212 | 213 | 214 | 215 | 216 | 217 | 218 | 219 | 220 | 221 | 222 | 223 | 224 | 225 | 226 | 227 | 228 | 229 | 230 | 231 | 232 | 233 | 234 | 235 | 236 | 237 | 238 | 239 | 240 | 241 | 242 | 243 | 244 | -------------------------------------------------------------------------------- /css/fonts/redacted/redacted-script-regular.svg: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 | 34 | 35 | 36 | 37 | 38 | 39 | 40 | 41 | 42 | 43 | 44 | 45 | 46 | 47 | 48 | 49 | 50 | 51 | 52 | 53 | 54 | 55 | 56 | 57 | 58 | 59 | 60 | 61 | 62 | 63 | 64 | 65 | 66 | 67 | 68 | 69 | 70 | 71 | 72 | 73 | 74 | 75 | 76 | 77 | 78 | 79 | 80 | 81 | 82 | 83 | 84 | 85 | 86 | 87 | 88 | 89 | 90 | 91 | 92 | 93 | 94 | 95 | 96 | 97 | 98 | 99 | 100 | 101 | 102 | 103 | 104 | 105 | 106 | 107 | 108 | 109 | 110 | 111 | 112 | 113 | 114 | 115 | 116 | 117 | 118 | 119 | 120 | 121 | 122 | 123 | 124 | 125 | 126 | 127 | 128 | 129 | 130 | 131 | 132 | 133 | 134 | 135 | 136 | 137 | 138 | 139 | 140 | 141 | 142 | 143 | 144 | 145 | 146 | 147 | 148 | 149 | 150 | 151 | 152 | 153 | 154 | 155 | 156 | 157 | 158 | 159 | 160 | 161 | 162 | 163 | 164 | 165 | 166 | 167 | 168 | 169 | 170 | 171 | 172 | 173 | 174 | 175 | 176 | 177 | 178 | 179 | 180 | 181 | 182 | 183 | 184 | 185 | 186 | 187 | 188 | 189 | 190 | 191 | 192 | 193 | 194 | 195 | 196 | 197 | 198 | 199 | 200 | 201 | 202 | 203 | 204 | 205 | 206 | 207 | 208 | 209 | 210 | 211 | 212 | 213 | 214 | 215 | 216 | 217 | 218 | 219 | 220 | 221 | 222 | 223 | 224 | 225 | 226 | 227 | 228 | 229 | 230 | 231 | 232 | 233 | 234 | 235 | 236 | 237 | 238 | 239 | 240 | 241 | 242 | 243 | 244 | --------------------------------------------------------------------------------