CSS, JavaScript, Coding On Lichess forum

The set of your contributions, gives an example of your proposed thread-making structure.

So let's follow the sticky nav bar posts. There are 3:
1 in existing userstyles (first in time)
2 in its own project thread (which is solved, but BTW: why close it, it may attract some questions related)
3 in the index of solved projects (pointing to project thread, and perhaps to the post in existing userscripts).

Should the index have priority, i mean the one to consult to get the links to all the posts in the team related to that project. Interested users would hence start there?

Perhaps the index of solved projects should link to an index of solved issues outside of the team (which the existing CSS selectors and Userscripts were in my mind doing, together: one about ready made packages, the other about doing it yourself)

Initially, i was wanting existing scripts to be just links and description of purpose. New projects would likely be more about code snippets as in your example project. Userscripts in package format would grow slower. Code snippets, faster, in a different thread(s). but maybe that was not really clear, and your structure is forcing this clarification.

Existing outside snippets versus projects snippets. or an index for all (team and outside).

Can we add an index of all modification subjects which tells where to look, outside team, or in the projects?

Or use what we have....existing for outside, and index of solved for inside? or let's not care about that...

My aim under my worrying:
avoid doubling efforts, yet have a cohesive set of threads/posts which interconnects without loose ends to search for manually.

This discussion is not urgent, just think about it...

about the #general thread:
ideas of content from past discussion, accumulated here, or in private correspondance, or in the main forum, before the team was initiated. posts or discussion that's not yet packaged into a well defined project, and that's not about the team format.

I propose to move all coding related content i just mentioned over there, and when done, these posts could be deleted from here, leaving this current thread to discuss format, and management.

to name a few:
perhaps all the stuff about persistence that we already discussed (before making it a project)
things we learn about JS CSS and Devtools, that's not going to end up in userstyles directly. like mutation.oveserver results.
perhaps from there, projets can be conceived, narrowing Project titles or topics, through discussion. the brainstorming spot.
I think, @ChesswurmOTB, that this is what you were expecting #general to be.

formatting idea for #general as a raw brainstorm, throw your questions, etc... discussion space:

with some cycles of cleaning redundant posts, or posts that are obsolete, per subsequent discussion, or posts migrated to emerging projects. or posts contributors regret having posted....and request deletion of.

See, @BerserkAsIfUWereMad, I did not know you had editing powers, this can give us the option of a dynamics structure (structure is fixed, except for new projects, but its content dynamic, some in, some out). So the exploding raw discussion monster could be tamed through such cleaning cycles.

@BerserkAsIfUWereMad @ChesswurmOTB

Since we intended the #general to be the free for all, free format discussion, and (i may be the only one thinking that) the entry point for new contributors and new contributions (questions, report of open forum related thread, report of web page, anything).

then i wondered, what if i am a member and would like to ask a question, and look at the forum front page?
is "general" looking as the entry point, what about the team title thread, but then i get in there, and wonder if i am in the right spot.

i suggest, keeping same rules, but difference title for general. something meaning:

free format, entry point, start here, ask your question

do you get my point? also, please let me know if my reshuffling of archived thread (and renaming), and consolidation bring any problem, or if in my copy-paste juggle I lost somethings you remember was there and worth it. thanks.

is it better to
A) start asking in open forum, for already existing solutions we don't know about,
and then go into team, if open forum stays silent?
B) put an echo post in general, from the start, the echo post there linking to open forum for quick call back?
C) start a thread in team and open forum, as Communicating vessels...?

Probably better to stay contained in one thread. It wouldn't be efficient if 2 teams were solving the same problems at the same time. Maybe post in team, then when a solution is found, post the solution to the open forum. This can also work as advertisements for the team.

Yes, thanks for pinging me for the open forum thread. That also advertised without trumpets for the team. team? what team? better to incite questions than feed an answer that may get lost in the ether of non-solicited information.

My questions could be asked both ways. project initiated here, or initiated there (open forum). Doubling is not a good thing, having to disperse and click and what not to gather two lines of discussions.

about questions initiated in the open forum and thinking out loud:
It would be nice to have an entry maybe a 2 liners in the index with WIP referring to the open forum thread so that we don't need to double, until some conclusion is reached there, and then we can have a finished project thread here, with solution in first post (it would be buried in the open forum thread). I guess, while the problem is in the open forum, use the index for scripts outside the team, WIP can work there too, keeping small modular delete-able posts (for replacement). thoughts?

I think that would make sense if somebody already started working on a solution in the open forum. Otherwise, I'd say try to keep it contained to our team forum. That way we can claim credit and if people want to help out they can join the team.

Right. good thinking.

@BerserkAsIfUWereMad @ChesswurmOTB
Please have a look at the new CSS JS coding team bio. criticism welcome
Also, we have a sibling team now, which is a virtual inbox for this team, as i don't know of any lichess feature that would do that.
link in bio. i could put it here, but instead:
lichess.org/team/css-javascript-coding-on-lichess

editing to save a captcha job:
also, i would like to be have a header or notification when new posts or threads are made in the team, without having to scan the front pages, and without requiring being pinged explicitely by posters. i think every member should have a little header line or notification as well... is that possible?

Can you ping all members?

there are no options about pinging or notification in team management features that I could see (note to tips).
would make sense though that the team admin would be able to call the whole team.
Do you think people would get annoyed if every new post would trigger a notification.

There are more than one level of notification.
in the main page of lichess there are 3 places: the bell (up right), top left headlines, and bottom, open forum headlines.

The rules for appearance on either of those 3 are different and I am not sure if below is covering all cases:

@ ping goes to bell (and desktop if allowed)
any new post goes to bottom (but limited history there)
followed people posts appear on top left
any post on thread participated by you also top left.

I find the top left, the least intrusive. and i wish all of them would have longer buffers (the bell module has long buffer, deferred).

Also, while on the subject, the @ mechanism only applies to current thread participants (the auto-completion i mean).
Maybe CSS or JS coding could help, working with team front page where all members are listed, could scrape or parse it.

Without having everybody notified at every new post, as leader i would like to know without having to browse, if there was new activity on the team forum...