SOFTWARE-CLINIC / featurebook

A command line tool (and Node.js library) for generating beautiful system specifications from Gherkin source files.
MIT License
40 stars 11 forks source link

Templates #58

Open airtonix opened 7 years ago

airtonix commented 7 years ago
Feature: `html` command

  Background:
    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
danielpacak commented 7 years ago

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?

airtonix commented 7 years ago

We've moved to using wintersmith-gherkin, I imagine you'd want to be doing something similar as that plugin

On Fri., 4 Nov. 2016, 17:26 Daniel Pacak, notifications@github.com wrote:

Hey @airtonix https://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?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/SOFTWARE-CLINIC/featurebook/issues/58#issuecomment-258357429, or mute the thread https://github.com/notifications/unsubscribe-auth/AADvKdW-27Akeu81O1_Nv0z9_lObz6ROks5q6tcOgaJpZM4Kl1aC .