Splitting assets in two and what to call them?

A draft blog post I just wrote:

In short, I need to split assets between design and content assets, and
I
am trying to figure out good names for the two directories. Any
suggestions?

On Wed, Jul 4, 2012 at 6:15 PM, Intransition [email protected]
wrote:

A draft blog post I just wrote:

https://github.com/trans/trans.github.com/wiki/2012-07-04-crossing-the-assets-divide

In short, I need to split assets between design and content assets, and I am
trying to figure out good names for the two directories. Any suggestions?

Funny, when reading the article it occurred to me that you actually
have used two new names already. Why not stick with them? Or use
“assets-design” and “assets-content”?

Kind regards

robert

On Wednesday, July 4, 2012 4:39:01 PM UTC-4, Robert K. wrote:

suggestions?

Funny, when reading the article it occurred to me that you actually
have used two new names already. Why not stick with them? Or use
“assets-design” and “assets-content”?

I thought the same thing after re-reading what I wrote. But (and isn’t
there always), while content works to describe it, I think it’s too
broad
a term for the directory b/c wiki page files are “content” too but
remain
outside said directory.

I’m not 100% about it, but at this point I’ve opted to name
“assets-content” to “media” and leave the other as “assets”.

I thought it was rather interesting that for practical reasons this SOC
(separation of concern) become necessary. I wonder if it’s a good
practice
more generally that website designers should adopt.