@UltraBulletIsVeryFun Thanks for joining. This post may serve for other new members that need some orientation, as well.
First, look at the indexes on our forum front page (they have # as prefix and are stickied, i.e. greenish background)
Scripts of two types:
- CSS for userstyles (Stylus)
- JS for userscripts (Tampermonkey).
-I would suggest that you install those two extensions either in chrome or Firefox.
-use the indexes for projects from our members,
-the project/thread titles show you the type of lichess front-end features that are modified to satisfy some user requests
CSS is the first most user experience related language that affects the front-end using local modifications (scripts, override).
the simplest approach is finding CSS selectors using browser inspector DOM tree browser in correspondance with the page of interest (hovering node mapped to page object in parallel). Once you isolate the specific selector, you can formalise it into a userstyle script. There are also, repositories outside lichess for userstyles and userscripts with lichess pages as target.
Also, after you are familiar with some of the finished projects, check the bug/feature request lichess forum and this team INBOX thread managed by our member named @chesswurmotb. Put that into your routine, as the search features in the forums are rudimentary and thread get archived after a while, despite their continued relevance, get buried. That is one reason for our somewhat rigid thread structure (see intro thread for some taste of that formatting question if curious).
I can help some with CSS selector i already played with, otherwise i might be co-learning with you. @berserkasifuweremad has experience with extensions, and Javascript, and @lamlamer has done some extensions as well that complete some part of lichess interface regarding text translation for those part not covered by the crowdin project. Other members may also be able to help you, but they have not yet expressed themselves here, yet. I hope i am not forgetting anybody. sorry if i did. Other lichess users have also been prolific authors as you could read in the index of projects from other sources.
Also, i am pondering whether to make a child team, where we could have learning thread and tech tips exchanges threads, since here we focus more on finished projects, and since learning is more messy (i get messy, i am not the only one).
To any member reading this, i welcome feedback as to how this could be improved for the target audience intended. thanks.
@UltraBulletIsVeryFun Thanks for joining. This post may serve for other new members that need some orientation, as well.
First, look at the indexes on our forum front page (they have # as prefix and are stickied, i.e. greenish background)
Scripts of two types:
- CSS for userstyles (Stylus)
- JS for userscripts (Tampermonkey).
-I would suggest that you install those two extensions either in chrome or Firefox.
-use the indexes for projects from our members,
-the project/thread titles show you the type of lichess front-end features that are modified to satisfy some user requests
CSS is the first most user experience related language that affects the front-end using local modifications (scripts, override).
the simplest approach is finding CSS selectors using browser inspector DOM tree browser in correspondance with the page of interest (hovering node mapped to page object in parallel). Once you isolate the specific selector, you can formalise it into a userstyle script. There are also, repositories outside lichess for userstyles and userscripts with lichess pages as target.
Also, after you are familiar with some of the finished projects, check the bug/feature request lichess forum and this team INBOX thread managed by our member named @chesswurmotb. Put that into your routine, as the search features in the forums are rudimentary and thread get archived after a while, despite their continued relevance, get buried. That is one reason for our somewhat rigid thread structure (see intro thread for some taste of that formatting question if curious).
I can help some with CSS selector i already played with, otherwise i might be co-learning with you. @berserkasifuweremad has experience with extensions, and Javascript, and @lamlamer has done some extensions as well that complete some part of lichess interface regarding text translation for those part not covered by the crowdin project. Other members may also be able to help you, but they have not yet expressed themselves here, yet. I hope i am not forgetting anybody. sorry if i did. Other lichess users have also been prolific authors as you could read in the index of projects from other sources.
Also, i am pondering whether to make a child team, where we could have learning thread and tech tips exchanges threads, since here we focus more on finished projects, and since learning is more messy (i get messy, i am not the only one).
To any member reading this, i welcome feedback as to how this could be improved for the target audience intended. thanks.