Skip to content

docs: update PDF embed instructions#1432

Merged
sarina merged 3 commits into
openedx:mainfrom
open-craft:fox/update-pdf-editor
Apr 21, 2026
Merged

docs: update PDF embed instructions#1432
sarina merged 3 commits into
openedx:mainfrom
open-craft:fox/update-pdf-editor

Conversation

@Kelketek
Copy link
Copy Markdown
Contributor

@Kelketek Kelketek commented Apr 20, 2026

Description

This PR updates the PDF block creation instructions to reflect the revised interface that will be landing alongside the block in Verawood.

Supporting information

openedx/frontend-app-authoring#2916
Internal ticket: https://tasks.opencraft.com/browse/BB-10743

Testing instructions

Follow the setup instructions here to build and serve the documentation. Verify that the page works and looks right. You should find it here:

http://127.0.0.1:8000/educators/how-tos/course_development/exercise_tools/add_embedded_pdf.html

Rendered doc

https://docsopenedxorg--1432.org.readthedocs.build/en/1432/educators/how-tos/course_development/exercise_tools/add_embedded_pdf.html

@openedx-webhooks openedx-webhooks added open-source-contribution PR author is not from Axim or 2U core contributor PR author is a Core Contributor (who may or may not have write access to this repo). labels Apr 20, 2026
@openedx-webhooks
Copy link
Copy Markdown

Thanks for the pull request, @Kelketek!

This repository is currently maintained by @openedx/wg-maintenance-docs.openedx.org.

Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review.

🔘 Get product approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

  • If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
    • This process (including the steps you'll need to take) is documented here.
  • If it doesn't, simply proceed with the next step.
🔘 Provide context

To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

  • Dependencies

    This PR must be merged before / after / at the same time as ...

  • Blockers

    This PR is waiting for OEP-1234 to be accepted.

  • Timeline information

    This PR must be merged by XX date because ...

  • Partner information

    This is for a course on edx.org.

  • Supporting documentation
  • Relevant Open edX discussion forum threads
🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

Details
Where can I find more information?

If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

When can I expect my changes to be merged?

Our goal is to get community contributions seen and reviewed as efficiently as possible.

However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

  • The size and impact of the changes that it introduces
  • The need for product review
  • Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.

Copy link
Copy Markdown
Contributor

@samuelallan72 samuelallan72 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Kelketek 👍

Please also add a link to the jira ticket to the PR description.

  • I tested this: followed the test instructions
  • I read through the code
  • I checked for accessibility issues
  • Includes documentation


#. In the **Name** field, enter the name for the new component. This will be
displayed above the component as a title.
You may optionally specify a specific URL for your PDF by selecting
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a small nit, but there is a variant of specify 3 times in this sentence; dropping one feels less of a tongue twister. ;)

Suggested change
You may optionally specify a specific URL for your PDF by selecting
You may optionally specify a URL for your PDF by selecting

@Kelketek Kelketek force-pushed the fox/update-pdf-editor branch from f0c89b0 to 1a4e730 Compare April 21, 2026 14:41
@Kelketek
Copy link
Copy Markdown
Contributor Author

@sarina Since you reviewed the initial version, would you be up for reviewing this update now that the UI has been updated?

Copy link
Copy Markdown
Contributor

@sarina sarina left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you also update the image in the top of the doc (and remove the old file)?

Image

The new component is added to the unit with a default example PDF embedded.
.. image:: /_images/educator_references/pdf_editor.png
:alt: The PDF embed component in Studio.
:width: 400
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This width makes it super tiny in the rendered doc, I bet you could just remove this entirely because the source image is pretty small.

Image

:alt: The PDF embed component in Studio.
:width: 400

.. image:: /_images/educator_references/pdf_embed.png
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you please delete this outdated image as part of this PR?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This image isn't out of date-- only the authoring interface has changed, so the image at the top of the article is still good, and refers to the same file.

@Kelketek
Copy link
Copy Markdown
Contributor Author

@sarina I've addressed one note and responded to another. Please take another look. Thanks!

@sarina
Copy link
Copy Markdown
Contributor

sarina commented Apr 21, 2026

Thanks, could you ping me when all my comments are addressed?

@Kelketek
Copy link
Copy Markdown
Contributor Author

@sarina As far as I can tell, all of your notes are addressed. You asked for me to remove the width constraint on one of the images, which I have done. And you asked for me to remove an image, but that image is not out of date as it is of the unchanged learner interface, and so I do not want to remove it. The image was previously used twice in the article, and now is only used once at the top. Was there anything else you needed?

Copy link
Copy Markdown
Contributor

@sarina sarina left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry @Kelketek I had pending comments I didn't realize my bad!


The new component is added to the unit with a default example PDF embedded.
.. image:: /_images/educator_references/pdf_editor.png
:alt: The PDF embed component in Studio.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This alt text isn't very descriptive. With alt text, you should convey what is being visually represented so that a screenreader user can understand why you're including this image at all. Sometimes this ends up being pretty long and that's okay!

Eg, "The PDF embed component in Studio modal dialogue has a field to provide a file upload. It has a checkbox to show the PDF download link, and optional fields to provide the source document, as explained in the following steps in this tutorial"

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added your description, since it looked good to me.

the PDF embed block.

The new component is added to the unit with a default example PDF embedded.
.. image:: /_images/educator_references/pdf_editor.png
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: this file should be in educator_how-tos folder not educator_references

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done. I've moved the other image as well.

Copy link
Copy Markdown
Contributor

@sarina sarina left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great, sorry about the confusion and thanks for the changes!

@sarina sarina enabled auto-merge (squash) April 21, 2026 20:31
@Kelketek
Copy link
Copy Markdown
Contributor Author

@sarina The CI choked-- can you restart it? Thanks!

@sarina sarina merged commit 01a93d2 into openedx:main Apr 21, 2026
2 checks passed
@github-project-automation github-project-automation Bot moved this from Needs Triage to Done in Contributions Apr 21, 2026
@Kelketek Kelketek deleted the fox/update-pdf-editor branch April 21, 2026 22:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

core contributor PR author is a Core Contributor (who may or may not have write access to this repo). open-source-contribution PR author is not from Axim or 2U

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

4 participants