The conversation

Lessons learnedExperience excerpt · English

I spent most of the past decade producing (as a writer, editor, and community manager) tutorial and …

… I spent most of the past decade producing (as a writer, editor, and community manager) tutorial and other technical content for a large software company. Because the company I worked for values open source principles, every single article I ever wrote for them was licensed under CC BY-SA or a similar license. If the sites I worked on disappeared tomorrow, I would be free to republish them on a new home on the web, and more importantly, to continue to keep them up to date. I don't work there any more, and it's such a relief not to have to worry about a lawsuit from a former employer just to be able to reuse my own work.

Original discussionGoodbye, CSS-Tricks151 source comments · at import
2

Community replies 0

No community replies yet. Add your perspective.

Replies from the source 2

Direct replies available in this import. Original-language excerpts.

AB

Are the articles on CSS Tricks under a libre license? I can't find any mention of it, though I haven't searched in depth, so it's proprietary? For the record, their code on CodePen looks to be MIT licensed (though CodePen requires a login). For example, Infinite Burger is MIT licensed [0]. [0] https://codepen.io/team/css-tricks/pen/mNBrNG#_=_

Full original
RE

this is why licensing matters! Yes. And it's also why any resource you use more than once should be submitted to archive.org — just in case! https://web.archive.org/web/20230000000000*/https://css-tric...

Full original
Continue on Hacker News

Respect different perspectives. Share concrete experiences.

Sign in to post, reply, repost, and quote.