@Friendica Theme Developer
Because of my limited time I have decided to focus my work on smaller pieces. After my attempt to work on the Friendiboot theme (I know I said I would publish the result but I lost a little bit the motivation after summer holiday to work on Friendiboot) I realized that much theme stuff is hardcoded in friendica core. Especial if you want to use css framworks (like bootstrap) which use their own classes you will realize that there are many cases where you have to stop and have to leave it the way friendica core presents it.
While my work on Friendiboot I wrote down a list of such cases. I would like to go through my list (according to my time,motivation and skills) and give the theme more control.BUT
this would also mean that while friendica core maybe will be cleaner the templates maybe will be more complex. I would go for it because with more control from template side many UI/UX things could be tried out by simply editing the theme (and don't have to changed any longer in friendica core).
I just want tho know what you are thinking about this.
To give some examples:
There are many cases with a different degree of how they would make the template code more complex. I just wanted to ask where the line between customization vs. simplicity should be.
Yesterday I started some simple work on the directory page (https://github.com/rabuzarus/friendica/tree/dir
) and on dirfind/match page (https://github.com/rabuzarus/friendica/commits/dirfind
). Both should allow to treat this pages as pages. This means you would be able to theme e.g. the directory page as whole. (BTW. can some test if pagination is working after this commits. I don't have enough contacts to test it
One last question: Is @Friendica Developers