prottmann

It could be a github-wiki page, so that everybody can add their components.

It is always hard to find matching components.

And grunt/gulp for complex projects. grunt, cause it is simpler than gulp, but only when it match the projects use case.

gulp for "live" things, like livereload or quick partial builds on developement.

Startet now to use webpack too, it is comfortable (campared with grunt), it does many build-stuff that you define in grunt by your own.

Like always, use the right tools to get the job done.

It exist not THE one and only tool that solve all problems in the world.

Thats why so many things changed too.

And the other thing is: why are all those things so successfully? People had enough from old fat frameworks, that where developed 10 years ago with a language from 15 or 20 years ago.

This old languages and frameworks did not fit to Web-Development, Apps, whatever... all the things that boomed since 2007.

Only you can answer: did you have enough people - and the matching people - to get the job in time X done and reach your goals?

You can compare your values only the similar startups, that work on the same problem. Then you now if you pay too much/less or use the wrong structures (inhouse / outsourcing / ...).

But most developers think, that when they learn once a Framework, they can use it for any kind of project.

When i read "xxx is really cool and fun" iam really careful. Most people create a "Hello World" and then THEIR favorite framework is the greatest thing in the universe and they communicate it to others.

Take a framework, live with the mistakes, until the next "better" framework appear... and it will appear, and the next, and .... ;)

Most of our customer projects use "old school" sql and only a few nosql-databases.

Waiting for Version 2 ;-)

For rest-api https://github.com/apidoc/apidoc

Within the doc you can add examples for usage and response.

But a some common pages with Tutorials / HowTos are nice and should be added to a good documentation. (it depend on the complexity of your project and your audience).

Last time i watch at RTD it was a plain .md project import from e.g. GitHub only to show a plain documentation.

In Readme.io you can edit/write your docs, have blog function and an integrated discussion plattform (for support your users). If you not need this features, you can use RTD or directly sphinx.

I really like your nice and clean template.

A similar project was in my mind since i create apiDoc, but due the lack of time i am happy now that you create such a project.

Will link to your site soon, so that apiDoc users can see your good alternative for creating and hosting a documentation.

Such software are working tools that save hundreds or thousands of dollars.

It is like the old discussion about the price of Microsoft Windows, or an Apple Mac, or Adobes Photoshop - oh my good, i call them all in one sentence ;-)

Yes they are expensive, but from the viewpoint of productivity, you make money with them and much more than they cost you.

I hope more developer have the courage and sell their work at reasonable prices.

Common Enduser surfin the web are an other species, but what should they seek on a github page ?

On a GitHub page are programming specific solutions for a problem a developer has.

When somebody search for a problem or find a link to a GitHub Project, he/she will visit the page.

All others don't have an urgent problem to solve, so you loose only users, that not need your solution. Can live with it. ;-)

I am a technican. I want to see the number of results. I don't like AutoSroll. I remember the page where i find a result, so i jump to the page, with endless scroll, i did not find things again.

The sign of clicked links is a good idea.

Mark a personal favorite site in combination with my search term would be a great feature. E.g. i remember i search something about nodejs but i forgot the sitename, my browser bookmark did not help me. But when i see my old search about "nodejs" and the favorite or clicked pages, that would be a great thing.

Forget google, if somebody want to use google, he can use google. So please implement usefull functions that help people with their daily work.

Fast and a really good documentation.

Its a pattern that you can watch on many IT-Projects.

Some "Key-People" like a project (for whatever reason) and a mass of developer follow them.

And than a thing get "standard" and more and more people use it.

* It's text-based, meaning it's readable and easy to parse.

* It has to be valid UTF-8, no hassle with other formats.

* Its numbers representation is double-precision floating-point, i can choose what i want.

Who cares? Use what you want and what solves your problem at the best way.

Node is a step into the right direction, but the Node.js way is only the base for building up new or other technoligies.

Yes programmers want to experiment with new things, but when programmers grow up, they want to use things that work without inventing the wheel again.

Node grow up now and it is exciting to see what node will be.

It seems that iam too old with my 35 years ;-) because i see things like node as a tool, a tool to solve a problem. I use node, but i did not say "yesssss it is the best thing in the world, wohoooooo" ;-)

If everybody thinks like you, than an iPhone was never invented ;-)

Most articles are so optimistic (because it is new, cool, make fun), that is hard to understand if the "tool" is the right one or not, you see it when you use it.

So i am glad to see when people / companies write about their expierence with the "new" technologies. Everybody can then verify if the tool is the right tool for a project/problem or not.

E. g. you write "If you are writing a web app to solve some business problem which sits behind a login angular really isn't a problem". When somebody read this, this person thinks "cool, angular is the right tool for a login backend application".