@Chalarangelo as far as I'm aware you've recently converted many 30s projects over to new domains and a new starter UI kit. I apologise for being AFK for a few months so I understand you couldn't ask before it transitioned over.

I do like this new UI, however, I think parts of it feel like a beta still and think it could use more polish.

Some big problems I see:

• The link that's first on Google (and was shared everywhere) is now broken
• JavaScript snippets don't seem to work anymore
• Some overflow problems with elements in the snippets
• Some snippets don't gel properly with night mode (as it wasn't accounted for originally) and are hard to see
• Clicking a link then clicking back doesn't restore scroll position

Is it possible to reinstate the old UI and old domain temporarily until these particular kinks are ironed out?

Hi to all! It could be useful to add a cite to :last-of-type selector in the ":not selector" snippet. Last-of-type is generally more reliable than :last-child in that context or at least a nice thing to be aware of.

I thought of this, reading this article by Timothy B. Smith https://brightlycolored.org/2017/02/css-tip-use-not-to-save-time-and-lines-of-code/

Add Facebook and Twitter custom image and title to the website so it is more appealing to users who see it on their timeline. It is also supported by messaging services, browsers and social networks.

This is my first time on GitHub so I hope I didn't make any mistake. Sorry if I did!

Hi,

I suggest to change the order of the first two fonts from ´´-apple-system, BlinkMacSystemFont,´´ to ´´BlinkMacSystemFont, -apple-system,´´.

Otherwise IE will use a serif font, which is the opposite of the intended behaviour.

Sidebar used to be scrollable, now it doesn't work. Does anyone have similar issues, if so do you have any idea why is that happening?

Environment: MacOS Mojave & Chrome 69.0.3

• Need to update all problematic snippets before merging
• Removed grid-layout.md because it broke the global styles -- I don't believe it's very useful anyway in this repo's format...

Fixes #59 Allows to select multiple tags and then view all the elements that contain at least one of them. I am not sure if this works correctly because I had no way to test it.

Since some user interactivity is being added, it might be a good idea to make everything more declarative and use components and all other benefits it brings.

Vue can be easily be plugged in to the page without a complex build system, so we don't need to use single file components etc. as that would be overkill.

The current naive solution was to use a "namespace" (.snippet-demo) for the demo code, but it's arduous to type and repeats the main visible code. We should just use the code inside the main code blocks, and when building, generate a custom scope for the styles so they don't conflict with other snippets or the global styles.

This means the demo should match the code exactly, which is better for the CodePen button. (Some don't match currently - as some only specify the minimum number of properties for the effect, but I think that causes confusion.)

I've long used rem but when the window is being resized or elements are transitioning in height, it can cause ugly 1px jitters everywhere due to browser rounding prolems. With px, this doesn't occur.

px is also responsive on most browsers when the zoom level is changed.

https://hackernoon.com/rems-and-ems-and-why-you-probably-dont-need-them-664b9ce1e09f

@Chalarangelo

Nice addition to this great repo would be : background transparency:

nicely explained in this stackoverflow answer:

https://prnt.sc/irr3c0

if you could implement it, it'd be great.