Skip to content

Conversation

@gilles-peskine-arm
Copy link
Collaborator

@gilles-peskine-arm gilles-peskine-arm commented May 23, 2019

The PDF link was to a preview page. Link to the actual PDF instead.

The HTML link went to a third-party service that broke links. Link to Github Pages instead. This requires the HTML to be in /docs on the master branch. Alternatively we could change the repository settings to use a dedicated gh-pages branch — @Patater should we do this?

There is still a problem with the HTML: Sphinx puts resources (CSS, JS, images) in a directory with the hard-coded name _static but Github Pages ignores files whose name starts with an underscore. We need to find a solution for this, but in the meantime, unformatted HTML isn't as bad as missing content. #127 makes _static work.

Link to the PDF file, not to a page with an embedded PDF reader
htmlpreview.github.io breaks some links: in index.html viewed through
this service, the links that should go to from_doxygen.html are shown
as internal links, so the meat of the document is invisible.

Link to Github pages instead. This relies on the documentation being
available on the `master` branch of the mbed-crypto repository.

This has the added benefit of not depending on a third-party service.
@gilles-peskine-arm gilles-peskine-arm added bug Something isn't working needs: review The pull request is ready for review. This generally means that it has no known issues. labels May 23, 2019
@Patater
Copy link
Contributor

Patater commented May 24, 2019

I don't think we should use a gh-pages branch. I'd like to just merge once into our development branch, into its docs folder, and have github publish from there. This may mean we need to rename our development branch to master. That might not be a bad thing, since most other git-based projects use master as the name for the branch we use as our development branch.

Copy link
Contributor

@Patater Patater left a comment

Choose a reason for hiding this comment

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

LGTM

@Patater
Copy link
Contributor

Patater commented May 24, 2019

I've manually tested the links. They work!

@Patater Patater removed the needs: review The pull request is ready for review. This generally means that it has no known issues. label May 24, 2019
Copy link
Collaborator

@yanesca yanesca left a comment

Choose a reason for hiding this comment

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

LGTM.

@Patater Patater merged commit f479aae into ARMmbed:development May 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants