assemble/assemble-boilerplate-bootstrap

Some liquid tags are not being converted properly

Closed this issue · 2 comments

Currently in footer.hbs:

{{#is slug "customize"}}
    {{ assets }}/js/less.js"></script>
  {{/is}}
<script src="{{ assets }}/js/jszip.js"></script>
<script src="{{ assets }}/js/uglify.js"></script>
<script src="{{ assets }}/js/filesaver.js"></script>
<script src="{{ assets }}/js/raw-files.js"></script>
<script src="{{ assets }}/js/customizer.js"></script>

Should be this:

{{#is slug "customize"}}
<script src="{{ assets }}/js/less.js"></script>
<script src="{{ assets }}/js/jszip.js"></script>
<script src="{{ assets }}/js/uglify.js"></script>
<script src="{{ assets }}/js/filesaver.js"></script>
<script src="{{ assets }}/js/raw-files.js"></script>
<script src="{{ assets }}/js/customizer.js"></script>
{{/is}}

Currently in default.hbs

            <ul class="nav bs-sidenav">
              {{#is slug "getting-started" }}  {{> nav-getting-started }}
              {{/is}}
              {{#is slug "css" }}  {{> nav-css }}
              {{/is}}
              {{#is slug "components" }}  {{> nav-components }}
              {{/is}}
              {{#is slug "js" }}  {{> nav-javascript }}
              {{/is}}
              {{#is slug "customize" }}  {{> nav-customize }}
              {{/is}}


            </ul>

Could be this:

            <ul class="nav bs-sidenav">
              {{#is slug "getting-started" }}
                {{> nav-getting-started }}
              {{/is}}
              {{#is slug "css" }}
                {{> nav-css }}
              {{/is}}
              {{#is slug "components" }}
                {{> nav-components }}
              {{/is}}
              {{#is slug "js" }}
                {{> nav-javascript }}
              {{/is}}
              {{#is slug "customize" }}
                {{> nav-customize }}
              {{/is}}
            </ul>

I'm planning on creating a version of this with swig as well, that version should be a lot easier to maintain since swig should be able to compile everything "natively". I'll just create custom tags/filters for whatever functionality is missing. we'll keep this repo too

Cool, I'd be excited to see that when you start working on it. I'm currently using this to generate documentation for a highly customized version of BS3 at work. I've got a lot of other crazy regex in my grunt task that further strips, converts, and adds new content to the docs.