nextcloud / nextcloud/notes

Overhaul Printing

Open
#936 11 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug enhancement needs discussion
Dominant language
JavaScript
Stars
738
Forks
162
Avg merge
6h 2m
Merged PRs (30d)
35

Description

Is your feature request related to a problem? Please describe.
I would like to see an overhaul to the printing-process. Currently the user has to know that "printing the page" will only print the note rendered in markdown. That is a bit limited and i can see some improvements.

Describe the solution you'd like
I would like to see dedicated printing-buttons somewhere. The Collectives-App has a button for that in each collective, but the notes app should have one on each note.
Additionally, i think it would be a good idea to have a "print all" button per folder, where we build a pdf from each note, making each note-title the chapter-title, and depending on the nesting of that file, subchapters. This allows for printing "whole books" similarly to the collectives app.

This would work with the current category-approach, but it would be trivially to understand if we would also switch to a folder based concept.

Additional Context:

There is https://www.npmjs.com/package/markdown-pdf. Alternatives were discussed in #179. It worked fine locally, and as per documentation, concatenation works aswell.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the current printing behavior and the alternatives discussed in #179; the issue names no files or tests, so first map the note and folder UI entry points. Done means dedicated printing for each note and a folder-level print-all flow that produces a PDF with note titles and nesting represented as chapters and subchapters.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, markdown
Domain
frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.