mirror of
https://github.com/bitwarden/help
synced 2026-02-07 12:03:16 +00:00
336e666357d7a79f8b6ceadc2ede50a4d309da24
* Add regex example to "Match detection for URIs" that is not broken I find it important that examples actually follow best practices. The current regex one is not. `^https://.*google\.com$` is an improper regex (as already pointed out because it also matches `malicious-site.com`) that is only there to show the weaknesses of regular expressions for this use case. I find such an example very good for this purpose but there should also be a "good example" that complements it. I found such a "good example" that I hope is more useful and has no unwanted loopholes. * Change wording from bad/good to unsafe/safe in regex match detection * Update uri-match-detection.md Co-authored-by: fred_the_tech_writer <69817454+fschillingeriv@users.noreply.github.com>
Bitwarden Help Center
The Bitwarden help center project is written using Jekyll, which is deployed at (https://bitwarden.com/help/).
Build/Run
Requirements
Run the following commands:
npm installnpm run build:watch
You can now access the help center at http://localhost:4009.
Ruby Gems
Jekyll Redirect From
To use jekyll-redirect-from add redirect_from to the YAML front-matter of your page or post. For example:
---
title: 10 Tips to Choosing a Password Manager for Your Team
layout: post
author: Gary Orenstein
redirect_from: /blog/10-tips-choosing-password-manager-for-teams/
---
Contribute
Article contributions are welcome! Please commit any pull requests against the master branch.
Description
Languages
HTML
68.6%
SCSS
15.8%
Ruby
8.4%
JavaScript
7.2%