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
Certain presentation aspects of the SHFB output are subjective, and obviously we can't match everyone's individual tastes. It would be nice to have a live example of an alternative presentation style so developers can easily understand how to use the reference implementation of SHFB alongside their custom theme.
I propose packaging the "light" theme described in the comments of #49, #51, as well as the script modifications in #44 as an independent package that can be installed in a SHFB project to automatically use that output.
I am not sure this is possible in the exact form described here, but I wanted to create this issue so it doesn't get lost. 😄
The text was updated successfully, but these errors were encountered:
sharwell
changed the title
Consider distributing lightweight theme via NuGet
Consider distributing alternative "light" theme via NuGet
Mar 28, 2015
A NuGet package is probably overkill. Expanding on the existing topic about stock content replacement and moving it up to the root of the TOC is more than sufficient. It can be updated to include a walkthrough. I don't really want to add a NuGet package for something like this since then it has to be maintained and published with each new release if it changes.
Certain presentation aspects of the SHFB output are subjective, and obviously we can't match everyone's individual tastes. It would be nice to have a live example of an alternative presentation style so developers can easily understand how to use the reference implementation of SHFB alongside their custom theme.
I propose packaging the "light" theme described in the comments of #49, #51, as well as the script modifications in #44 as an independent package that can be installed in a SHFB project to automatically use that output.
I am not sure this is possible in the exact form described here, but I wanted to create this issue so it doesn't get lost. 😄
The text was updated successfully, but these errors were encountered: