1. knowledge management
1.1. code commenting
1.2. trac
1.3. mantis - bug tracking
1.4. wiki
2. framework vs pure code vs cms
2.1. frameworks
2.1.1. http://www.phpframeworks.com/
2.1.2. Cake
2.1.2.1. http://cakephp.org/
2.1.3. Zend Framework
2.1.3.1. for libraries
2.1.4. to look into Yii
3. technology selection
3.1. DB
3.1.1. mysql
3.1.1.1. optimisation
3.1.1.2. engine: innodb vs PBXT
3.1.1.2.1. BLOB Streaming Infrastructure
3.1.2. postgresql
3.2. business logic
3.2.1. php
3.2.1.1. php5
3.3. interactivity
3.3.1. jquery
3.3.1.1. bigger community / more evolved
3.3.2. prototype
3.3.3. ExtJS
3.3.4. GWT
3.4. OS
3.4.1. debian - Linux
3.5. webserver
3.5.1. lighttpd
3.5.1.1. specially good at static content serving
3.5.2. apache
4. sw development
4.1. scrum
4.2. UML
4.2.1. use case diagrams and use case descriptions
4.3. object oriented
4.3.1. php5
4.4. svn / git
4.4.1. svn
4.5. dev environment
4.5.1. eclipse / aptana
5. hosting
5.1. cloud computing
5.1.1. amazon
5.1.1.1. EC2 and S3
5.1.2. www.gogrid.com
5.1.2.1. 100%SLA Low latency
5.1.3. www.rackspacecloud.com
5.1.3.1. 100%SLA
5.1.3.2. cloud and dedicated servers
5.1.3.3. CDN available
5.1.4. www.rightscale.com
5.1.4.1. load balancing product
5.1.4.2. cloud management
5.1.5. www.flexiscale.com
5.1.5.1. UK based
5.1.6. http://hp.sys-con.com/node/665165
5.2. centralised hosting
5.2.1. where?
5.2.1.1. amsterdam
5.2.1.1.1. http://easyspeedy.com/servers/high_performance_dedicated_servers.jsf
5.2.1.1.2. http://www.leaseweb.com/
5.2.1.2. london
5.2.1.2.1. http://www.easynetconnect.net/Products/Dedicated-Server-Solution.aspx
5.2.2. cdn
5.2.2.1. limelight integration offered by rackspacecloud
6. server architecture
6.1. for 1 to 3 customer
6.1.1. parameters
6.1.1.1. transference per day
6.1.1.1.1. delivery
6.1.2. setup
6.1.2.1. 2 servers
6.1.2.1.1. 1 db server
6.1.2.1.2. 1 app/web server
6.2. for above 3 customers
6.2.1. parameters
6.2.1.1. transference per day
6.2.1.1.1. delivery
6.2.2. setup