Board Thread:General Discussion/@comment-44975735-20200322133212/@comment-44975735-20200430175837

I agree that being explicit is the key. I think I'll try using line numbers and colored text to describe any complex change alongside with standard description of it's functionality. Something like "Here is a block of code. It replaces lines from 40 to 60. What is red is there already, what is green is what is new, what isn't there isn't supposed to be there.".

I can do linear styling in replies like this and this using the   tags.

I'm asking because of my desire to fix wiki's CSS which would involve replacing existing code and that can lead to a lot of misunderstanding.

Is this the last bit of CSS code required for the infoboxes or is there more to do? Because at least to me, it looks done.

edit: It looks like I can't see the line numbers when viewing the source code which is quite a complication for this approach that can lead to a lot of trouble.

Also I would have no way to test the pre-integrated code so that brings us back to square one. You would either get a snippet that can break things with improper integration or you would get a chunk of code that is not tested and can be broken on it's own just as easily. Any code needs to be checked after being modified to see if it does what it should. It looks like there is no way around that.