I remember seeing a demo of a website which didn't have any tag - I think the stylesheet was served by an http header that the browsers were automatically linking. I can't find the url.<p>[edit] Here it is! It still doesn't work in Chrome. <a href="http://css-tricks.com/using-css-without-html/" rel="nofollow">http://css-tricks.com/using-css-without-html/</a>
Makes text uncopiable in all browsers. Combined with entity-encoded source, this could make a decent protection against most users. Not that I approve such things.<p>[edit] unicode encoding (\67). html-entities do not work.
You can do this /without/ a link tag in Firefox by using a link header. Syntax is:<p>Link:<[filename]>;rel=stylesheet<p>It's fun to use:<p>Link:<.>;rel=stylesheet<p>and detect the Accept: text/css header to serve a css file conditionally, too.
Well, thank goodness for accessibility requirements, at least in California. There would be plenty of site owners, including the government, who'd love to make their sites much more difficult to scrape or excerpt from.
I embraced this idea a while ago on <a href="https://macko.mici.hu" rel="nofollow">https://macko.mici.hu</a> — purely for childish entertainment, without any actual content. Source here: <a href="https://github.com/underyx/mici.hu" rel="nofollow">https://github.com/underyx/mici.hu</a><p>macko.mici.hu loosely translates to pooh.winnie.hu; mici is also the nickname a friend of mine goes by, which is why I bought the mici.hu domain.
Seems to be a clever idea for caching and reducing traffic. All static content can be stored within the CSS, which is tagged with a long HTTP expire date. This allows to send all dynamic content within a tiny HTML page that only references the CSS above, thereby adding the static content.
This is exactly what I did when a friend of mine asked how to make the text uncopy-able. I did server-side rendering, create a bunch of randomize tag and generate inline css with ::before and ::after. It was brutal but it works.
I think this shows that the "Content" tag in CSS is a bad idea, at least if you're concerned about separating presentation and content. It's a bit like a single-image website.
1. need a 'compiler' to compile html and css into one css file
2. seems it can make embedding content a bit easier and cleaner. eg. embed a facebook/twitter button.