Configuration options to enable less content

neil_neilzone commented

2026-03-20 12:12:50 +01:00

I am very much enjoying using BSSG!

I have been looking at ways of simplifying the displayed content, to remove some of the elements that I would prefer not to be there.

I can do this via hand-editing the build scripts, but it would be amazing to do this via a configuration option, so that I do not have the patch the scripts with each update.

On the index page, I am trying to:

suppress the menu list (Home Tags Archives RSS) at the top of the page (not in the footer)
suppress the blogpost description / generated excerpt (and even the functionality to generate an excerpt, since this uses processing power to generate something that I am just going to hide!)

so that it is a cleaner list.

On each post, I am trying to:

suppress the menu list (Home Tags Archives RSS)
suppress the "reading time" entry

I think that these are relatively straightforward, in the sense of being new configuration items, and corresponding if statements in the build scripts. I will see if I can make it work!

I am very much enjoying using BSSG! I have been looking at ways of simplifying the displayed content, to remove some of the elements that I would prefer not to be there. I can do this via hand-editing the build scripts, but it would be amazing to do this via a configuration option, so that I do not have the patch the scripts with each update. On the index page, I am trying to: * suppress the menu list (Home Tags Archives RSS) at the top of the page (not in the footer) * suppress the blogpost description / generated excerpt (and even the functionality to generate an excerpt, since this uses processing power to generate something that I am just going to hide!) so that it is a cleaner list. On each post, I am trying to: * suppress the menu list (Home Tags Archives RSS) * suppress the "reading time" entry I think that these are relatively straightforward, in the sense of being new configuration items, and corresponding if statements in the build scripts. I will see if I can make it work!

stefano commented

2026-03-20 19:33:36 +01:00

Owner

Interesting idea - if you want, I can have a look at it to make it permanent. If you can do it, I'll surely merge it

neil_neilzone commented

2026-03-20 20:35:58 +01:00

Author

I suspect that you would make a better job of it than I could, but I am mindful that I have sent quite a lot of feedback and suggestions this week!

A broader consideration might be separating layout from the build script, so that one could edit / arrange the HTML as one wished, like a template, without needing to edit a build script. But that is probably a much bigger undertaking.

I suspect that you would make a better job of it than I could, but I am mindful that I have sent quite a lot of feedback and suggestions this week! A broader consideration might be separating layout from the build script, so that one could edit / arrange the HTML as one wished, like a template, without needing to edit a build script. But that is probably a much bigger undertaking.

logullo commented

2026-03-25 01:11:29 +01:00

I am also enjoying using BSSG! And I too had a desire to change some of the displayed content. But I took a different approach:

I wanted to suppress the final menu item at the top of the page (“RSS”) but was okay with it appearing at the bottom.

A friend suggested I add this to my “my-styles.css” file:

nav a:last-child {
    display: none;
}

And sure enough… “RSS” was gone from the top of my pages.

A different approach; one that adds zero code complexity. Perhaps some of these CSS tricks could be added to the docs to address these sorts of requests.

I am also enjoying using BSSG! And I too had a desire to change some of the displayed content. But I took a different approach: I wanted to suppress the final menu item at the top of the page (“RSS”) but was okay with it appearing at the bottom. A friend suggested I add this to my “my-styles.css” file: ``` nav a:last-child { display: none; } ``` And sure enough… “RSS” was gone from the top of my pages. A different approach; one that adds zero code complexity. Perhaps some of these CSS tricks could be added to the docs to address these sorts of requests.

neil_neilzone commented

2026-03-25 06:58:10 +01:00

Author

I have used CSS in the same way to hide DOM elements for now, but it is a workaround, not a solution, since the DOM still contains those elements, and thus the page size is higher than it needs to be.

But yes, as a temporary workaround, I did the same.

I have used CSS in the same way to hide DOM elements for now, but it is a workaround, not a solution, since the DOM still contains those elements, and thus the page size is higher than it needs to be. But yes, as a temporary workaround, I did the same.

Rows
Columns

Configuration options to enable less content #53