-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sara/tec 198 create a developer friendly onboarding page in the docs #1848
base: main
Are you sure you want to change the base?
Sara/tec 198 create a developer friendly onboarding page in the docs #1848
Conversation
❌ Deploy Preview for semgrep-docs-prod failed. Why did it fail? →
|
- Follow security practices set by security engineers | ||
|
||
:::tip Developer and AppSec role | ||
- If you are a developer responsible for your **own** security program in personal projects, see the **Quickstart** and **Core deployment** docs. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is "docs" too casual for us?
…oarding-page-in-the-docs
The following example is a simplified Semgrep rule that detects possible cross-site scripting vulnerabilities: | ||
|
||
|
||
```yaml showLineNumbers |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This 3rd example doesn't have an embedditor (it requires log in to view the rule). How do we feel about that? I could also convert the other two previous examples into plain YAML / source code rather than use the embedditor.
Thanks for improving Semgrep Docs 😀
Please ensure