What I want, instead of a “themes” section for discovering hugo, is something more like a builder. By this I mean, I select the features I want, check the box, and I get that generated. I want Categories, and Tags, and Images, and Slideshows. A header, a footer, a logo, a menu. Some themes have …

Sounds to me like what you want is to build your own theme. Much faster then having to piece things together IMO.

I would start by building your own theme by maybe re-purposing an existing minimalist theme. Or start from scratch with a lightweight CSS framework that provides a simple grid and built it up from there with what elements you need. Maybe use other themes you like as a guide and implement your favori…

This is what is so great about Wordpress and the Genesis layer by StudioPress. You can Very quickly and easily click a few things to add another sidebar box, or a slider, or and additional footer layer.

Hello, I’ve started to build something… in regard of a UI Builder with “block components”… and I am wondering about the frontend development of a CMS Admin though. What do you guys think would be great for the “backend of it”. I know there is a lot of “PHP” folks out there, so its easier for them …

Toma, you got me! This is what a I want… Not a theme, but a few FEATURES, acting like a theme. But features in hugo, are not packaged in a stand-alone way, so much manual editing, copy/paste etc… to weave it all together, The directtory, Layouts, hints at it, but it does not contain a collection…

I gotcha, I just don’t know how one would go about loading in different smaller features into their site in this stage of Hugo other than if a theme carried all of these components that could be configured. It’s kind of encouraging me a bit to build some sort of theme framework like that.

Yes, my problem exactly! I want each “feature” packaged, separately, sub-themes, ala Git, dump each into Layouts… But things are not done this way in hugo! Well factored components, with no dependencies! no external stuff needed. Put all needed stuff into Git! and nothing more! No theme, jus…

But these theme components would have to be pretty plain and bare style-wise to be plugged in with no dependencies, no? If someone created a navbar with Bootstrap and another person created a slider with Flexbox Grid and some one else created a header section using their own CSS concoction… I’m not…

Ok, then skip easy, let us aim for EASIER! plus your own CSS… :slight_smile: and js is evil, so, skip that… No dependencies!

This thread is getting crazy, at least with respect to the number of exclamation points :wink: If you want to make something ultra flexible, my thoughts are as follows: Create a library of flexible partials you treat like “components” that users can easily clone into a project or a theme. Give sai…

I think I do not want a "theme"

feature

abathur June 24, 2017, 6:30pm 21

A while back I posted a loosely-related idea about supporting feature/behavior tests to kickstart a distributed/community effort to codify features. It probably isn’t necessary for your idea, but it could be helpful. I just wanted to cross-link this in case anyone does attempt to work towards this.

Topic		Replies	Views
Theme standards and general experience feature	15	4139	June 2, 2018
Widget mechanism feature	14	9332	March 18, 2017
Theme component/module topic or listing Meta modules	15	2332	March 6, 2022
New Themes Gallery site feature	52	12666	February 14, 2017
How can I judge the quality of a theme? Using Themes	26	3579	December 9, 2021

I think I do not want a "theme"

Related topics