Created
February 16, 2011 19:15
-
-
Save BiosElement/829951 to your computer and use it in GitHub Desktop.
A draft concept for a Pyramid application series.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| BIOS | |
| Basically Intelligent Operational Systems | |
| ----------------------------------------- | |
| BIOS is intended to be a collection of applications designed to be built on | |
| to create an entire website. It can be compared to Drupal. | |
| bios_auth | |
| --------- | |
| User auth system. | |
| bios_board | |
| ---------- | |
| Message board, note board and task tracker. | |
| NOTE: Split task tracker into seperate app? - BiosElement | |
| bios_mail | |
| --------- | |
| E-mail, Personal message and contact form system. |
Author
1. Are there similar applications out there that solve the problems BIOS is intended to solve?
BIOS aims to be an integrated system, with a complete API and easy integration with external services. This sets it apart from most existing systems. The closest comparisons would probably be Drupal and Django.
- Drupal is a CMS which aims to be as basic as possible, moving all advanced functionality into 'modules'.
- Django is a python framework generally well suited to develop a CMS with. It has a system called 'apps' which basically allows multiple django websites to exist as a single 'site'. (Example: A blog app, a contact form app, ETC)
2) Is there a target market for this application suite?
BIOS was partially inspired by two key things: My experience as the Community Manager for an Open-Source Project and during my discussions with various leaders within the Open-Source community. These communities face many of the same problems that exist within large enterprise organizations and they have the general advantage of being more nimble, rapidly updating their systems as the need arises. And yet they still face problems such as these:
- Flexibility: Many systems are designed for a single purpose.
- Integration: Blogs, Contact systems, E-Mail, Forums, Task-Tracking, all of these are generally separate systems. This is silly, because there are many advantages to loose integration. Single-Sign-On and Major workflow improvements (Such as sending an e-mail directly to your task tracker or forwarding it to a blog.) would greatly benefit anyone.
- Duplicated Effort: Simply put, it's silly to solve the same problem dozens of time without bringing anything new to the table. There are at least a dozen popular CMS systems, each with their own advantages/disadvantages. Why not try to combine some of that effort to create a truly better system?
- Freedom: Keeping the system open-source ensures it won't vanish overnight. While many of the most popular CMS's are Free/Open-Source, not all of them are and some are moving towards a closed-source model.
- Self-Hosted: Host your own BIOS system for a highly-custom solution or host it with the official BIOS system and don't worry about server maintainer again.
- Linking: Linking BIOS systems hosted by other groups would extend the integration further and offer awesome ways for groups to work together.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
#1 are there similar applications out there that solve the problems BIOS is intended to solve?
#2 is there a target market for this application suite?
2a) for each answer to #2, answer this: how will they benefit from BIOS as compared to similar suites such as 37signals' BaseCamp (and answers to question #1)?
#3) are there any other questions you can think of to ask about BIOS if you knew nothing about it? if so list them.
3a) for each answer (question) to #3, list and answer them, and then keep thinking.