Skip to content

docs: add feedback form#9159

Merged
TheAlexLichter merged 4 commits into
rolldown:mainfrom
TheAlexLichter:docs/feedback
Jun 19, 2026
Merged

docs: add feedback form#9159
TheAlexLichter merged 4 commits into
rolldown:mainfrom
TheAlexLichter:docs/feedback

Conversation

@TheAlexLichter

@TheAlexLichter TheAlexLichter commented Apr 19, 2026

Copy link
Copy Markdown
Collaborator

This PR adds the newly created vitepress-plugin-feedback-tracker plugin that I was working on and off over the past weeks.

It allows users to send feedback via the sidebar or on the bottom of the screen.

image image

TODO:

  • Test on the preview deployment
  • [] Test when live

@netlify

netlify Bot commented Apr 19, 2026

Copy link
Copy Markdown

Deploy Preview for rolldown-rs ready!

Name Link
🔨 Latest commit e07a12b
🔍 Latest deploy log https://app.netlify.com/projects/rolldown-rs/deploys/6a34f254c5c5a30008cd8bcf
😎 Deploy Preview https://deploy-preview-9159--rolldown-rs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
🤖 Make changes Run an agent on this branch

To edit notification comments on pull requests, go to your Netlify project configuration.

@sapphi-red

Copy link
Copy Markdown
Member

Nice! Here are the things I noticed:

  • I cannot change 👎 to 👍 if I missclicked.
  • When I click 👍 or 👎 on the side bar, the page is scrolled, but it's a bit laggy. It takes a bit until the scroll happens. It is a bit unclear why the scroll happened.
  • After selecting the reason on the sidebar, the bottom one still shows the reason selection. (i.e. the state is not synced)
  • In the source code, I see that Arrow* keys are handled. But I cannot select other categories by pressing those buttons.

@mdong1909

Copy link
Copy Markdown
Collaborator

@TheAlexLichter - to make things simpler, how about we only have the feedback form at the bottom of the page? Remove the sidebar form.

Was looking at other docs sites like nuxt and almost everyone only has one. Either bottom or sidebar.

@TheAlexLichter

TheAlexLichter commented Apr 26, 2026

Copy link
Copy Markdown
Collaborator Author

@sapphi-red Good call on these!

I cannot change 👎 to 👍 if I missclicked.

When I click 👍 or 👎 on the side bar, the page is scrolled, but it's a bit laggy. It takes a bit until the scroll happens. It is a bit unclear why the scroll happened.

In the source code, I see that Arrow* keys are handled. But I cannot select other categories by pressing those buttons.

Will fix these!

After selecting the reason on the sidebar, the bottom one still shows the reason selection. (i.e. the state is not synced)

That was originally on purpose but I see how this is confusing

@mdong1909

to make things simpler, how about we only have the feedback form at the bottom of the page? Remove the sidebar form. Was looking at other docs sites like nuxt and almost everyone only has one. Either bottom or sidebar.

What is the main concern? I think we can do that so we don't overload users but only for "short pages" so longer pages like https://rolldown.rs/reference/OutputOptions.cleanDir still have both 🤔

@mdong1909

Copy link
Copy Markdown
Collaborator
  1. Maintenance. We want this plugin/feature to be lightweight. Even if it won't be hard to fix issues in the future, it's still a context switch. Err towards simplicity.
  2. Ux. Half of sapphis comments are related to sidebar-bottom interaction. As a user, I'm thrown when inputting sidebar jumps me to the bottom. Real world experience is I'll have to then scroll back up to the part I was just at. Syncing state when a user can see both forms is another ux exercise.

The question is "what benefit do we get from including both the sidebar & bottom?"

It's possible we get a few more responses but I'd argue it doesn't justify the added complexity and maintenance surface. Looking ahead, I don't want you to spend much, if any, time maintaining this plugin. There's more impactful projects to work on. For an initial version, the simpler the better.

@TheAlexLichter

Copy link
Copy Markdown
Collaborator Author

Okay, then lets keep it only at the bottom. That way we don't have weird scrolling and can still show the email + option field.

@sapphi-red sapphi-red marked this pull request as draft May 19, 2026 09:15
@socket-security

socket-security Bot commented Jun 16, 2026

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Addednpm/​vitepress-plugin-feedback-tracker@​0.2.0-alpha.17510010089100

View full report

@TheAlexLichter

TheAlexLichter commented Jun 16, 2026

Copy link
Copy Markdown
Collaborator Author

Updated this PR:

  • Addressed all the feedback from before.
  • Switched the docs integration to vitepress-plugin-feedback-tracker@0.2.0-alpha.0
  • Removed the sidebar feedback widget so feedback only renders at the bottom of doc pages

@TheAlexLichter TheAlexLichter marked this pull request as ready for review June 16, 2026 08:02
@sapphi-red

Copy link
Copy Markdown
Member
repro-change.webm

It seems it breaks when changing the "Yes" / "No".

@TheAlexLichter

TheAlexLichter commented Jun 19, 2026

Copy link
Copy Markdown
Collaborator Author

Fixed in the latest version (but needs to wait for the min release age guard, adding a workaround)

# Conflicts:
#	pnpm-lock.yaml
#	pnpm-workspace.yaml
@sapphi-red

Copy link
Copy Markdown
Member

It seems it's still broken for me 🤔

@TheAlexLichter TheAlexLichter self-assigned this Jun 19, 2026
@TheAlexLichter

Copy link
Copy Markdown
Collaborator Author

It seems it's still broken for me 🤔

