Skip to content

docs: add Marked Responsive Images extension to documentation#3886

Open
ELowry wants to merge 2 commits intomarkedjs:masterfrom
ELowry:patch-1
Open

docs: add Marked Responsive Images extension to documentation#3886
ELowry wants to merge 2 commits intomarkedjs:masterfrom
ELowry:patch-1

Conversation

@ELowry
Copy link

@ELowry ELowry commented Feb 5, 2026

Description

This PR adds Marked Responsive Images to the Known Extensions list in the documentation.

This extension parses image filenames using a simple convention (e.g., image__400-300_800-600.jpg) to automatically generate srcset and width/height attributes, providing an easy way to handle responsive images without leaving standard Markdown syntax.

Note: I am the developer behind this extension. I felt it may be of use to others and did not find a suggested process for submitting extensions for consideration.

Changes

  • Added marked-responsive-images to the "Known Extensions" table.
Name Package Name Description
Marked Responsive Images marked-responsive-images Generate responsive (srcset) images based on structured filenames.

Checklist

  • Documentation change only
  • No breaking changes

Added the **Marked Responsive Images** to the **Known Extensions** list in the documentation.
@vercel
Copy link

vercel bot commented Feb 5, 2026

@ELowry is attempting to deploy a commit to the MarkedJS Team on Vercel.

A member of the Team first needs to authorize it.

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @ELowry, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request enhances the project's documentation by incorporating a new extension, 'Marked Responsive Images,' into the list of known extensions. This addition aims to inform users about a tool that streamlines the process of creating responsive images directly from Markdown, improving the overall utility and discoverability of relevant ecosystem tools.

Highlights

  • Documentation Update: The pull request adds the 'Marked Responsive Images' extension to the 'Known Extensions' list within the documentation.
  • New Extension Functionality: The 'Marked Responsive Images' extension automatically generates srcset and width/height attributes for images based on a simple filename convention, facilitating responsive image handling in standard Markdown.
Changelog
  • docs/USING_ADVANCED.md
    • Added an entry for 'Marked Responsive Images' to the 'Known Extensions' table, including its name, package name, and a brief description of its functionality.
Activity
  • The pull request was initiated by ELowry.
  • The author, ELowry, is also the developer of the 'Marked Responsive Images' extension and submitted it for consideration.
  • The PR description confirms that this is a documentation-only change with no breaking changes.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request adds a new extension, 'Marked Responsive Images', to the list of known extensions in the documentation. The change is straightforward and correctly placed alphabetically. I have one minor suggestion to improve consistency with the rest of the document.

|[Katex Code](https://github.com/UziTech/marked-katex-extension)|[`marked-katex-extension`](https://www.npmjs.com/package/marked-katex-extension)|Render [katex](https://katex.org/) code|
|[LinkifyIt](https://github.com/UziTech/marked-linkify-it)|[`marked-linkify-it`](https://www.npmjs.com/package/marked-linkify-it)|Use [linkify-it](https://github.com/markdown-it/linkify-it) for urls|
|[Mangle](https://github.com/markedjs/marked-mangle)|[`marked-mangle`](https://www.npmjs.com/package/marked-mangle)|Mangle mailto links with HTML character references|
|[Marked Responsive Images](https://github.com/ELowry/MarkedResponsiveImages)|[`marked-responsive-images`](https://www.npmjs.com/package/marked-responsive-images)|Generate responsive (`srcset`) images based on structured filenames.|
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

For consistency with other entries in this list, could you please remove the period at the end of the description? Most other descriptions in this table do not end with a period.

Suggested change
|[Marked Responsive Images](https://github.com/ELowry/MarkedResponsiveImages)|[`marked-responsive-images`](https://www.npmjs.com/package/marked-responsive-images)|Generate responsive (`srcset`) images based on structured filenames.|
|[Marked Responsive Images](https://github.com/ELowry/MarkedResponsiveImages)|[`marked-responsive-images`](https://www.npmjs.com/package/marked-responsive-images)|Generate responsive (`srcset`) images based on structured filenames|

Copy link
Author

@ELowry ELowry Feb 5, 2026

Choose a reason for hiding this comment

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

Agreed; I can also see that there are similar periods at the end of the descriptions for Base URL CJK Breaks GFM Heading ID Misskey-flavored Markdown and a few others.

Removed trailing periods for **Known Extensions** descriptions for better consistency.
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.

1 participant