You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add a one-click export option/button to export an article to a downloadable PDF document.
Background
Is your feature request related to a problem? Please describe:
Often with the Innovation Fund, we distribute multiple documents, agreements, and other resources at once when we bring in a new Innovation Fund start-up. Usually this is via Office 365 (Word) documents and PDFs. While it makes sense in this context to distribute files like .docx and .pdf, this method is also difficult to manage versioning and reliably maintaining a parent copy over time.
Describe the solution you'd like:
Some documents, which can be public, could be stored as editable source text in this repository. In the event where we create on-boarding packages tailored to a specific grantee, a one-click export of an article to a PDF enables parent copies to be maintained in GitHub, while also reliably fitting into this existing manual workflow.
Describe alternatives you've considered:
Not sure. This feature request requires more research on implementation before jumping in and writing code.
Details
The PDF export needs to be as simple as possible. The PDF metadata should also be derived from the document metadata defined in the article front matter. This needs research into the cleanest implementation possible. Ideally, it fits into the Hugo theme.
If it does not fit into the Hugo theme, we could explore some hacky ways of doing this in the Circle CI pipeline with pandoc, but that is a last-resort choice. It has messy design implications as a long-term feature, but addresses an immediate need.
Outcome
New workflow: Better document versioning and easier to keep parent copies of important documents distributed on a recurring basis
Old workflow: Distributing files at time of Innovation Fund on-boarding is still possible, fitting in with other documents we distribute unrelated to Open Source
The text was updated successfully, but these errors were encountered:
This commit updates the theme submodule to include an option to download
any page from the Open Source Inventory as a PDF. This was added by
@Idadelveloper in unicef/inventory-hugo-theme#9.
Furthermore, we plan to upstream this patch in the near future per the
discussion in gethugothemes/dot-hugo#167. Therefore,
this commit contributes to #33 but will not close the issue. We will
close#33 once the patch is merged upstream.
Signed-off-by: Justin W. Flory (he/him) [UNICEF Innovation] <jflory@unicef.org>
This commit updates the theme submodule to include an option to download
any page from the Open Source Inventory as a PDF. This was added by
@Idadelveloper in unicef/inventory-hugo-theme#9.
Furthermore, we plan to upstream this patch in the near future per the
discussion in gethugothemes/dot-hugo#167. Therefore,
this commit contributes to #33 but will not close the issue. We will
close#33 once the patch is merged upstream.
Signed-off-by: Justin W. Flory (he/him) [UNICEF Innovation] <jflory@unicef.org>
Summary
Add a one-click export option/button to export an article to a downloadable PDF document.
Background
Is your feature request related to a problem? Please describe:
Often with the Innovation Fund, we distribute multiple documents, agreements, and other resources at once when we bring in a new Innovation Fund start-up. Usually this is via Office 365 (Word) documents and PDFs. While it makes sense in this context to distribute files like
.docx
and.pdf
, this method is also difficult to manage versioning and reliably maintaining a parent copy over time.Describe the solution you'd like:
Some documents, which can be public, could be stored as editable source text in this repository. In the event where we create on-boarding packages tailored to a specific grantee, a one-click export of an article to a PDF enables parent copies to be maintained in GitHub, while also reliably fitting into this existing manual workflow.
Describe alternatives you've considered:
Not sure. This feature request requires more research on implementation before jumping in and writing code.
Details
The PDF export needs to be as simple as possible. The PDF metadata should also be derived from the document metadata defined in the article front matter. This needs research into the cleanest implementation possible. Ideally, it fits into the Hugo theme.
If it does not fit into the Hugo theme, we could explore some hacky ways of doing this in the Circle CI pipeline with
pandoc
, but that is a last-resort choice. It has messy design implications as a long-term feature, but addresses an immediate need.Outcome
The text was updated successfully, but these errors were encountered: