When the team chooses to use WordPress, you might be in for a struggle though. Seperation between front and back-end development in WordPress is quite vague and is smeared all over the place.
This article is aimed to convince you why WordPress is bad to front-end developers, what has to be done about it, and finally how a better way of developing can be achieved.
With DigitalOcean you can deploy your very own cloud based server in a very short time. This makes is perfect for hosting web apps. You can use Node.js to run as a web server and serve files and responses to the client. Setting up a Node.js powered web server is relatively easy when using DigitalOcean.
In this article I’ll guide you from setting up a DigitalOcean droplet to running a simple HTTP static file server in Node.js.
Markdown is used to quickly write a styled document with a simple syntax, great for taking notes or writing journals. MarkPress allows you to turn your WordPress install into an App to easily write and store Markdown notes.
While working on a frontend project you’ll easily come to a point where you need data from a webserver that will be retrieved through an Ajax call. Serving mockup data from those endpoints is a tricky thing when you don’t run your frontend project on a webserver.
Luckily there is a way to easily write middleware using Connect for NodeJS. Other great thing: works with task-runners!
There are a few class naming conventions you can live by, the problem with most of them is writing long class names that tend to give your CSS a messy look without compound selectors.
Luckily Sass now supports compound selectors which will make our stylesheets a lot easier and better to maintain.