Starting with just a simple line of code 11 years ago, WordPress has evolved to become the platform of more than 74 million websites.

Even with a vast array of competitors offering similar functionality, WordPress still dominates the CMS market with a 21.9% market share.

I have had a more detailed look at WordPress than most.

I have contributed to 6 releases of WordPress, including work in the XML-RPC API (in 3.4) and WP_Image_Editor class (in 3.5). I have also been involved in an upcoming release (3.9).

As we look toward the future of WordPress, it is important to evaluate current practices and trends within the WordPress user base, as well as the industry as a whole.

Comparison of WordPress.org home page

In this article, I will discuss my predictions and opinions regarding the future of WordPress.

Moving with Demands

Recently, the demand for advanced features has been increasing as more and more developers are using WordPress to build mobile apps and complex e-commerce websites.

While WordPress already delivers many solutions for advanced use-cases, changes in consumer behavior will consistently affect the demand for unique plugins and ongoing enhancements.

WordPress as a Mobile App Backend

The uptake of mobile technologies is on the rise. 58% of adults in the U.S. currently have smartphones according to the Pew Research Internet Project.

Emerging solutions such as the AppPresser plugin — a finalist in the 6 About to Break competition at MacWorld 2014 — are allowing users to create mobile apps using WordPress.

This current consumer trend towards mobile presents an opportunity for WordPress to capitalize on the shift toward mobile development.

By incorporating a RESTful application programming interface (API), current WordPress apps could be supported, as well as mobile apps that use WordPress as a backend.

WordPress as a Development Framework

WordPress has been placing a large focus on providing the best user experience possible. And, in my opinion, it has succeeded in this goal.

Moving forward, I see the concentration shifting toward evolving WordPress into a full CMS and application framework.

Right now, WordPress does a splendid job as a content publishing platform, as evidenced by its use by the major online magazines, journals, and blogs. Time magazine, CNN, Forbes.com, Wired, and TechCrunch are just a few examples of web properties that rely on WordPress.

However, more complicated use-cases like online stores, mobile app development, and web app development require plugins, heavy customization, and development.

The next step is to evolve the platform to make it a more robust CMS/app framework that can make more complicated use-cases easier to produce for developers.

Dealing with Legacy Code

While the system currently offers users a wide range of features and possibilities, WordPress will update its legacy code and deliver new APIs to ideally fit the needs of web developers.

If an emphasis is placed on this area, the biggest challenge will be streamlining the codebase while building a solution that ensures backwards compatibility.

Considering the first version was released over 10 years ago, achieving this objective is likely to be quite a huge undertaking.

Where WordPress Doesn’t Need to Change

The past few years of success have truly proven the knowledge, experience and passion found within the WordPress community.

We have worked together to accomplish great milestones and made the impressive strides that have advanced WordPress to become the most popular Web platform across the globe.

The WordPress community will play a large role in the continual development of the platform to best suit its users’ needs.

Related Content

About the Author


Marko Heijnen is a 1&1 WordPress specialist and a contributor to the WordPress community. He’s had a hand in developing 6 releases (3.0, 3.4, 3.5, 3.6, 3.7, and 3.8) and the upcoming 3.9. Some notable contributions include working on XML-RPC API and WP_Image_Editor. He’s also the main core developer for GlotPress and is currently creating a better open source tool for translations. As a 1&1 WordPress specialist, Marko is committed to improving the platform by contributing back to the community. Visit his site markoheijnen.com and follow him on Twitter: @m arkoheijnen.

The post The Future of WordPress appeared first on Six Revisions.

With more and more technology companies adopting remote working environments, having team members in different parts of the world is not uncommon any more.

Remote working comes with many benefits, but also unique challenges.

The biggest perk of working remotely is you are able to give all members the option to live and work where they are most productive. It’s often easier to stay focused without the day-to-day distractions of commuting to work and normal office interruptions.

But as we mentioned, many challenges persist.

Communication can be difficult.

Team-building can be very tough.

And working with time zones can throw you a curveball.

This can all be very tricky for design teams because we need to communicate regularly and extensively, share and pass files, brainstorm, and much more.

Any type of team needs to be on the same page, but this is especially true for design teams.

At Formstack, we’ve been a remote company for over a year now. We have team members from all departments working remotely across the country, and we also have a member of our development team in Poland.

As a company, we’ve learned quite a lot about remote working, and we want to share our insights with you.

Communication

Communicating is central to any design team.

When you work in the same office as your teammates, you can take a short walk or simply look across the room to talk with someone. It’s easy to bounce ideas around or steal 5 minutes of time to brainstorm.

As great as all the communication technologies are these days, you can’t beat face-to-face communication.

In a remote team scenario, impromptu discussions don’t happen as easily. You have to make an extra effort for these kinds of discussions.

Dealing with Facial Expressions and Tone of Voice

Text-based communication like instant messaging (IM) and email does a very poor job of conveying tone of voice, facial expressions, and body language. Yet, all of these things are essential components of good communication.

We know, for example, that a significant amount of communication is done through nonverbal cues.

We help solve this communication barrier quite simply by using video chats and gathering the team together from time to time.

Particularly, we use Google Hangouts for regular meetings and the new video feature on HipChat for quick chats.

We’ve seen designs can often come out underdeveloped when you remove face-to-face communication, but an open door policy with video communication software like Google Hangouts, or even just voice calls, is a good solution for this.

The Importance of Planning

Planning is already a critical process in a traditional design team whose members are in a single geographical location.

But then add the remote/distributed team factor into the mix, and planning becomes even more crucial and demanding.

As a development-design team, we’re always working both ahead and behind the rest of the development team.

What that means is we lay the groundwork for how designs will both look and function within the Formstack app. But once the rest of the development team hooks up all their functionality and does testing, it’s once again our turn to put the finishing touches on design.

It’s important for us to plan and understand timelines of not only our own team, but the entire development unit of our company.

We have to constantly communicate not only about the projects we’re working on that will go into development later, but also revisiting design work that has come back through the development cycle for us to finish.

Workflow

We have a couple of suggestions regarding workflow.

Utilize Time Zone Differences to Your Advantage

We mentioned earlier that Formstack has a developer residing in Poland.

Instead of this distance being a pain point for us, we actually benefit from this geographical difference because he gets to have a 6-hour head start every single workday.

Thus, we are able to jump right in and do design work on features that he has already completed while we were still sleeping.

The time zone difference is still tough, though — our Polish teammate does have to flex his hours a bit so he can have a window of time to work and communicate with the rest of our team.

Create a Style Library

Another workflow tip that’s helped our design team is the creation of a style library. We’ve built documentation around the uniform styles we want to remain consistent within our app. It has been an extremely useful tool as a remote team.

Our style library contains the snippets of code we need for easy implementation of common elements such as buttons, menus, utility classes, etc.

The library helps us design and build quicker without added communication around these standard elements.

You can build your own style library, whether you’re working as an in-app developer, front-end developer, or web/graphic designer. If you’re working mainly with graphics, your library might be as simple as a document containing consistent colors, icons, backgrounds, etc.

The goal of the style library is to maintain consistency within the product and to cut down any communication barriers.

Essential Tools

There are also a number of useful tools our design team uses that allow us to make remote working possible.

We’ve mentioned a couple already, but here are some other apps we love using:

Project Management: Basecamp

Project Management: Basecamp

Basecamp is the project management software we use to share wireframes, mockups, and completed files. We also use it heavily for leaving comments and communicating.

Prototyping: InVision

Prototyping: InVision

InVision is a web and mobile prototyping tool that we use to show the UX and user flow of designs.

Version Control/Code Repo: GitHub

Version control/Code repo: GitHub

For our code repository and versioning software, we use GitHub. We also use the commenting system in GitHub.

Task-tracking: DailyStat.us

Task-tracking: DailyStat.us

This app helps us keep tabs on our teammates’ tasks. This allows us to show each other what we finished yesterday, what we’re working on today, and what we need help with.

Other Things to Keep in Mind

Again, we can’t stress enough how important frequent communication really is to the success of a distributed team.

Also, we want to say that, just like riding a bike, remote working takes practice and a bit of getting used to. Don’t get discouraged if after a couple of months things don’t seem to be working out.

After a while, for example, planning and communicating just became second nature to us.

We like to set scheduled meeting times throughout the week where we’re communicating over video for brainstorming.

We also like to do quick daily video chats sometimes just to say "Hi, how’s it going?"

The way we see it, we also have to maintain personal work relationships — that non-distributed design teams have traditionally benefited from — as well.

Are you part of a remote team? What helps you stay connected and battle the communication gap? Give your advice in the comments below.

Related Content

About the Authors

Noah Coffey is a UX Developer at Formstack – an app that helps you design and build powerful online forms with no coding knowledge – where he creates and brings focus to the user experience of the application. Outside of work, Noah loves his time as a father, watching the Colts, and working with local charities and nonprofits. Connect with Noah on Twitter.

Aaron White is a UX Developer at Formstack where he works on streamlining the form-building process for users. Aaron is a proud father and veteran of the U.S. Army. He’s one of the company’s remote employees: Aaron works out of Bloomington, Indiana at a coworking space he founded called Cowork Btown. Connect with Aaron on Twitter.

The post How to Make Distributed Design Teams Work appeared first on Six Revisions.


What, it’s been two years already? That’s how long it took me to fill in my dotted Leuchtturm notebook (German engineering at its finest) front to back. Since I’m starting a new one, I thought to devise a bit of a color coding system for my upcoming notes and just share it here. The colors I typically use to underline the very first page title. Here are the colors:

Light Grey For Thoughts & Inspirations

Sometimes I’ll hear or read something of interest from a podcast, article, or book and it gets coded this way. My own free-form personal random thoughts across various disciplines get placed here as well.

Medium Grey For Project Ideas

For the more solid, practical and actionable thoughts or sketches. These are both new project ideas or adjustments to existing ones and are often accompanies by sketched out screens.

Black For Business Strategies

These are the most strict, closest and firm action points which are tied to my business initiatives. They are very high level for the most part and act as strategic todo’s of sorts.

Red For Contacts

If I meet someone or a company of interest, they will get placed here. This section might also be some residue from a conversation with someone over a cup of coffee.

Blue For UI Patterns

Here come the user interface patterns – both good and dark. Be it existing patterns seen somewhere or envisioned ones, they both land here.

Yellow For Content

I write and rely heavily for content marketing for much of my business. Specific content ideas for existing projects get placed here. Oh, and in the example listed you can actually see that I’ve started scribbling down some content points for the GoodUI Datastories promotions. :)

Was this helpful? How do you structure your notebooks or sketchbooks?

Credits: Jakub Linowski

A wireframe is not the same as a prototype but even seasoned design professionals can sometimes get the two terms mixed up.

It’s time to set things straight once and for all, since (semantics aside) the difference between a wireframe and a prototype is actually quite substantial.

Editor’s note: This is an article by Marcin Treder, CEO of UXPin.

Wireframe

A wireframe is a low-fidelity representation of a product’s design.

It has three simple objectives; the clear presentation of:

  1. Main groups of information
  2. Layout/structure of information
  3. Core visualization and descriptions of user interface interactions

Wireframes, if properly created, serve as the backbone of the product.

It’s just like an architectural blueprint of a house: It states plainly and clearly what should go where.

Visual Characteristics of a Wireframe

The visual characteristics of a wireframe are very limited. Usually designers just use boxes, lines, and a grayscale color palette (to represent different levels of visual hierarchy in the design).

A simple vector wireframe

The majority of the final content — images, videos, text, etc. — is left out for later stages of the process. Often, these omitted parts of the interface are represented by placeholders. Images tend to be represented by crossed boxes and text with Lorem ipsum.

Benefits of Wireframing

Since wireframes are quick and cheap to produce — especially when you use dedicated wireframing software such as UXPin, Balsamiq, or Axure — they should be used right at the beginning of the design process.

There’s nothing better for gathering feedback early on than a solid wireframe.

Why?

Because people can focus more on function, information architecture, UX, user flow, usability, user interactions, and so on, rather than having these foundational aspects of a design being overshadowed by its aesthetics.

In addition, any required changes can be done quickly without too many tedious code and graphics-editor adjustments.

This video that my startup put together shows how easy wireframing can be.

Interactive Wireframe (or Clickable Wireframe)

Sometimes designers like to increase the fidelity of their work a bit to stress the importance of certain parts of the UI, as well as to present and quickly test the soundness of interactions between elements. A very popular way of doing that quickly is the creation of an interactive wireframe, also known as a clickable wireframe.

A more sophisticated wireframe designed using UXPin, a specialized wirefaming/prototyping tool

Interactive wireframes might be very helpful on the first presentation of a design to a stakeholder or client. If you’ve ever heard the classic question "What happens if I click this button?" you will have the answer right on your interactive wireframe. It’s impressive and engaging.

Being Careful with the Presentation of Wireframes

To a layman, e.g. our project clients or non-technical managers/employers, looking at a wireframe might be perplexing because wireframes might not have any resemblance to the final design at all.

Quick hand-sketched wireframing of an app’s user flow by Fernando Guillen

That’s why we need to take some time to explain what a wireframe is — and, more importantly, its significance within the design process — before we show it to individuals that are uninitiated to the concept of wireframes.

Prototype

A prototype is a mid- to high-fidelity representation of the final user interface.

The goal of a prototype is straightforward: Simulate the interaction between the user and the interface.

Whenever a button is clicked, the appropriate action must occur, mimicking the experience of a full product.

Visual Characteristics of a Prototype

When it comes to aesthetics, a prototype may closely resemble the final version of the product.

Basically, a prototype looks like the final product, but it just doesn’t have the nuts-and-bolts yet (i.e. HTML, CSS, JS, server-side programming, databases, etc.)

Interactive prototype designed in UXPin

Primary colors should be all set, key content (at least the essential pieces) must be present, IA should be demonstrated, and typography should, to a reasonable extent, represent the final version. Clicking on an interactive object should demonstrate its subsequent response.

Benefits of Prototyping

Why is prototyping important? Because prototypes are typically for testing a product with real users. Early testing of prototypes can save tons of money and time that would have gone toward developing the wrong interface and back-end product architecture. It is a good validation tool for the design and development of the product.

In addition, showing a prototype to users and asking them to go through some basic use-cases is amazingly insightful and inspiring for the entire team.

Instead of spending time coding the prototype, designers today can engage in a rapid and cost-effective prototyping process using software that I’ll talk about in a bit.

Any changes you need to make after user-testing can be implemented more quickly, without wasting the time of your engineers.

Design Workflow

Understanding the very nature of design, and the difference between wireframes and prototypes, is really just the entry point to the world of user experience design.

The magic happens when you’re able to combine the many pieces of the process into a cohesive, effective, and efficient workflow.

When I was managing a UX design department a few of years back, the biggest mistake I saw in our process was this: We treated wireframes as disposable and non-essential. So we would rush the process and we wouldn’t give the wireframing process the time and effort it deserves. They were too sketchy and messy to be used as a blueprint — the foundational backbone — of a solid prototype and the final product.

A Few Tips

  • While wireframing, create reusable elements that can be edited so that when you’re in the prototyping stage, you can simply just refine those elements
  • Make sure that when the wireframe is done, it represents the latest feedback from your teammates and stakeholders
  • Use software to your advantage

Wireframing and Prototyping Software

I’ll end with a list of tools you can use to make wireframing and prototyping easier.

Below you’ll find some of the most popular wireframing and prototyping tools, including the one my company has developed.

Test them (most have some sort of free trial) and choose the weapon that fits you and your team best!

UXPin

We have over 900 UI elements ready to be used on wireframes and prototypes. Please feel free to ask me questions about it in the comments.

UXPin

Proto.io

A very robust prototyping tool that can output HTML/CSS and demonstrate touchscreen interactions. Prototypes can be tested in actual devices.

Proto.io

Balsamiq

A very popular, longstanding, and easy to use wireframing app. Limited to static wireframing only though.

Balsamiq

Moqups

Allows for wireframing in the browser.

Moqups

Mockingbird

A simple wireframing tool. Product development stopped in 2010.

Mockingbird

Axure

A wireframing and prototyping app that’s popular in the enterprise software sector.

Axure

Protoshare

Wireframing and prototyping in the browser.

Protoshare

InvisionApp

Allows you to build functional prototypes using your existing designs. You can’t draw anything, but you can add links between screenshots.

InvisionApp

Related Content

About the Author

Marcin Treder is a UX designer, the CEO of UXPin, and author of several UX design books (such as UX Design for Startups).

The post Wireframes vs. Prototypes: What’s the Difference? appeared first on Six Revisions.

CSS3 gives designers many new properties and modules (like the CSS Animations and CSS Transitions modules) that allow them to add fascinating interactivity onto their work.

If you want to take advantage of these modern CSS capabilities, one quick way to do that would be to use (or study) CSS effects libraries. Let me talk about a few open source collections of CSS that will help you craft great transitional interfaces.

1. Animate.css

Animate.css

Animate.css is a collection of over 60 CSS effects by Daniel Eden, a designer at Dropbox. Daniel Eden’s work on Animate.css is an inspiration to some of the other CSS effects libraries below.

2. Hover.css

Hover.css

This is a huge collection of 48 CSS3 hover effects by front-end developer, Ian Lunn. What’s cool about Hover.css is it comes with a SASS version, which is really, really handy for a whole lot of us.

3. fancyInput

fancyInput

fancyInput deals specifically with interactions related to your HTML <input> and <textarea> elements. It gives you the ability to implement interesting CSS effects when users type into your form fields.

4. magic

magic

(Note: The link above goes to an Italian-language website.)

magic is an interesting collection of CSS3 effects. The magic project is inspired by Daniel Eden’s work on Animate.css and is by an Italian developer who goes by the moniker, miniMAC.

With magic, you can easily trigger CSS animations and transitions using jQuery (or your preferred JavaScript front-end web development framework) simply by setting event listeners on your target HTML objects and then adding/removing the magic-specific CSS animation classes when the event occurs.

For example, say we have a button called #submit-button and we wanted to remove it from the DOM — which is a design pattern for critical interactions where you don’t want users to keep clicking on a button that’s intended to be pressed only once — but we wanted to do it in an impressive, transitional way to make sure the user doesn’t get confused and left wondering where the button went, all we would need to do is this (using jQuery):

$('#submit-button').click(function(){
  $(this).addClass('magictime vanishOut')
});

5. Effeckt.css

Effeckt.css

Effeckt.css — which is still a work in progress — is a Mobile First library of animation and transition CSS effects. The effects included are contributed and curated by designers to make sure they’re tasteful. Effeckt.css strongly emphasizes on performance, one criteria being if it can’t run well at 60fps on mobile devices, it’s out. Read the 9 goals of Effeckt.css and watch the project’s 22-second video on YouTube to get a glimpse of Effeckt.css’s future.

This isn’t an exhaustive list of CSS effects libraries. I’m sure I’ve missed some equally great projects out there. If you know of an open source project that should’ve been on this list, or if you’re working on one, please share it with us in the comments. Thanks!

Related Content

About the Author

Jacob Gube is the founder of Six Revisions. He’s a front-end web developer by profession. If you’d like to connect with him, head on over to the contact page or follow him on Twitter: @sixrevisions.

The post 5 CSS Effects Libraries for Supercharging Your Designs appeared first on Six Revisions.

CSS3 gives designers many new properties and modules (like the CSS Animations and CSS Transitions modules) that allow them to add fascinating interactivity onto their work.

If you want to take advantage of these modern CSS capabilities, one quick way to do that would be to use (or study) CSS effects libraries. Let me talk about a few open source collections of CSS that will help you craft great transitional interfaces.

1. Animate.css

Animate.css

Animate.css is a collection of over 60 CSS effects by Daniel Eden, a designer at Dropbox. Daniel Eden’s work on Animate.css is an inspiration to some of the other CSS effects libraries below.

2. Hover.css

Hover.css

This is a huge collection of 48 CSS3 hover effects by front-end developer, Ian Lunn. What’s cool about Hover.css is it comes with a SASS version, which is really, really handy for a whole lot of us.

3. fancyInput

fancyInput

fancyInput deals specifically with interactions related to your HTML <input> and <textarea> elements. It gives you the ability to implement interesting CSS effects when users type into your form fields.

4. magic

magic

(Note: The link above goes to an Italian-language website.)

magic is an interesting collection of CSS3 effects. The magic project is inspired by Daniel Eden’s work on Animate.css and is by an Italian developer who goes by the moniker, miniMAC.

With magic, you can easily trigger CSS animations and transitions using jQuery (or your preferred JavaScript front-end web development framework) simply by setting event listeners on your target HTML objects and then adding/removing the magic-specific CSS animation classes when the event occurs.

For example, say we have a button called #submit-button and we wanted to remove it from the DOM — which is a design pattern for critical interactions where you don’t want users to keep clicking on a button that’s intended to be pressed only once — but we wanted to do it in an impressive, transitional way to make sure the user doesn’t get confused and left wondering where the button went, all we would need to do is this (using jQuery):

$('#submit-button').click(function(){
  $(this).addClass('magictime vanishOut')
});

5. Effeckt.css

Effeckt.css

Effeckt.css — which is still a work in progress — is a Mobile First library of animation and transition CSS effects. The effects included are contributed and curated by designers to make sure they’re tasteful. Effeckt.css strongly emphasizes on performance, one criteria being if it can’t run well at 60fps on mobile devices, it’s out. Read the 9 goals of Effeckt.css and watch the project’s 22-second video on YouTube to get a glimpse of Effeckt.css’s future.

This isn’t an exhaustive list of CSS effects libraries. I’m sure I’ve missed some equally great projects out there. If you know of an open source project that should’ve been on this list, or if you’re working on one, please share it with us in the comments. Thanks!

Related Content

About the Author

Jacob Gube is the founder of Six Revisions. He’s a front-end web developer by profession. If you’d like to connect with him, head on over to the contact page or follow him on Twitter: @sixrevisions.

The post 5 CSS Effects Libraries for Supercharging Your Designs appeared first on Six Revisions.

CSS3 gives designers many new properties and modules (like the CSS Animations and CSS Transitions modules) that allow them to add fascinating interactivity onto their work.

If you want to take advantage of these modern CSS capabilities, one quick way to do that would be to use (or study) CSS effects libraries. Let me talk about a few open source collections of CSS that will help you craft great transitional interfaces.

1. Animate.css

Animate.css

Animate.css is a collection of over 60 CSS effects by Daniel Eden, a designer at Dropbox. Daniel Eden’s work on Animate.css is an inspiration to some of the other CSS effects libraries below.

2. Hover.css

Hover.css

This is a huge collection of 48 CSS3 hover effects by front-end developer, Ian Lunn. What’s cool about Hover.css is it comes with a SASS version, which is really, really handy for a whole lot of us.

3. fancyInput

fancyInput

fancyInput deals specifically with interactions related to your HTML <input> and <textarea> elements. It gives you the ability to implement interesting CSS effects when users type into your form fields.

4. magic

magic

(Note: The link above goes to an Italian-language website.)

magic is an interesting collection of CSS3 effects. The magic project is inspired by Daniel Eden’s work on Animate.css and is by an Italian developer who goes by the moniker, miniMAC.

With magic, you can easily trigger CSS animations and transitions using jQuery (or your preferred JavaScript front-end web development framework) simply by setting event listeners on your target HTML objects and then adding/removing the magic-specific CSS animation classes when the event occurs.

For example, say we have a button called #submit-button and we wanted to remove it from the DOM — which is a design pattern for critical interactions where you don’t want users to keep clicking on a button that’s intended to be pressed only once — but we wanted to do it in an impressive, transitional way to make sure the user doesn’t get confused and left wondering where the button went, all we would need to do is this (using jQuery):

$('#submit-button').click(function(){
  $(this).addClass('magictime vanishOut')
});

5. Effeckt.css

Effeckt.css

Effeckt.css — which is still a work in progress — is a Mobile First library of animation and transition CSS effects. The effects included are contributed and curated by designers to make sure they’re tasteful. Effeckt.css strongly emphasizes on performance, one criteria being if it can’t run well at 60fps on mobile devices, it’s out. Read the 9 goals of Effeckt.css and watch the project’s 22-second video on YouTube to get a glimpse of Effeckt.css’s future.

This isn’t an exhaustive list of CSS effects libraries. I’m sure I’ve missed some equally great projects out there. If you know of an open source project that should’ve been on this list, or if you’re working on one, please share it with us in the comments. Thanks!

Related Content

About the Author

Jacob Gube is the founder of Six Revisions. He’s a front-end web developer by profession. If you’d like to connect with him, head on over to the contact page or follow him on Twitter: @sixrevisions.

The post 5 CSS Effects Libraries for Supercharging Your Designs appeared first on Six Revisions.

Mainstream blogging platforms like WordPress, Blogger, Tumblr, etc. aren’t designed for hackers. They’re encumbered by features developers just don’t need or want.

And, out of the box, the popular blogging platforms certainly lack a lot things coders actually would want, such as code syntax highlighting, blog theming capabilities using a standardized templating engine, markup language support besides HTML, and integration with source code repositories, among other things.

If you’re looking for a blogging solution that’s programmer-friendly, you’ve come to the right place. The free and open source blogging platforms I’ll talk about are designed with the needs of developers in mind, and not their moms’ (unless she likes to code too).

Hexo

Hexo

Hexo is a blogging platform powered by Node.js (it says so right there in the site’s tagline).

Its hacker-friendly features include native support for GitHub Flavored Markdown (GMF) as well as templating and extensibility capabilities using EJS, Swig and Stylus.

Installing Hexo will take you but a few seconds, assuming you already have npm set up and ready to go. Boom:

$ npm install hexo -g

Fun tangential fact: "npm" doesn’t stand for Node packaged modules or Node Package Manager. It’s a recursive acronym like PHP. Or more accurately: "It’s a recursive bacronymic abbreviation because it stands for ‘npm is not an acronym’," as the author explains. [Source]

Jekyll

Jekyll

Jekyll is a static site generator that compiles your markup files into Web-ready HTML documents — that’s what all static site generators do, more or less — the value proposition being better Web performance and the option to ditch your databases and server-side scripts.

Jekyll has a steady-growing ecosystem, as evidenced by the other open source projects being developed for it:

  • Octopress – a blogging framework designed for hackers
  • JekyllBootstrap – makes it easier for you to use your GitHub Pages to host your blog for free
  • Exitwp – helps you move from WordPress to Jekyll

Jekyll can be installed as a Ruby Gem:

gem install jekyll

Anchor CMS

Anchor CMS

Anchor CMS is a featherweight; the project’s source code .zip archive is just a little over 200 KB.

Off the bat, Anchor supports Markdown syntax, which a lot of coders feel is easier and more natural for blog-writing and formatting. It also supports art-directed blogging, i.e., you can easily make each post look different.

Wheat

Wheat is truly cool: It pulls articles from your GitHub repo and then publishes it to your website. Imagine the possibilities! Like open source blogging where other hackers can issue pull requests for correcting and improving your blog posts.

Wheat is developed with Node.js and can be installed as a Node packaged module:

npm install wheat

Nikola

Nikola

Nikola, a static site generator, is strongly blog-oriented but it can also be used for any other type of website. Code wranglers will love the fact that it has a small codebase, which the creator of Nikola deems as an advantage because it means "programmers can understand all of Nikola core in a day."

Nikola supports a whole slew of markup languages: reStructuredText, Markdown, etc. And, of course, HTML will do just fine too if that’s how you roll.

toto

Stolen straight off its repo description: toto is "the 10 second blog-engine for hackers."

toto is a minimalist blogging engine that runs on Git, which means you can version-control your posts just like you would when you’re writing code.

Poet

Poet

Poet is another Node.js-powered blogging platform. What makes it unique is the project’s snooty character mascot. Just kidding.

What’s notable about Poet is it gives you the ability to write your blog posts using a markup language you’re comfortable in, whether it’s Markdown, Jade or whatever you want. Also, customizing routes for your blog posts and other pages is simple.

Dropplets

Dropplets is a minimalist Markdown blogging platform. Its purposefully limited feature set helps makes sure you spend more time writing and less time tinkering.

Pelican

Pelican

Pelican is another static site generator, but it’s written in Python. It supports reStructuredText, Markdown, or AsciiDoc markup. It has code syntax highlighting right out of the box, and an importing feature for data coming from other publishing platforms such WordPress. Theming can be done using Jinja2.

Wardrobe

Wardrobe

Wardrobe is a minimalist blogging platform with a simple UI that will help you focus on writing. Wardrobe is developed with PHP. It’s very similar to Anchor CMS.

Bolt

Bolt

Bolt is a full-on content management system, so you can use it for other purposes outside of blogging. It uses Twig for templating and comes with its own Symphony debug bar for tracing code issues. And, with absolutely no magic required, you actually get to choose which relational database management system to use for a change: SQLite, MySQL or PostgreSQL. Need more reasons? How about this: Bolt was built with the assumption that you might actually want to run unit tests on your CMS; it supports PHPUnit natively.

Shout out to the awesome Six Revisions readers who pointed me to some excellent open source blogging platforms via the comments of another related post.

Related Content

About the Author

Jacob Gube is the founder of Six Revisions. He’s a front-end web developer by profession. If you’d like to connect with him, head on over to the contact page or follow him on Twitter: @sixrevisions.

The post 10 Open Source Blogging Platforms for Developers appeared first on Six Revisions.

Mainstream blogging platforms like WordPress, Blogger, Tumblr, etc. aren’t designed for hackers. They’re encumbered by features developers just don’t need or want.

And, out of the box, the popular blogging platforms certainly lack a lot things coders actually would want, such as code syntax highlighting, blog theming capabilities using a standardized templating engine, markup language support besides HTML, and integration with source code repositories, among other things.

If you’re looking for a blogging solution that’s programmer-friendly, you’ve come to the right place. The free and open source blogging platforms I’ll talk about are designed with the needs of developers in mind, and not their moms’ (unless she likes to code too).

Hexo

Hexo

Hexo is a blogging platform powered by Node.js (it says so right there in the site’s tagline).

Its hacker-friendly features include native support for GitHub Flavored Markdown (GMF) as well as templating and extensibility capabilities using EJS, Swig and Stylus.

Installing Hexo will take you but a few seconds, assuming you already have npm set up and ready to go. Boom:

$ npm install hexo -g

Fun tangential fact: "npm" doesn’t stand for Node packaged modules or Node Package Manager. It’s a recursive acronym like PHP. Or more accurately: "It’s a recursive bacronymic abbreviation because it stands for ‘npm is not an acronym’," as the author explains. [Source]

Jekyll

Jekyll

Jekyll is a static site generator that compiles your markup files into Web-ready HTML documents — that’s what all static site generators do, more or less — the value proposition being better Web performance and the option to ditch your databases and server-side scripts.

Jekyll has a steady-growing ecosystem, as evidenced by the other open source projects being developed for it:

  • Octopress – a blogging framework designed for hackers
  • JekyllBootstrap – makes it easier for you to use your GitHub Pages to host your blog for free
  • Exitwp – helps you move from WordPress to Jekyll

Jekyll can be installed as a Ruby Gem:

gem install jekyll

Anchor CMS

Anchor CMS

Anchor CMS is a featherweight; the project’s source code .zip archive is just a little over 200 KB.

Off the bat, Anchor supports Markdown syntax, which a lot of coders feel is easier and more natural for blog-writing and formatting. It also supports art-directed blogging, i.e., you can easily make each post look different.

Wheat

Wheat is truly cool: It pulls articles from your GitHub repo and then publishes it to your website. Imagine the possibilities! Like open source blogging where other hackers can issue pull requests for correcting and improving your blog posts.

Wheat is developed with Node.js and can be installed as a Node packaged module:

npm install wheat

Nikola

Nikola

Nikola, a static site generator, is strongly blog-oriented but it can also be used for any other type of website. Code wranglers will love the fact that it has a small codebase, which the creator of Nikola deems as an advantage because it means "programmers can understand all of Nikola core in a day."

Nikola supports a whole slew of markup languages: reStructuredText, Markdown, etc. And, of course, HTML will do just fine too if that’s how you roll.

toto

Stolen straight off its repo description: toto is "the 10 second blog-engine for hackers."

toto is a minimalist blogging engine that runs on Git, which means you can version-control your posts just like you would when you’re writing code.

Poet

Poet

Poet is another Node.js-powered blogging platform. What makes it unique is the project’s snooty character mascot. Just kidding.

What’s notable about Poet is it gives you the ability to write your blog posts using a markup language you’re comfortable in, whether it’s Markdown, Jade or whatever you want. Also, customizing routes for your blog posts and other pages is simple.

Dropplets

Dropplets is a minimalist Markdown blogging platform. Its purposefully limited feature set helps makes sure you spend more time writing and less time tinkering.

Pelican

Pelican

Pelican is another static site generator, but it’s written in Python. It supports reStructuredText, Markdown, or AsciiDoc markup. It has code syntax highlighting right out of the box, and an importing feature for data coming from other publishing platforms such WordPress. Theming can be done using Jinja2.

Wardrobe

Wardrobe

Wardrobe is a minimalist blogging platform with a simple UI that will help you focus on writing. Wardrobe is developed with PHP. It’s very similar to Anchor CMS.

Bolt

Bolt

Bolt is a full-on content management system, so you can use it for other purposes outside of blogging. It uses Twig for templating and comes with its own Symphony debug bar for tracing code issues. And, with absolutely no magic required, you actually get to choose which relational database management system to use for a change: SQLite, MySQL or PostgreSQL. Need more reasons? How about this: Bolt was built with the assumption that you might actually want to run unit tests on your CMS; it supports PHPUnit natively.

Shout out to the awesome Six Revisions readers who pointed me to some excellent open source blogging platforms via the comments of another related post.

Related Content

About the Author

Jacob Gube is the founder of Six Revisions. He’s a front-end web developer by profession. If you’d like to connect with him, head on over to the contact page or follow him on Twitter: @sixrevisions.

The post 10 Open Source Blogging Platforms for Developers appeared first on Six Revisions.

Mainstream blogging platforms like WordPress, Blogger, Tumblr, etc. aren’t designed for hackers. They’re encumbered by features developers just don’t need or want.

And, out of the box, the popular blogging platforms certainly lack a lot things coders actually would want, such as code syntax highlighting, blog theming capabilities using a standardized templating engine, markup language support besides HTML, and integration with source code repositories, among other things.

If you’re looking for a blogging solution that’s programmer-friendly, you’ve come to the right place. The free and open source blogging platforms I’ll talk about are designed with the needs of developers in mind, and not their moms’ (unless she likes to code too).

Hexo

Hexo

Hexo is a blogging platform powered by Node.js (it says so right there in the site’s tagline).

Its hacker-friendly features include native support for GitHub Flavored Markdown (GMF) as well as templating and extensibility capabilities using EJS, Swig and Stylus.

Installing Hexo will take you but a few seconds, assuming you already have npm set up and ready to go. Boom:

$ npm install hexo -g

Fun tangential fact: "npm" doesn’t stand for Node packaged modules or Node Package Manager. It’s a recursive acronym like PHP. Or more accurately: "It’s a recursive bacronymic abbreviation because it stands for ‘npm is not an acronym’," as the author explains. [Source]

Jekyll

Jekyll

Jekyll is a static site generator that compiles your markup files into Web-ready HTML documents — that’s what all static site generators do, more or less — the value proposition being better Web performance and the option to ditch your databases and server-side scripts.

Jekyll has a steady-growing ecosystem, as evidenced by the other open source projects being developed for it:

  • Octopress – a blogging framework designed for hackers
  • JekyllBootstrap – makes it easier for you to use your GitHub Pages to host your blog for free
  • Exitwp – helps you move from WordPress to Jekyll

Jekyll can be installed as a Ruby Gem:

gem install jekyll

Anchor CMS

Anchor CMS

Anchor CMS is a featherweight; the project’s source code .zip archive is just a little over 200 KB.

Off the bat, Anchor supports Markdown syntax, which a lot of coders feel is easier and more natural for blog-writing and formatting. It also supports art-directed blogging, i.e., you can easily make each post look different.

Wheat

Wheat is truly cool: It pulls articles from your GitHub repo and then publishes it to your website. Imagine the possibilities! Like open source blogging where other hackers can issue pull requests for correcting and improving your blog posts.

Wheat is developed with Node.js and can be installed as a Node packaged module:

npm install wheat

Nikola

Nikola

Nikola, a static site generator, is strongly blog-oriented but it can also be used for any other type of website. Code wranglers will love the fact that it has a small codebase, which the creator of Nikola deems as an advantage because it means "programmers can understand all of Nikola core in a day."

Nikola supports a whole slew of markup languages: reStructuredText, Markdown, etc. And, of course, HTML will do just fine too if that’s how you roll.

toto

Stolen straight off its repo description: toto is "the 10 second blog-engine for hackers."

toto is a minimalist blogging engine that runs on Git, which means you can version-control your posts just like you would when you’re writing code.

Poet

Poet

Poet is another Node.js-powered blogging platform. What makes it unique is the project’s snooty character mascot. Just kidding.

What’s notable about Poet is it gives you the ability to write your blog posts using a markup language you’re comfortable in, whether it’s Markdown, Jade or whatever you want. Also, customizing routes for your blog posts and other pages is simple.

Dropplets

Dropplets is a minimalist Markdown blogging platform. Its purposefully limited feature set helps makes sure you spend more time writing and less time tinkering.

Pelican

Pelican

Pelican is another static site generator, but it’s written in Python. It supports reStructuredText, Markdown, or AsciiDoc markup. It has code syntax highlighting right out of the box, and an importing feature for data coming from other publishing platforms such WordPress. Theming can be done using Jinja2.

Wardrobe

Wardrobe

Wardrobe is a minimalist blogging platform with a simple UI that will help you focus on writing. Wardrobe is developed with PHP. It’s very similar to Anchor CMS.

Bolt

Bolt

Bolt is a full-on content management system, so you can use it for other purposes outside of blogging. It uses Twig for templating and comes with its own Symphony debug bar for tracing code issues. And, with absolutely no magic required, you actually get to choose which relational database management system to use for a change: SQLite, MySQL or PostgreSQL. Need more reasons? How about this: Bolt was built with the assumption that you might actually want to run unit tests on your CMS; it supports PHPUnit natively.

Shout out to the awesome Six Revisions readers who pointed me to some excellent open source blogging platforms via the comments of another related post.

Related Content

About the Author

Jacob Gube is the founder of Six Revisions. He’s a front-end web developer by profession. If you’d like to connect with him, head on over to the contact page or follow him on Twitter: @sixrevisions.

The post 10 Open Source Blogging Platforms for Developers appeared first on Six Revisions.

Powered by WP Robot