Custom Home Page broke Liebling theme index css

Themes
1

I made a custom home page and moved the normal home page to /news. With the only changed file in the theme being the added home page, the /news page(old home page) now has broken css, the slider being the noticeable part. I poked around a bit but I can’t gather why.

The site I am editing is live with these errors at https://serbc.ridvan.org.

I have also been having difficulty getting the normal post css to apply to the new home page’s body content. I’m not sure if this issue is theme specific, or if its an error with my handlebars syntax.

excerpt from my home.hbs for the homepage styling issue.

        {{#page}}
        <article>
            <div class="l-content">
                <div class="l-wrapper in-post" data-aos="fade-up" data-aos-delay="300">
                    <div class="l-post-content">
                        <div class="pos-relative js-post-content">
                            {{content}}
                        </div>
                    </div>
                </div>
            </div>
        </article>
        {{/page}}
2

It appears you have a space in your URL to the CSS file which is preventing that file from loading:

bahai-site-error-1
bahai-site-error-11755×810 118 KB

As a matter of fact… the same is true for multiple additional URLS as well…

bahai-site-loading-errors
bahai-site-loading-errors1430×542 173 KB

3

Thanks so much! It was my linter, and because I’m new to handlebars I thought, “thats weird syntax oh well…”

I had it set to format on save.

4

Sorry- so could you help me understand how these are supposed to be formatted? I thought the following would work…

<link rel="stylesheet" type="text/css" href="{{asset "css/home.css"}}" media="screen" />
<link rel="stylesheet" type="text/css" href="{{asset "css/listing.css"}}" media="screen" />
<link rel="stylesheet" type="text/css" href="{{asset "css/post.css"}}" media="screen" />

I got the following error uploading:

index.hbs: Parse error on line 135: ....js"}}"></script> {{/contentFor}} ----------------------^ Expecting 'EOF', got 'OPEN_ENDBLOCK'

Edit nvm, I just missed a similar error on the bottom.