Just double checked. Yes -> Change (And same for no) seems fine now for me. The "validation changed" as in the video didn't happen.

Maybe there was something cached?

@sapphi-red

Copy link
Copy Markdown
Member

Hmm, it seems it's working now. I did reload with cache clear, but maybe I somehow got the old one 🤔
Sorry for the false flag.

@TheAlexLichter TheAlexLichter merged commit 24a925d into rolldown:main Jun 19, 2026
32 checks passed
@TheAlexLichter TheAlexLichter deleted the docs/feedback branch June 19, 2026 16:09
@rolldown-guard rolldown-guard Bot mentioned this pull request Jun 24, 2026
shulaoda added a commit that referenced this pull request Jun 24, 2026
## [1.1.3] - 2026-06-24

### 🐛 Bug Fixes

- `defer_drop` crashes the browser main thread (#9942) by @shulaoda
- camel-case: correct camel case for nested values (#9933) by @kb019
- cli: display --help options in camelCase (#9941) by @IWANABETHATGUY
- preserve used re-exports under preserveModules (#9122) (#9934) by @IWANABETHATGUY
- watch: make close reentrant in event callbacks (#9904) by @hyf0
- git for windows treats symlink files as regular files (#9915) by @AliceLanniste
- dev: cancel pending full reload on build error (#9903) by @h-a-n-a
- chunking: pass plugin meta to codeSplitting groups name function (#9267) by @Kyujenius
- dev: serve assets emitted during HMR/lazy compile (vite#22596) (#9815) by @h-a-n-a
- release: dry-run step no longer publishes binding packages (#9866) by @Boshen

### 🚜 Refactor

- rolldown_common: model ModuleId as a classified Path/Virtual/Bare enum (#9927) by @Boshen
- remove unused LegacyModuleIdx (#9872) by @shulaoda
- remove unused StmtInfos::get_namespace_stmt_info (#9870) by @shulaoda
- remove unused Module::as_external_mut (#9871) by @shulaoda
- remove unused EcmaAst::is_body_empty (#9869) by @shulaoda
- drop dead is_css_module handling in resolve_dependencies (#9867) by @shulaoda
- drop redundant with_commonjs on cjs source type (#9868) by @shulaoda

### 📚 Documentation

- clarify on drafting PRs (#9952) by @h-a-n-a
- update contribution guidelines (#9944) by @fubhy
- note Rust crates don't follow semver in AGENTS.md (#9905) by @IWANABETHATGUY
- add feedback form (#9159) by @TheAlexLichter

### ⚡ Performance

- utils: avoid allocation in default_sanitize_file_name for clean names (#9928) by @Boshen
- binding: box once-per-build futures before spawn_future (#9864) by @Boshen
- utils: avoid wasted allocation in legitimize_identifier_name (#9926) by @Boshen
- rolldown: fuse the canonical-name dedup and insert in the renamer (#9900) by @Boshen
- rolldown: probe the name map once in ConflictResolver::resolve (#9899) by @Boshen
- cut two heap allocations from wrapped ESM init finalize (#9901) by @Boshen
- rolldown_plugin_vite_reporter: hoist invariant out_dir prefix out of reporter loop (#9873) by @shulaoda
- drop throwaway Vec in wrapped esm init stmt (#9878) by @shulaoda
- borrow owner_filename in build-import-analysis AddDeps (#9874) by @shulaoda

### 🧪 Testing

- cover preserveModules named export via namespace re-export (#6010) (#9937) by @IWANABETHATGUY

### ⚙️ Miscellaneous Tasks

- deps: update napi to v3.9.4 (#9954) by @shulaoda
- reduce noise from CODEOWNERS for trival changes (#9953) by @h-a-n-a
- deps: update mimalloc-safe to 0.1.64 (#9950) by @shulaoda
- deps: update rollup submodule for tests to v4.62.2 (#9931) by @rolldown-guard[bot]
- deps: test mimalloc-safe upstream-mimalloc switch in CI (#9930) by @shulaoda
- rolldown_plugin_vite_build_import_analysis: remove unused v2 code path (#9917) by @shulaoda
- rolldown_plugin_vite_manifest: remove unused is_enable_v2 code path (#9916) by @shulaoda
- rolldown_plugin_vite_asset_import_meta_url: remove unexposed native vite plugin (#9896) by @shulaoda
- rolldown_plugin_vite_asset: remove unexposed native vite plugin (#9895) by @shulaoda
- rolldown_plugin_vite_css_post: remove unexposed native vite plugin (#9894) by @shulaoda
- rolldown_plugin_vite_css: remove unexposed native vite plugin (#9893) by @shulaoda
- rolldown_plugin_vite_html_inline_proxy: remove unexposed native vite plugin (#9892) by @shulaoda
- rolldown_plugin_vite_html: remove unexposed native vite plugin (#9891) by @shulaoda
- deps: update github actions (#9909) by @renovate[bot]
- deps: update rust crate oxc_sourcemap to v8.0.2 (#9910) by @renovate[bot]
- deps: update npm packages (#9912) by @renovate[bot]
- deps: update github actions to v7 (#9913) by @renovate[bot]
- deps: update rolldown-plugin-dts to ^0.26.0 (#9897) by @renovate[bot]
- remove rolldown_filter_analyzer crate (#9865) by @Boshen

### ❤️ New Contributors

* @fubhy made their first contribution in [#9944](#9944)

Co-authored-by: shulaoda <165626830+shulaoda@users.noreply.github.com>
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.

4 participants