CSS, JavaScript, Coding On Lichess forum

Welcome to the CSS, JavaScript, Coding On Lichess forum!
Only members of the team can post here, but everybody can read.

We could start by putting a list of open questions we still have.
starting concise at the cost of cryptic (reminder to myself)
a list of questions or problems we solved by tweaking CSS or Javascript using overrides, tampermonkey, or stylus (or equivalent tools).

Perhaps, some newbie questions about priorities within code, and between js and CSS.

I don't know how team forum works, BTW, can we make headings, chapters under which we could arrange the answers as they emerge. How about editing back, after a while. i stop here. brainstorm section? summary section?

i'll keep adding ideas for this sub-forum, while we figure out a structure for the info in it.

opinion: (perhaps some titles here and there to give a sense of how true we hold the following statements)

I find that the chrome Devtools override mechanism is a good way to explore the DOM (live html tree) and CSS variables and values in relation to what we see. But, once the correct code (for whatever question, problem or intent) is identified, it is a bit flaky, in the long run, and previous mechanisms of userstyles and userscripts (stylus and tampermonkey, e.g.) might be a better approach, for seamless lichess use.

@dboing would it be possible to pin a google drive link to the top of the team page and post update notes in there? make a folder for each 'active' member of the team and give the email for that person permission to edit and post their updates?

I have discussed this with @BerserkAsIfUWereMad privately, with intent to post resulting solution avenues. You have added some practical ideas to that of shared folder.

Just talking about the common cloud drive account, or folder-in-account. The question of not giving away more personal info than what is on Lichess profiles came up, for me at least. And the question of making a new google account. I don't have a cell subscription, which has become requirement for verification of identity at creation time. landline, voice automation not an option anymore. How, can that be? no cell phone line...no need actually, until this.

Moving personal exchanges to the team main thread, used for discussion, for now, leaving emerging topics to new threads.

... to indicate i truncated the text. hopefully without loss of meaning.

@dboing wrote:
If you have any suggestions about how best to organize the threads policy (when to start a new one versus keep posts inside existing ones ...)

@ChesswurmOTB wrote:
My personal opinion is to have a #General thread to talk about anything and open a new thread when there is a new project. So I started a new thread because I had a new code for a previously unmentioned problem. Can team leader close certain threads? If so, maybe format as follows:

#rules
#general
#index of finished projects (links to other threads that have been finished)
#project 1 (closed because it is finished)
#project 2 (open because it still needs solution)
etc.

@BerserkAsIfUWereMad wrote:

should I close or delete some threads?
Are these threads I should create?
...
Unfortunately no way to edit titles
possible to make threads sticky, so they appear greenish on top
...
I've had a few other teams

Terminology:
it appears that we have the following synonyms in play: Topic, Category, Project, and Thread.

@BerserkAsIfUWereMad
So about your powers of editing:
can you make a list, or is there a link with that info.

Or, these are things that you figured out by yourself from team leading before?

@ChesswurmOTB
We could each practice with creating our teams (temporarily), if that's how we can find out what tools are available...just thinking..one member practice teams, please don't join...etc...

@ChesswurmOTB tentative understanding here,

So projects are discussions centered on topics (they are topics?), only rule there: try to stay on topic, but discuss freely.
It may get difficult at some point to untie the knots in the resulting spaghetti.
Can leader put a top post at any time within a thread?

What is a finished project? What is a project? I thought that these would be raw discussion for a project of Topic. That would be linked to in a more succinct and coherent way elsewhere.

Why an index of finished projects? The team front page (from main menu =>...=>forum), shows last 10 ish posts, but the list of threads (last link at bottom right), is some sort of index already.
But no way to know if a thread has stop discussing? That is your intent, right? Did you mean closed by time limit?
If the thread title is wide enough, the discussion may never reach an end, other than the time limit when no new posts.

There are already different types of threads. Existing userstyles is not discussion prone, it is more like an index of what is out there. Same for Other teams. Then i have another thread idea that i'm proposing in the same trend, where discussion might be needed to understand the code in the posts, but the initiative goes to gathering identified CSS selectors (i will send you my first draft for shrinking, if you have time).

Do you see, where i there might be some confusion on my part?

Of course, there are other threads which might be projects like you mean (but still unclear to me).

So my idea of "project" is like my sticky nav bar. If I didn't know how to do it, I would make a new thread with my vision, and idea on how to make it a reality. Then, whoever has input on how to make the actual code can add to the thread. When the code is finished then the "project" is finished, and thread can be closed. Your idea of staying on-topic but discuss freely is great.

Index: A table of contents of all finished projects. That way it can be easy to find finished userstyles, etc. that were compiled by the team.