If anyone has ideas for something that should be added. Post here.
So far I plan to include:
Libraries
Repository
Request
Dependencies
Information
Glossary
Parts List
Circuit List
FAQ
Debugging
Resources
Projects
Mentors
Feedback
Bugs
Suggestions
This will ultimately be a collaboration project, kind of like a wiki, where you create a user, and can add to all categories via tools the site will provide.
I don't like the Troubleshooting page here: it needs to be at least organized into Hardware and Software; it doesn't seem to be editable by the general population; there doesn't appear to be anything about debugging the Sketch (no tips about using Serial).
Just today I had a Sketch that used too much SRAM. It would run fine for a few loops and then start spitting out gibberish. It took me about two hours to realize what was wrong :'(. I'd like to pass that knowledge on but where is a good place?
Hello!
First I want to warmly welcome the idea - a more organized and structured space will greatly benefit the community!
As I have (probably fairly good) experience designing and developing web based information systems, and maintaining a large Linux community site, and after looking at the initial design I have couple of questions :
What will be the underlying technology - PHP, perl, java?
What people are expected to develop and maintain it?
Do you know the technology you will use (PHP?) or you want to learn while creating?
As such tool (the one you want to create) is absolutely needed now (my own opinion) you might fall into some basic traps. First - the pressure from users to develop and later improve it will be big. This means that it will take (most of) your time, and if you still continue with your other projects it soon might feel neglected to the crowd.
I allow myself to humbly suggest two things. Quickly find someone to help you, probably two or three people. And because the need for helpers will rise stick to well know technology - PHP might be the best choice. If PHP is chosen then don't invent a framework, but use one. Suggestions - http://www.codeigniter.com, it's fork http://www.kohanaphp.com, or something similar. The guys developing codeigniter develop a commercial product - ExpresionEngine, that they might provide for free to the community and it contains many ready modules - forum, blog, news, wiki, etc.
The design basically does not matter given the audience :).
If I am being off topic or unnecessary elaborate on well known truths I humbly beg you to please excuse me.
Hello!
First I want to warmly welcome the idea - a more organized and structured space will greatly benefit the community!
I agree!
What will be the underlying technology - PHP, perl, java?
What people are expected to develop and maintain it?
Do you know the technology you will use (PHP?) or you want to learn while creating?
I will use PHP, and I know it. (Although I expect to learn while creating as well. Never know it all)
I expect myself to maintain and develop it at first. But anyone willing will not be rejected.
[edit]Technologies:
PHP
HTML/CSS
JavaScript
MySQL[/edit]
As such tool (the one you want to create) is absolutely needed now (my own opinion) you might fall into some basic traps. First - the pressure from users to develop and later improve it will be big. This means that it will take (most of) your time, and if you still continue with your other projects it soon might feel neglected to the crowd.
A good point.
But I actually do not fear it becoming a problem.
[edit]Because I already spend a lot of time on the arduino, the forums and the playground. And will have no trouble spending it on this site instead or in addition. Love the Arduino, and love contributing to the community.[/edit]
I allow myself to humbly suggest two things. Quickly find someone to help you, probably two or three people.
I will do that.
If PHP is chosen then don't invent a framework, but use one.
I will not do that.
I've found that I spend equal or less amount of time just writing what I want by my self. Twaking or forcing someonelses code just does not suit me.
This way it will be easy to get what I want. And to add what I need.
At least, in my experience.
(Two obvious exceptions: Wikis and forums)
If I am being off topic or unnecessary elaborate on well known truths I humbly beg you to please excuse me.
About the framework - it's up to you, and I personally feel that given the great amount of users, documentation and support in the PHP community it will be not so hard to move ahead.
I just referred to the framework issue as being important if the focus of your efforts is creating the community portal rather than fiddling with all the mundane tasks - the DB abstraction layer, user authentication, integration, web services, componentization, MVC abstraction etc.
And I can be of more help than only providing opinions :). Count me in.
Another suggestion: Find someone who's willing to be a technical editor. There's some great content on this site but, in my opinion, it needs to be better organized.
