jeblister / bulma Goto Github PK

As soon as I change the theme_variant, I get something ugly:

The Bulma logo is oversized

Hi,
I tested it in two different browsers in Linux. I just can't figure out how to fix it. Pic related:

Nice theme. Do you consider i18n? See e.g. alanorth/hugo-theme-bootstrap4-blog#16 and gohugoio/hugo#3255

Hello, just trying your theme with hugo v0.111.3+extended.
When tried the example site, Hugo complained with these two issues in baseof.html file.

/layouts/_default/baseof.html:5:12": execute of template failed: template: _default/list.html:5:12: executing "_default/list.html" at <.Hugo.Generator>: can't evaluate field Hugo in type *hugolib.pageState

To fix error for the moment, I have comment it out.

/layouts/_default/baseof.html:35:1": parse failed: template: _default/terms.html:35: undefined variable "$rsslink"

To fix error I decided to use $rssLink variable, and set it with the value of .RSSLINK from config.toml or the front matter.

Please find attached the diff patch baseof.diff.txt

All the best.

In #4 I noticed the README of this theme contained concepts I personally developed, and spent hundreds of hours upon to perfect. As I look at the README I can see most of the base and its feature set is After Dark reskinned with Bulma.

If you would like to continue using After Dark code please do either:

• Rework this theme as a direct fork of After Dark;
• Or apply the following license to any part of the code which uses my creative work and boldly link to After Dark in your README, in addition to including my ISC license in the LICENSE file in your repository. https://github.com/comfusion/after-dark/blob/master/LICENSE

/cc @digitalcraftsman @bep

There is bug in the sample config.toml file show here http://blog.elemnts.org/bulma/
This produces an error:
Error: While parsing config: (24, 3): The following key was defined twice: params.theme_variant

Hi,

Cloned the git repo shown here https://themes.gohugo.io/bulma/

And i'm seeing that the nav bar is blown up, looks exactly as what is seen here https://themes.gohugo.io/theme/bulma/ when i view in my local.

when i go here http://blog.elemnts.org/ i see the correct format of the site. how can i clone the hugo theme correctly so that there are no css issues?

See https://github.com/jeblister/bulma/blame/master/README.md#L9

where http://blog.elemnts.org leads to a for-sale domain landing page

According to this page https://gohugo.io/content-management/archetypes/#what-are-archetypes,
archetypes/post.md should be name posts.md

The summaries shown by the Bulma theme currently appear to be sub-optimal. They include the description from the post metadata, but also the first 70 words. Meanwhile Bulma does not insert the title automatically, so the first words of my document always also include the page title.

I currently have to workaround this by specifying a description and also making the document start with <!-- more --> in order to disable Hugo-defined summary splitting.

As a first step, I would prefer, if the Hugo-defined summary splitting would be disabled, if a description (better named summary) was provided.

The best solution would probably be, if Bulma would automatically insert the title as a heading and then allow people to use either the Hugo-defined summary splitting (first 70 words) or the user-defined summary splitting (split at the <!-- more --> tag).

Hello,

Bulma framework uses SASS along with npm (via package.json) as build tool. Its docs says that in order to:

Add your own colors, set new fonts, override Bulma styles...

one has to provide file with the following content:

// 1. Import the initial variables
@import "../sass/utilities/initial-variables"

// 2. Set your own initial variables
// Update blue
$blue: #72d0eb
// Add pink
$pink: #ffb3b3
// Add a serif family
$family-serif: "Merriweather", "Georgia", serif

// 3. Set the derived variables
// Use the new pink as the primary color
$primary: $pink
// Use the existing orange as the danger color
$danger: $orange
// Use the new serif family
$family-primary: $family-serif

// 4. Import the rest of Bulma
@import "../bulma"

but it's not clear to me if one e.g. names such file as master.sass, how to incorporate it into the present build system?

One way to customize Bulma theme is to use:

<link rel="stylesheet" href="{{ .Site.BaseURL}}/css/custom.css"> <!--Custom CSS-->

but I wonder how could I achieve to generate the above custom.css by using SASS mechanism within Bulma framework itself instead of overriding styles directly in CSS file?

Look here

The JavaScript file bulma.js looks for an element with css class nav-toggle which does not exist in the menu.html.