Skip to content
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

Some silly improvements (decoration) in README.md #5974

Merged
merged 6 commits into from
Jan 10, 2025

Conversation

1hehaq
Copy link
Contributor

@1hehaq 1hehaq commented Jan 9, 2025

Proposed changes

Checklist

  • Pull request is created against the dev branch
  • All checks passed (lint, unit/integration/regression tests etc.) with my changes
  • I have added tests that prove my fix is effective or that my feature works
  • I have added necessary documentation (if appropriate)

Summary by CodeRabbit

  • Documentation
    • Reformatted README.md for improved readability
    • Enhanced visual hierarchy of sections
    • Improved formatting of language links and headings
    • Added emphasis to key phrases and sections
    • Introduced horizontal rules for better section separation

@auto-assign auto-assign bot requested a review from dogancanbakir January 9, 2025 19:59
Copy link
Contributor

coderabbitai bot commented Jan 9, 2025

Walkthrough

The pull request introduces comprehensive formatting improvements to the README.md file, focusing on enhancing document structure and visual presentation. The changes involve replacing HTML paragraph tags with <div> tags, adding backticks around language names, and implementing bold and italic styling for section headings. Horizontal rules have been introduced to improve section separation, and important phrases are now emphasized using bold formatting. The modifications aim to improve readability and visual hierarchy without changing the underlying content.

Changes

File Change Summary
README.md - Replaced <p> tags with <div> tags
- Added backticks around language names
- Enhanced section headings with bold/italic styles
- Introduced horizontal rules for section separation
- Emphasized key phrases with bold formatting

Poem

🐰 A README's dance of style and grace,
Markdown tags now find their place
Divs and backticks, bold and bright
Guiding readers with pure delight
A rabbit's touch of formatting flair! 🔤✨


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (4)
README.md (4)

Line range hint 30-39: Consider restructuring the feature list for better visual hierarchy.

While the bold emphasis on the introduction is good, the feature list could be improved by using consistent formatting.

Consider this structure for better readability:

-Simple YAML format for creating and customizing vulnerability templates.
-Contributed by thousands of security professionals to tackle trending vulnerabilities.
+- **Simple YAML format:** Create and customize vulnerability templates
+- **Community-driven:** Contributed by thousands of security professionals
🧰 Tools
🪛 LanguageTool

[grammar] ~30-~30: Did you mean “are” or “were”?
Context: ...white">



**Nuclei is a modern, high-performance vulnerabilit...

(SENT_START_NNS_IS)

🪛 Markdownlint (0.37.0)

22-22: null
Images should have alternate text (alt text)

(MD045, no-alt-text)


45-54: Table of Contents formatting is inconsistent.

The mix of backticks and italics in the ToC makes it harder to scan. Consider using a single style for better consistency.

