It's easy to pick an icon in Notion, so any time I want to add a new category, I wouldn't have to add it in the source code.

It might be a good idea to introduce semantic versioning:

• Major - breaking changes, e.g. Notion template has been updated in a way that the app will be broken,
• Minor - features,
• Patch - chores, fixes, refactors, etc.

Consider using a "windowing" library like react-window to minimize the number of DOM nodes created if you are rendering many repeated elements on the page. Learn more. Also, minimize unnecessary re-renders using shouldComponentUpdate, PureComponent, or React.memo and skip effects only until certain dependencies have changed if you are using the Effect hook to improve runtime performance.

It'd be nice to have a possibility to filter the entries by tags/categories

Todos

• Create draft design - where should the filters be located?
• Create filtering mechanism - start small - single select only, multi select later on

Only entries with isPublished === true should be returned from API

Should be something like this:

const { ... } = useSWRInfinite<TimelineEntriesPage>( ... );

https://github.com/sitek94/hangman-game/tree/main/src/components/GitHubCorner

prefers-color-scheme media query is enough

Notes
Material UI provides a helper function to get a contrast text color.

theme.palette.getContrastText(color)

It's not a big deal at the moment, but the more entries, the more time it'll take to load them, so it should be addressed some time in the future.

• implement the logic / fetching mechanism
• style load more button
• create skeleton loader
• add "no more data" message