Ideas for optimized print view
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.4k
- Forks
- 354
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 43
Description
Printing of decks is not working well - there is a issue for this: #752
This issue covers just a small part of the things that could be optimized in a print view - the problem that only the first page can be printed.
I think printing a deck is useful to archive it for example after a project has been finished.
So I think a optimized print view should cover this points:
- print on more than one pages (#752 )
- configurable number of columns for printing
- include descriptions and comments (configurable)
- don't print UI elements that are not useful in prints
- don't print avatars, use usernames insted
- don't print relative dates like "2 days" ago - use fixed date like 10.08.2021 for print.
What do you think about this suggestions?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading issue #752 and reviewing the existing print-view entry point. Compare the current output with each requested improvement: multiple pages, configurable columns and metadata, and removal or replacement of UI elements. Done would require an agreed scope and verification that the selected print options produce an archive-friendly deck.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100