Skip to main content


#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
@Pygoscelis Papua
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.
I'm guessing what you mean by "can't navigate to the next page" is that it moves up to cover the pagination button at the bottom of the feed? A screenshot would help me figure out what's going on. The bars are "fixed" positioned, they shouldn't move (well, except to slide off screen in landscape mobile view).
Image link is broken. Also please check the permissions on the image.
Hello @Pygoscelis Papua

In Fio mobile, this hover panel needs some attention. The buttons are particularly obscured and need to move towards the left a bit.

@randompenguin@andy this is not the bookface template but "stock" frio.
I can't do anything about it in stock "Frio" but this will be fixed in the next release of the "Bookface" scheme. Thank you for bringing it to my attention.
Hello again, @Pygoscelis Papua

The network icon in a reshared post, on the mobile version, is running into the timestamp text.

Yes, I'd noticed that both on mobile and with deeply indented comments, especially if people add stuff to the status line like what app they are posting from or longitude and latitude or it adds that (received) info.

The next release of Bookface will have a right margin to make sure the status text never overlaps the network icon/button.
@Pygoscelis Papua

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.
I'm not convinced adding a CSS pre-processor will really help. A bunch of the stylesheets are already modularized and PHP processes variables and concatenates those files on the server side already. That might be why none of the stylesheets I've looked at in Friendica are minified, like maybe it messes up parsing them or something? I'll have to test it on my dev server.

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."
⇧