How do you find working with Laravel 5?
It's great! I have used Laravel 4 for a while so getting used to all the new directories and general layout of things is a bit of a tough one, but once you get around that, it's mostly the same. Love it.
Nice to hear about it.
By the way, just curious, how long were you working on this up until launch?
The initial site took around 24hours to make, but in the evenings I am making small releases for it improving it each day with the feedback we get and more features!
I wish I could comment on the articles so I could mention what a bad idea it is to use @extend for things like ".helvetica-bold". Enough with the extend abuse already!
My scar tissue... it is deep.
Can you elaborate? I'd be curious to know about the pitfalls of using @extend?
Harry Roberts (csswizardry-guy) breaks it down better than I ever could: http://csswizardry.com/2014/11/when-to-use-extend-when-to-use-a-mixin/
The article touches on it, but I think it's important to emphasize the importance of looking at your compiled CSS, to really understand what Sass is doing.
TL;DR: It's very easy to find yourself in a position where you've created inherent relationships between unrelated components, based on coincidential similarities, for the perceived benefit of DRY-er, more maintainable code.
For example: Let's say you've got a component called
.tweet-authorand a component called
.sign-in-buttonon the page. Both are Helvetice Neue Bold, 14px. Using @extend to declare your font properties creates a hardened relationship between the two components even though they are totally unrelated.
Indeed, the short-term benefits make this a tempting approach — it can certainly pretty up your pre-compiled CSS — but the long-term cost of dealing with mammoth selectors and false relationships can be extremely painful.
This is a case for variables or mixins.
Thanks, I'll read up on that :)
Hey Sacha, fan of Sidebar! I just submitted Programmar on there :)
Let me get this right—
Programmar is a medium-esque writing platform for developers that uses GitHub for version control?
If that's the case, I think it is brilliant.
If that isn't it, maybe an about page wouldn't hurt.
Either way I'm intrigued.
Thanks for your input. It actually doesn't use GitHub for that reason. Our aim is to create a better place for developers to share knowledge. Maybe an about wouldn't hurt, thanks again!
Some aspect of the typeface (Karla), the line-length, line-height and/or the font-size are really throwing off readability for me on the article pages.
... which I could definitely live with if Safari Reader worked on the articles.
Thanks for your input. While we work on fonts, we'll have our developer make it friendly for Safari Reader right now. Hope that helps!
Safari Reader is supported on articles and we're designing for a typography update. Thanks again!
Yep—nice. Hey, no worries and best of luck with the project.
Nice work guys! I really love the simplicity, and I am looking forward to writing some articles in the future. I would suggest adding some sort of organization to these articles. Whether it be by using tags, or an archive organizing articles by month, etc. In the near future, there are going to be a myriad of articles with no way of finding which one I want. For example, I really enjoyed Joseph's inline-block article. It would be a pain to find it in the future without the url and all the articles written after piling up above it.
Thanks for your feedback. We're currently working on new features to help with the points you hit. We didn't quite expect as many articles with such language diversity so quickly! We've actually just updated the sidebar. It will now help you with filtering articles from random posts to ones posted by developers you follow.
Awesome one folks <3
Thank you :)