@timapple I’m glad you like it. If you aren’t chomping at the bit, I was going to update the plug-in to have settings for 5 or 6 of the main colors so they’d be configurable.
@timapple I’m glad you like it. If you aren’t chomping at the bit, I was going to update the plug-in to have settings for 5 or 6 of the main colors so they’d be configurable.
@timapple There are definitely some bugs to work out. I’m likely missing some default layouts and/or some partials. I’ll work on it this weekend.
@timapple I spoke too soon about having parameters for colors for Vapor1994. As best I can tell, Micro.blog does not yet support SASS or PostCSS so I can't use template code in the CSS. You could use the theme as a base and then add custom CSS to change the colors.
@timapple That works for the CSS. However, the challenge is to get MB to change those values when it builds the site. That means a Hugo template variable needs to sit in the CSS or SCSS so it can be evaluated. Hugo supports that with pipelines but MB doesn't yet.
@ezellwrites Can this be accomplished by using custom parameters in the config.toml file?
// @manton
@pimoore My understanding is no. Those parameters still have to become values in the CSS. They have be inserted when Hugo builds the site. Because MB's Hugo doesn't have the PostCSS or SASS pipelines, those CSS files never get processed against any template replacements.
@ezellwrites @timapple You can put the parameters in a layout template still. So, for example directly in the header. Might not be as cleanly organized but should still work. (And plug-ins can have a setting screen to set parameters.)
@ezellwrites This is also supported by Hyde (see here) which I see Vapor is based on. So, bascially add a custom value defined by theme setting to the layout. Class exists already in CSS. // @manton
@ezellwrites @manton Maybe that's what Jason is doing with Hain's Point? Either way there are settings for colours in the plug-in.
@SimonWoods I looked at this one. It's using Bootstrap and JS. The values available to the user are the Bootstrap theming values. They are not RGB hex values which is what I was going for. I also wanted to avoid including any JS in the theme. // @manton
@ezellwrites Ohhhh... see this is what happens when you don't take even a slightly harder look at the details 🤦♂️
I've always had the impression that web design is often made up of JS-or-non-JS decision making. Your approach makes sense.
@ezellwrites Ah, ok. That's sounds a lot tricker. Hmmm ... 🤔
@timapple Excellent. I'm going to do something similar so those colors can be set from MB settings so a user needn't edit CSS to change colors.
@timapple I think I added that template in the latest version. 1.0.7 should have a single.html
that gets applied. Also, that version has a cleaned up Archive page. Still quite simple but actually is themed.
@timapple The site is looking great! It's kind of neat to see how a different color scheme has a different vibe but retains some of the underlying inspiration. Awesome!
@timapple I think it should be either .page
or .post
depending on whether it’s inside a list or just a base page. I can poke it a bit more when I get back to my computer.
@timapple You're welcome. Hopefully, future versions can make this kind of customization easier. I have some "I get paid for this" code to work on this week but maybe I can sneak in a new version at some point.