Without being able to see the full source code or website itself, it could be one of two things given the snippet you included. I know I'm late to the party, but I'm answering questions specifically...
1) It could either be a lack of DIV containers being properly opened and closed for the header segment, or if the server is missing assets. When comparing your snippet with the source code, I don't know if the two actually not there before the logo DIV container comment properly closing it out and opening a new one for the logo, or if they're not there because you simply didn't copy/paste that far, you should have:
<!-- Header -->
<div id="header">
<div id="nav-wrapper">
<!-- Nav -->
<nav id="nav">
<ul>
<li class="active"><a href="index.html">Homepage</a></li>
<li><a href="left-sidebar.html">Left Sidebar</a></li>
<li><a href="right-sidebar.html">Right Sidebar</a></li>
<li><a href="no-sidebar.html">No Sidebar</a></li>
</ul>
</nav>
</div>
<div class="container">
<!-- Logo -->
<div id="logo">
<h1><a href="#">Linear</a></h1>
<span class="tag">By TEMPLATED</span>
</div>
</div>
</div>
(Protip: If you want people to debug your code but you don't want to post everything, at least post the entirety of the segment in question, or at least make sure everything is closed out.)Given what's happened thus far, I doubt that's the case, however.
2) If they
are there in your code, the only other cause I can think of is a lack of additional assets not being properly loaded onto or by the server, specifically:
../js/skel.min.js
../js/skel-panels.min.js
../js/init.js
../css/skel-noscript.css
../css/style.css
../css/style-desktop.cssGiven how tiiny.site works, if you're only uploading the edited HTML file to their servers or flattened the directory structure to stick all the files in the same directory, there's your problem. You have to upload a ZIP file with all relevant files and folder structures included, structured like the ZIP file you downloaded of the template itself. Or, there could be directory or server issues.
Now, all this said, it's a template for a static website, which means no databases and no complex hosting. You're literally just delivering text and media files. Let me see if I can help you with some related tips that might make your life far, far easier, and lower the expected costs even further, and eliminate your need to try and deal with sketchy or bargain bin freebie hosting sites, even for prototyping.
1) You don't necessarily need a web server to test a static website. You can edit and open HTML files locally in any web browser, and if you did your SRC and HREF references properly, should function properly no matter where it's located.
2) You may already be in over your head if you're not comfortable with this level of HTML editing given how little you've actually edited in the actual quoted code, things that really should be edited and customized for your site. Responsive design websites are a bit more complex to deal with than old school, fixed format, HTML layouts. If you really want to edit by hand, be sure to use a text editor that supports coding, code highlighting, and can show you if you forgot to close something - something like
Notepad++ will help. Given you want a responsive site design that works on both desktop and mobile screens, and you would probably appreciate something far more WYSIWYG in usability and development, give
Mobirise a spin.
3) If you want a free "web server" to test static websites out on, or actually host the site for free because you're not looking at it being a huge traffic draw, look into
Github Pages, which includes custom domain support. Fortunately,
Mobirise can publish to Github directly, taking some of the guesswork out of it. No sketchy hosts this way, either. It also means you can do free hosting without a ton of ad links injected, or being locked into a proprietary editing system with no data/site portability to other hosts or ability to edit with other editors, like Wix and its ilk does.
4) If you find that you need to host a static website on a host that can handle more traffic than Github, look into
NearlyFreeSpeech.NET, which is the best PAYGO equivalent of cheap but reliable web hosting. Honestly, though,
Github can handle most smaller sites without a problem these days... especially if you pair it with CloudFlare handling your DNS. Also, don't bother with CPanel based hosts if you're running a static website, it's just unnecessary overhead and an additional layer of security vulnerabilities and hassles to deal with, especially with really cheap shared hosting providers using CPanel.
Good luck.
