There’s a growing trend of ditching traditional “back-end” frameworks for dynamically rendering pages. As the interest in client-side frameworks grows, so does confusion about which one to use. There’s React! But then there’s Angular…and have you heard about Vue? What about Handlebars? But let’s back up a second. Should you even use one at all?
It came to my shock and surprise to learn in January that I’d been awarded a fourth SDL Tridion Web Tridion MVP award. In the previous year, I hadn’t felt as if my contributions were that great —but contribution is not in the eye of the beholder. One of the perks of winning an MVP
It’s not that hard to write CSS. The basics of how the language works can be learned in 15 minutes. Most of the major properties and techniques for using them can be learned in a few days. You can learn how to build static websites within a few weeks —and there’s scores of books and blogs
One of the things that front-end and back-end developers alike loathe is the dreaded scenario where a content author wants to be able to add their own styles to content. No, not set a skin or theme to the content. They insist that an <h1> be any of 16+ million colors. The <img> should have
So you’re a back-end developer. You write .net or Java all day. You create Schemas and Templates in Tridion. It’s Friday. The front-end developers have signed off early and you just got a high priority bug. And it’s in the CSS. You hate CSS. What do you do?
You’re a front-end developer. You’re writing for a component template. You hand off HTML for a back-end developer to write a view. The back-end developer looks at it, goes cross-eyed and starts muttering to himself. You explain it. He says, “yeah, Tridion can’t do that.” You read my last post; you’d know that there’s a
So, you’re a front-end developer, eh? And you’ve been told that you’ll be writing code, and that it’ll be moved into a Content Management System. Called Tridion. And you can’t find out where to download it because there’s not a version on Github. There’s some random blogs out there, a Stack Exchange, but it all
This is part three of a series called “Front-end for the Middle”. Honestly, I didn’t mean to write three posts. But when one post is over 2,000 words without being finished, it’s time to get slicing. Previously, we’ve talked about directing a front-end developer’s focus away from design, and on to content. And we’ve also
This is a continuation of a previous post that I wrote, entitled Front-end for the Middle: Focus and Design. Previously, we established that it’s better for a front-end developer to be focused on content, rather than design. In this post, we’re going to move into a discussion on how HTML semantics can influence what happens