-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Document Export Functionality #191
Comments
I want to try to solve this issue. Can I try it? |
@minai621 |
I think we have to research other approaches. I will search approaches in this weekend too! |
I've thought about it, and it seems appropriate to provide a demo-level solution to users by capturing from the client side, as long as we can resolve the CORS issue. In testing, I found that it perfectly supports markdown syntax except for applying style props directly in HTML. Images can be fetched via requests as long as they do not run into CORS issues. However, if we include images in the content, we'll need to upload them to an image server to handle CORS. We might need to choose between setting up an image server and installing Puppeteer in the Docker image. If we decide to use Puppeteer, I'll look for the latest libraries instead of the previously suggested html-to-pdf. |
What would you like to be added:
Currently, users can write Markdown documents in CodePair, but there is no functionality to export these documents to formats like PDF. It would be beneficial to introduce a document export feature that allows users to save their Markdown documents in various file formats.
Why is this needed:
Adding a document export functionality will enhance the usability of CodePair and provide users with the flexibility to save and share their work in different formats. This feature can improve the overall user experience and make it easier for users to collaborate and share their work outside of the platform.
Additional Information:
The text was updated successfully, but these errors were encountered: