Skip to content
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

Embedding Content From Your Documentation, blog post #83

Closed
wants to merge 2 commits into from
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Binary file added _static/sphinx-hoverxref-demo.gif
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
71 changes: 71 additions & 0 deletions embedding-content-from-your-docs.rst
Original file line number Diff line number Diff line change
@@ -0,0 +1,71 @@
.. post:: June 23, 2020
:tags: embed, sphinx, sphinx-extension, api
:author: Manuel
:location: BCN

.. meta::
:description lang=en:
Read the Docs allows you to embed content from any of the projects we host.
This allows reuse of content across sites, making sure the content is always up to date.


Embedding Content From Your Documentation
=========================================

We are excited to announce the release of content embedding.
Copy link
Contributor

Choose a reason for hiding this comment

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

question: Rephrase first line?

If I understand correctly, we have an embed API at the moment, and readthedocs/readthedocs.org#8039 discusses improvements to it. Therefore, if I understand correctly, this API has been present for some time (can trace exactly how much), and and we are making it known for users. Am I understanding correctly? If so, the sentence "we announce the release of content embedding" is a bit misleading to me because we are not releasing anything now (it's been there for some months already). Perhaps it is leaving experimental state? Or we just want to describe how it works?

Sorry this looks like a super nitpick, but I'd love to have a bit more context to frame the review correctly.

This allows users to embed content from any of the projects we host, *anywhere*.
Our approach to embedding content is a very simple but powerful idea:
*return the content of a specific section from a particular document in a project*.

We have built an `Embed API`_ as the backend that powers this feature.
Copy link
Contributor

Choose a reason for hiding this comment

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

question: Shouldn't we decide on readthedocs/readthedocs.org#8107 first?

On top of this API,
we have built two improvements to the experience of our platform.

.. _Embed API: https://docs.readthedocs.io/en/latest/api/v2.html#get--api-v2-embed-

Contextualized tooltips on documentation pages
----------------------------------------------

Our first goal was adding extra context to a link within the same page.
This helps the reader understand a concept,
without switching context and jumping into another completely different page.
Copy link
Contributor

Choose a reason for hiding this comment

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

suggestion: make this sentence shorter

Suggested change
without switching context and jumping into another completely different page.
without having to jump into another completely different page.


Documentation is already full of links to additional content,
and with the new Embed API that can return that exact content,
we thought *let's add a tooltip with this content when the reader hovers the link!*
That's how `sphinx-hoverxref`_ was born.

``sphinx-hoverxref`` allows documentation authors to easily add these tooltips,
customize their style, and decide which elements will show tooltips.
We recommend `reading the docs`_ to see everything it can do.

.. figure:: /_static/sphinx-hoverxref-demo.gif

Example of ``sphinx-hoverxref`` on Read the Docs documentation.

.. _sphinx-hoverxref: https://sphinx-hoverxref.readthedocs.io/
.. _reading the docs: https://sphinx-hoverxref.readthedocs.io/

Inline help on our application website
Copy link
Contributor

Choose a reason for hiding this comment

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

thought: It took me a few seconds to understand what "our application website" meant.

I am not sure if there is a better term, or if we are using similar terminology in our docs that can be reused here.

--------------------------------------

Adding too much copy in your application can be overwhelming to users,
meaning they don't read it.
We try to keep the application copy minimal, and link out to documentation when appropriate.
Copy link
Contributor

Choose a reason for hiding this comment

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

question: What does "the application copy" mean in this context?

This pattern has worked fine over time, but it has the same problem of context switching to a completely different page.

Since we've started working on a new re-design of our entire application UI (more on this coming soon!),
we added the usage of the Embed API to add this extra documentation.
Copy link
Contributor

Choose a reason for hiding this comment

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

suggestion: Rephrase to avoid saying "add" twice in the same sentence?

By adding a tooltip to our documentation links,
we allow the user to maintain the content in our application but also learn more about the features they are using.

In summary
----------

If you liked the Embed API and you would like to embed content from your documentation anywhere,
you can `read its full documentation`_ to learn more about it.

.. _read its full documentation: https://docs.readthedocs.io/en/stable/guides/embedding-content.html

We think it's a super powerful feature and we encourage you to use the extension we built on top of it,
or even better, build your own and share them with us!
Copy link
Contributor

Choose a reason for hiding this comment

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

nitpick: The tone looks a bit informal here.

I wonder if we should make it a bit more formal, in line with other blog posts.