#Friendica people! I think #Bookface is getting close to another release. So let me know if there is anything you've noticed that should be tweaked or fixed for the next major version. If I can, of course. Bookface is just CSS and I can only style what's already there in the "Frio" theme.
@Friendica Support @Friendica Admins
@Friendica Support @Friendica Admins
Thomas
•When I go on a self -created channel with Fennec, the lower bar wanders up a bit and sometimes I can't navigate to the next page.
Pygoscelis Papua
•Thomas
•http://[img=https://friendica.world/photo/870872489267df0a11333f9986461737-0.png][/img]
Pygoscelis Papua
•Thomas
•Andy H3
•In Fio mobile, this hover panel needs some attention. The buttons are particularly obscured and need to move towards the left a bit.
wilhelm
•Pygoscelis Papua
•Andy H3
•The network icon in a reshared post, on the mobile version, is running into the timestamp text.
Pygoscelis Papua
•The next release of Bookface will have a right margin to make sure the status text never overlaps the network icon/button.
L.A.M.F.
•I have a few general optimization suggestions:
- Convert CSS to LESS (.scss)
- Compile .css and min.css (minified) files
- Use min.css files by default, with an option in the theme settings to switch to the non-minified CSS file
This would significantly reduce the CSS file size and simplify writing CSS.
Pygoscelis Papua
•I'm not a fan of CSS pre-processors though. After nearly 30 years of doing web design+dev I don't like to introduce dependencies if I don't need to because I've seen a lot of these things come and go. Next week someone will tell me to rewrite it in PostCSS. 🤷 The only reason I can think to use them now is to support advanced CSS features for old browsers nobody should probably be using anymore. Because modularization, nesting rules, pseudo-selectors, variables, computation, reassigning values at runtime, and color transforms are now all built into vanilla CSS for modern browsers. Bookface is already making use of most of those features, and the PHP pre-processing is taking care of the rest.
So minifying and/or compressing is probably the best bet for optimizing it, but the real solution is probably a major rewrite or replacement of the underlying "Frio" theme itself, which is very, very code-heavy (thanks to legacy code reflecting its age). But that...will be a major undertaking because that theme as a lot of "moving parts."