Hi there,
I just tried out Marked to open an md file with images, and the editor keeps randomly scrolling up & down. This is very annoying, as I'm confused about where I was. Here is the file. I didn't upload the images.
README.md# Example Feature Tour - Populated Data
Date: Example date
Setup used
- Local environment:
example-local-environment - Workspace:
/path/to/example/workspace - Frontend URL:
http://localhost:3000 - API URL:
http://localhost:8000 - Browser capture tool:
example-browser-tool - Database mirror: skipped for this example
- Debug user used for the tour:
example-user - Feature flags enabled locally for the tour user:
example_feature_flag,example_navigation_flag - Event source: local mock service at
http://localhost:9000
Synthetic data
I seeded a few local example entities and used a small local mock service for upcoming example events.
Example entities
| Name | Entity ID | Favorite for example-user? |
|---|---|---|
| Example One | example-entity-one |
Yes |
| Example Two | example-entity-two |
Yes |
| Example Three | example-entity-three |
No |
Example events
| Entity | Event | Date | Location |
|---|---|---|---|
| Example One | First sample event | Future date 1 | Sample venue, Sample city |
| Example Two | Second sample event | Future date 2 | Another venue, Another city |
| Example Three | Third sample event | Future date 3 | Remote location |
| Example One | Fourth sample event | Future date 4 | Online |
What the example changed
This example moves a discovery workflow into a navigation model that starts with events:
- The app exposes Events as the first top-level tab.
- The favorite-item event experience remains the Events landing page at
/example/overview. - The all-item event feed has its own route and page at
/example/all-events. - The favorite-events page links to View all when the all-events rollout flag is enabled.
- The all-events page adds secondary navigation and sort controls while preserving list tabs.
Tour
1. Events landing page: favorite item events
Path: /example/overview
The Events landing page focuses on upcoming events from favorited items. In this sample dataset, Example One and Example Two are favorites, so the page renders several favorite-event cards and a list-level feedback prompt.
2. All events page: chronological feed
Path: /example/all-events
The all-events feed is a separate page. It shows the secondary Favorite events / All events navigation and renders all sample events in chronological order, including an event from a non-favorite item.
3. All events page: favorites-first sorting
The same all-events page can prioritize favorited items. With Favorites first selected, favorite-item events move ahead of non-favorite-item events while still keeping the all-events context.
4. Existing favorite-item navigation remains available
Path: /example/favorites
The existing Favorite items page remains separate from event navigation. The seeded favorite items appear here as normal favorites, confirming that the Events-first change does not replace list navigation.
Local-only implementation notes
- The synthetic entities were inserted into a local-only test database.
- The API process was pointed at a local mock service so event calls resolve without external dependencies.
- The mock service lives in an example tools folder for this demo.
- The mock service can be kept running for interactive refreshes while testing the local page.