-- [**`Get Started`**](#get-started)
-  - [_`1. Nuclei CLI`_](#1-nuclei-cli)
+- [**Get Started**](#get-started)
+  - [_1. Nuclei CLI_](#1-nuclei-cli)

74-78: Important notice formatting could be improved.

The important notice uses a mix of markdown and HTML table syntax, which might not render correctly on all platforms.

Consider using standard markdown blockquotes:

-> [!Important]
-> |**This project is in active development**. Expect breaking changes with releases. Review the release changelog before updating.|
-> |:--------------------------------|
-> | This project is primarily built to be used as a standalone CLI tool. **Running nuclei as a service may pose security risks.** It's recommended to use with caution and additional security measures. |
+> ⚠️ **Important**
+> 
+> This project is in active development. Expect breaking changes with releases. Review the release changelog before updating.
+>
+> This project is primarily built to be used as a standalone CLI tool. **Running nuclei as a service may pose security risks.** It's recommended to use with caution and additional security measures.
🧰 Tools
🪛 Markdownlint (0.37.0)

75-75: null
Tables should be surrounded by blank lines

(MD058, blanks-around-tables)


421-421: Fix hyphenation in compound adjective.

The term "AI powered" should be hyphenated when used as a compound adjective.

-**Try it online with our free AI powered Nuclei Templates Editor by**
+**Try it online with our free AI-powered Nuclei Templates Editor by**
🧰 Tools
🪛 LanguageTool

[uncategorized] ~421-~421: When ‘AI-powered’ is used as a modifier, it is usually spelled with a hyphen.
Context: ...process. Try it online with our free AI powered Nuclei Templates Editor by [**`clicki...

(POWERED_HYPHEN)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 18552bf and 4edf07e.

📒 Files selected for processing (1)
  • README.md (14 hunks)
🧰 Additional context used
🪛 LanguageTool
README.md

[grammar] ~30-~30: Did you mean “are” or “were”?
Context: ...white">



**Nuclei is a modern, high-performance vulnerabilit...

(SENT_START_NNS_IS)


[uncategorized] ~86-~86: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...sting workflows:_ - 50x faster scans - Large scale scanning with high accuracy - Integrati...

(EN_COMPOUND_ADJECTIVE_INTERNAL)


[uncategorized] ~421-~421: When ‘AI-powered’ is used as a modifier, it is usually spelled with a hyphen.
Context: ...process. Try it online with our free AI powered Nuclei Templates Editor by [**`clicki...

(POWERED_HYPHEN)


[style] ~457-~457: Consider using a different adverb to strengthen your wording.
Context: ...rs it used to take. This shift requires a completely different approach to tackling trending...

(COMPLETELY_ENTIRELY)


[grammar] ~459-~459: Did you mean “are” or “were”?
Context: ...vulnerabilities on the internet. Nuclei is now used and contributed by Fortune 500...

(SENT_START_NNS_IS)

🪛 Markdownlint (0.37.0)
README.md

105-105: null
Images should have alternate text (alt text)

(MD045, no-alt-text)


105-105: null
Images should have alternate text (alt text)

(MD045, no-alt-text)


58-58: null
Link fragments should be valid

(MD051, link-fragments)


75-75: null
Tables should be surrounded by blank lines

(MD058, blanks-around-tables)

🔇 Additional comments (2)
README.md (2)

3-12: Language selector improvements enhance readability.

The reorganization of language links using <div> and backticks improves visual consistency and accessibility.


633-633: Excellent addition of contributor avatar.

Adding the PR author's avatar to the contributors section is a nice touch that recognizes their contribution.


<p align="center">
<div align="center">

<a href="https://www.youtube.com/watch?v=b5qMyQvL1ZA&list=PLZRbR9aMzTTpItEdeNSulo8bYsvil80Rl&utm_source=github&utm_medium=web&utm_campaign=nuclei_readme" target="_blank"><img src="/static/nuclei-getting-started.png" width="350px"></a> <a href="https://www.youtube.com/watch?v=nFXygQdtjyw&utm_source=github&utm_medium=web&utm_campaign=nuclei_readme" target="_blank"><img src="/static/nuclei-write-your-first-template.png" width="350px"></a>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

Add alt text to images for accessibility.

Images are missing alt text, which is important for accessibility and SEO.

-<img src="/static/nuclei-getting-started.png" width="350px">
+<img src="/static/nuclei-getting-started.png" width="350px" alt="Nuclei Getting Started Guide Video Thumbnail">
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
<a href="https://www.youtube.com/watch?v=b5qMyQvL1ZA&list=PLZRbR9aMzTTpItEdeNSulo8bYsvil80Rl&utm_source=github&utm_medium=web&utm_campaign=nuclei_readme" target="_blank"><img src="/static/nuclei-getting-started.png" width="350px"></a> <a href="https://www.youtube.com/watch?v=nFXygQdtjyw&utm_source=github&utm_medium=web&utm_campaign=nuclei_readme" target="_blank"><img src="/static/nuclei-write-your-first-template.png" width="350px"></a>
<a href="https://www.youtube.com/watch?v=b5qMyQvL1ZA&list=PLZRbR9aMzTTpItEdeNSulo8bYsvil80Rl&utm_source=github&utm_medium=web&utm_campaign=nuclei_readme" target="_blank"><img src="/static/nuclei-getting-started.png" width="350px" alt="Nuclei Getting Started Guide Video Thumbnail"></a> <a href="https://www.youtube.com/watch?v=nFXygQdtjyw&utm_source=github&utm_medium=web&utm_campaign=nuclei_readme" target="_blank"><img src="/static/nuclei-write-your-first-template.png" width="350px" alt="Write Your First Nuclei Template Video Thumbnail"></a>
🧰 Tools
🪛 Markdownlint (0.37.0)

105-105: null
Images should have alternate text (alt text)

(MD045, no-alt-text)


105-105: null
Images should have alternate text (alt text)

(MD045, no-alt-text)

@GeorginaReeder
Copy link

Thanks for your contribution @1hehaq ! :)

Copy link
Member

@ehsandeep ehsandeep left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@1hehaq Thank you for making the README look better.

@ehsandeep ehsandeep merged commit 01668d7 into projectdiscovery:dev Jan 10, 2025
1 check passed
@ehsandeep ehsandeep removed the request for review from dogancanbakir January 10, 2025 12:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants