Monday, May 23, 2016

tl;dr: What belongs on a developer website? Below is my page as the public has seen it for about seven...

tl;dr: What belongs on a developer website?

Below is my page as the public has seen it for about seven years. Clearly, I have not seen changing this site as a valuable use of my time.

I'm beginning to rethink that, in oh so many ways. Should I keep it where it is? (probably not) Should I use the work-related page I have? (probably not) Should I use GitHub hosting? Should I use blogging platform like Tumblr or Blogspot? (less emphatically probably not, but probably not) Should I get a Digital Ocean VM or something and host from there?

I'm at the point of deciding I'll make it static, template-generated and the like. If there's no dynamic content, there's no point of attack.

Which leads to the next question: What goes on a developer site? What is the point?

Most developer sites I see are blogs. I do blog. My tech-related blog is /var/log/rant and my music-related blog is Sans Direction. I don't want that to be my main face, because that requires me to either blog a lot or let it seem not current and abandoned. Certainly pointers to places where I am active (blogs, various social media outlets) is more the thing. But I'm curious about what I should put.

Also, most developer sites I see are based on the aesthetics of earlier points in the evolution of the web. Like, "that developer stopped caring in 2005" or the like.

So, what are the crucial must-haves for a developer site? What are the that's-good points? What should I absolutely not do?

No comments:

Post a Comment