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
{{ message }}
This repository has been archived by the owner on Apr 19, 2022. It is now read-only.
Feature: `html` commandBackground:
Given a directory with Gherkin source files
Scenario: Generate HTML specification using a html template When I run `featurebook html --template ./features-template.html`
Then featurebook should generate output html using that template
Scenario: Generate HTML specification using conventionally present html template When there is a `<specdir>/.featurebook.tpl.html`
And I run `featurebook html`
Then featurebook should generate output html using the conventionally present template
The text was updated successfully, but these errors were encountered:
Hey @airtonix thank you for reporting this. Do you, by any chance, have an idea or preferences how a template will look like? I'm asking because I was thinking about moving CSS (LESS or SASS) to an external module (e.g. featurebook-theme-darkula) so that the featurebook html and featurebook serve will use the same style sheets. Now I have this styling code duplicated in both places. Next step would be to implement this style templating thing but there're different approaches to do that. For example, we can define some LESS or SASS variables that impact look&feel and compile to CSS on the fly. Any thoughts?
Hey @airtonixhttps://github.com/airtonix thank you for reporting this.
Do you, by any chance, have any idea or preferences how a template will
look like? I'm asking because I was thinking about moving CSS (LESS or
SASS) to an external module (e.g. featurebook-theme-darkula) so that the featurebook
html and featurebook serve will use the same style sheets. Now I have
this styling code duplicated in both places. Next step would be to
implement this style templating thing but there're different approaches to
do that. For example, we can define some LESS or SASS variables that impact
look&feel and compile to CSS on the fly. Any thoughts?
The text was updated successfully, but these errors were encountered: