Areas for improvement

[fritz-c]

Here are the notes for areas that could be potentially worked on in the near future. There is a fair amount of overlap with existing issues, and I've tried to note issue numbers when possible. They're a bit rough, as I made them for myself, but I cleaned them up enough that I think they should be understandable on their own.

Docs

• Keyboard shortcuts are out of date https://formidable.com/open-source/spectacle/docs/advanced-concepts#keyboard-controls
• backgroundImage example values kind of hard to understand. Do you really need to wrap with url()? https://formidable.com/open-source/spectacle/docs/props#background
• "The last three props are for..." props probably reordered since then. https://formidable.com/open-source/spectacle/docs/api-reference#deck
• Deck props intro in general is hard to understand. Most people probably don't care about printer options. This will be one of the first references people find, as Deck is hugely important, so it should be streamlined and niche information be moved to an appropriate spot https://formidable.com/open-source/spectacle/docs/api-reference#deck
• References to PropTypes, when it's not even used in the source any more https://formidable.com/open-source/spectacle/docs/api-reference

Features / Improvements

• In presenter mode, show a message in the space of the next slide when you've reached the last slide (except when looping)
• Performance improvement for traversing several slides at once - right now it freezes up when you hold down the right arrow key.
• Presenter mode's notes vs slide preview halves could be resizable to fit user's preference.
• quick-find interface, riding on top of the existing CMD+K shortcut, making arbitrary text searchable using a fuzzy-search interface.
• Presenter mode's next slide is interactive when it doesn't need to be
• CodePane: would like to force line highlighting without having to work around its internal steps counter (Highlight lines in Code Pane simultaneous with other items. #1063)
• It's pretty tough to synchronize Step-based stuff: (useSteps and animations #1229)
• CodePane style customization (CodePane size not customizable #1053)
• Forward up the imperative ref (or maybe just key parts of it) from inside default-deck so users can use it to programmatically control the presentation navigation.
• Make <Appear>/<Stepper> children visible in exportMode (Show <Appear> children when exportMode is active #1111)
• Presenter mode's "Open a second browser tab at..." could include an anchor tag around the URL for easier opening.

Bugs

• CMD+K quick selector styling missing in exportMode
• appear+mdx stuff? Needs investigation
  • Md list appear #994
  • [Question] How to let list items "appear" with *.mdx  #968
  • Appear component does not function when placed in an MDX file #870
• SpectacleThemeOverrides does not allow for arbitrary keys, e.g. for "pink" or "header", even though our old codepen shows that being done - is that not the accepted practice any more?
• Since we use styled-components internally, it's hard to use styled-components in the user's own code (because of different ThemeContext, etc). Should it be a peer dependency? (Would be a breaking change, so it would need to be in v10)
• Presenter mode might typically show the next animation on a slide instead of the next slide entirely when animations in the slide are present. Presenter mode should show the next animation rather than the next slide #924 should have solved it but it regressed?