Git Product home page Git Product logo

light-hugo's Introduction

light-hugo

This a responsive hugo theme using normalize.css (sass). It is material in nature and very bare boned. No javascript is used. Just straight up HTML and CSS.

Page support

There is support for the following types...

  • Posts
  • Pages

The posts will be treated as blogs and pages will be treated with a similar fashion. There is a GitHub css theme used for the markdown generated for posts and pages from markdown styles.

Config

The following config options are available for displaying custom content...

baseurl = "https://example.org/"
languageCode = "en-us"
theme = "light-hugo"

title = "Light Hugo"
author = "John Doe"
copyright = "© Copyright 2016 John Doe"

[Params]
  description = "Describe your website"
  email = "[email protected]"
  github = "tblyler"
  twitter = "tonyblyler"
  linkedin = "johndoe"
  facebook = "johndoe"
  youtube = "johndoe"
  logo = "/images/logo.png"

You can also append your own <head> and footer elements (just before the </body>). Do so by creating layouts/partials/foot.html and layouts/partials/head.html files in your hugo directory before compilation.

light-hugo's People

Contributors

alos-source avatar bep avatar tblyler avatar twillmz avatar

Stargazers

avatar avatar avatar avatar avatar avatar avatar avatar

Watchers

avatar avatar

Forkers

bep pebsconsulting twillmz pavolloffay kuleszdl mekkiamiri alos-source mortenkjarulff davidarchanjo mreferre

light-hugo's Issues

Typo in the "Archive" links?

Hey there! I am trying to play around with this theme as I am considering it for my migration from WP to a Hugo-bsed blog hosted on S3. It's all great except one tiny thing I am trying to determine if it's a bug or user-error.

If I deploy the blog + this theme.... the Archive hyperlink in both the footer.html and header.html files point to /post/. This gives me a 404. If I change manually the link in the browser to <myFQDN>/posts/ it works just fine.

Is it possible that you have a typo in those two files? Worst case I am planning on using a sed in my build instructions to s*/post/*/posts/ in those two files (I don't want to fork your repo) but it just feels wrong. If you feel this is a typo I am happy to submit a PR for this but I am checking if I am not missing something first.

Thanks!

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.