-
Notifications
You must be signed in to change notification settings - Fork 35
Can attached files be viewed in a separate browser window instead of just downloading? #280
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
Comments
With respect to download speeds it doesn't really matter if you're downloading the file or viewing it directly in your browser but I agree the usability aspect of being able to see it in the browser does make it easier to view. How were these files uploaded in the first place though? I see them in https://openmodelingfoundation.github.io/governance/working-groups/ -> https://github.com/openmodelingfoundation/openmodelingfoundation.github.io/files/6481459/standards_workflow.pdf and https://openmodelingfoundation.github.io/governance/charter/ -> https://github.com/openmodelingfoundation/openmodelingfoundation.github.io/files/6462528/OMF_org.pdf but don't see where / how they were added to the repository... |
create custom template for links that overrides default markdown rendering functionality for any pdfs on the site, open the file to a new tab in a google docs preview create hook for links that adds target=_blank to external links ending in .pdf https://gohugo.io/getting-started/configuration-markup/#link-with-title-markdown-example refs #280
I added some commits that open the diagram pdf files to a google docs preview in a new tab in the most recent commits https://openmodelingfoundation.github.io/governance/charter/ |
That's really nice. It will make it easier for people to see |
Those mysterious floating files should probably be tracked. Default behavior for static files in hugo should be to open in a new tab e.g. https://www.openmodelingfoundation.org/about/history/#planning-workshops so we'd be able to get rid of the google redirect Also with some relevance to #431, we should decide on where to keep static files ( |
Minor usability issue but one that can make life better for people behind firewalls or with slow internet. Currently, files attached to documents (e.g., standards workflow schematic attached to Standards WG text) simply download. Am I missing a markdown code to get them to open in a new browser window instead?
The text was updated successfully, but these errors were encountered: