Page 1 of 2
1 · 2

Daniel Hofstetter :: 18.06.2008 11:13:21
Personally, I don't see what the difference is between a "normal" CMS and a CMS from developers, for developers, so it is difficult to say what I would expect from such a CMS ;-)
Robert Scherer :: 18.06.2008 11:31:36
- No install routine -> Simple configuration

- No WYSIWYG, just Markdown and/or Textile

- Leave tickets and software roadmaps out, because you destroy the simplicity, you cannot develop such tools in a reasonable time and there is good software for it out there. So better think of a good solution to integrate applications in the CMS. Or viceversa. See Drake or Jake. Let me create a page in your CMS and enter PHP code that will be executed or written out there persistantly, so I'll get my ticket thing in there myself.

- Expandable. Let me add additional infos to the pages. If I don't do it with additional db fields, have a look at Felix Geisendörfer's Expandable Behavior (http://www.debuggable.com/posts/unlimited-model-fields-expandable-behavior:48428c2e-9a88-47ec-ae8e-77a64834cda3)

- Good, commented code. Bad code and debugging or adding something getting a bad dream is the worst for developers.

Just some ideas...
lecterror :: 19.06.2008 04:26:16
@Daniel: Well, my beef with "regular" CMS is the fact that they tend to over-generalize things and get too complicated. I'm aware of the fact that this only my point of view and probably not true. Still, what I want from a "developers" CMS is extreme simplicity, extreme usability and 0% maintenance. Basically, I want to publish software, code snippets and articles without the extra work.

@Robert:

- Would you say that the "no install routine" is already met by the alpha version of Neutrino? Or do you mean *absolutely* no install routing, not even the database initialization?
- WYSIWYG is out of the question, agreed.
- This is a good idea, maybe something like integration with MantisBT and similar..
- Expandable: what kind of additional data did you have in mind? A kind of private meta-data for your own usage, but related to the articles?

Thank you both for your comments!
Pranakhan :: 04.09.2008 13:27:04
Don't kill me... but: a really simple Wiki-like tool for capturing notes, docs, etc, from developer TEAMS. Wiki's are great for dev docs, especially during development (compliance not-withstanding), but the VAST majority of Wiki solutions have way more functionality than necessary. Google Code's is pretty nice, and I like how a table of all the related pages is always right there so you can add articles without having to bother thinking about ways of linking them together so they can be easily found and not orphaned. It would be nice to be able to easily associate these "Wiki" pages with other CMS object types, like add a Wiki page to a blog post, file download, heck even another Wiki page, and the CMS will always create a standard link/icon in the same place relative to the associated item.
Pranakhan :: 04.09.2008 13:27:27
The blog feature, I realize, can be used for capturing that kind of thing too, but devs in the biz world work in teams and only one of them would be authorized to edit a blog post and the rest would need to comment, its nicer if everyone can just mess up and spam a page together at whim.

Then, streamlined login for developer teams. As a matter of fact, do everything in your power to support as many commercial/open-source SSO solutions as you can in your login "module". So, if I'm logged into Windows and using IE8, it would be great if there was a way to configure it to just know who I am based on my Windows credentials, or whatever SSO solution I may have available.

Sorry, some of this may be off a bit, I'm just trying to brainspam quickly to help you out and keep you encouraged!

Pranakhan