Isset Presentation @ EECI2009
1 like•342 views
The document outlines the approach of isset internet professionals to building custom web applications, highlighting their focus on database-driven development and effective project management practices. It emphasizes the importance of using CodeIgniter for its functionality, speed, and community support while addressing key aspects like SEO management, security measures, and source control. The presentation includes best practices for project organization, development processes, and communication strategies with clients to ensure successful project delivery.
Isset Presentation @ EECI2009
- 1. ISSET INTERNET PROFESSIONALS How to approach CI projects which go beyond the ‘homepage’
- 2. Who we are Jeroen van der Gulik Lead Developer Isset [email protected] Rommert van Til Project Manager [email protected]
- 3. What we do Isset Internet Professionals targets companies with an ambition on the internet. We provide solutions for problems related to the web using internet technology. Isset only works with professionals who are up to date on current internet problems as well as solutions. We are purely functional and technical.
- 4. What we are currently doing Building custom web applications / websites. Building connectors/ middleware applications. Optimizing and monitoring SEO performance on a technical level (not ga). Migrating a large custom build webshop. We are currently developing an in house application that will be make sense of SEO / SEA.
- 5. Why we chose CodeIgniter Avoiding the DreamWeaver effect.
- 7. General pros Lightweight Fast (!) Open Source Very good documentation Very good User Community Simple (KISS) MVC
- 8. What we think is important All we need is routing + database abstraction. Easily extendible/ adjustable. Simple Caching mechanism. Has few ‘conventions’. Has many ‘add-ons’. Easy to add external classes/ libraries
- 9. What we discovered Application framework, not a website framework. Forces a team to work in the same structure. CI is fast so you can write ‘sloppy’ code. CI plays nice (mostly) with Zend which is a good thing CodeIgniter is relaxed.
- 10. What we will talk about
- 11. Why not Expression Engine? Client server 2 Client server 1 Middleware application Client server N
- 12. Topics Making what the client needs Database Driven Development (DDD). How we design our projects Project file organization Source control management Extending Classes (Base Classes) DB routing Layout/ Templating ICF (Isset Content Framework) Logging Security (CLRF, AR) Making sense of SEO / SEM
- 13. The Client
- 14. Making the Client happy Force the client to participate. Three tier communication : developer(s), project manager, client(s) Make a ‘design’ document. Make sure both the client and the developer can understand the document. Use the project manager as mediator. Use feature list to determine if all requirements are made. Don’t use vague terminology. Prevent scope creep.
- 15. Database Driven Development Think about the data structure first. Generate template CRUD based on DB scheme
- 17. How we design our projects Making a test environment New project Migration Middleware / connector / webservice
- 18. Make a test environment Make sure that it matches the production environment. Replace all e-mail addresses and cell phone numbers with traceable test data. Don’t use offensive test data for fun, just don’t use it.
- 19. New Project Prerequisite : no database, no legacy system. Database Driven Development. Plan meeting(s) to write the design document with the client. Use agile approach (small iterations so the Client can see progress and test).
- 20. Migration Prerequisite: any project that has a database or legacy functionality. Should we migrate to CodeIgniter? What is the database scheme like? (DDD) What is the scope of the legacy functionality? How maintainable is the legacy code? Are their 3rd party components? What is the platform? Bottom line: start from scratch or migrate functionality over time.
- 21. Migration Path Make legacy application work next to CodeIgniter. Be aware of sessions (authentication). Be aware of absolute paths. Be aware of User Generated Content. Avoid changing existing code; move functionality into CodeIgniter.
- 22. Middleware / connector / webservice. Prerequisite; the application has to communicate with other applications. Demand (api) documentation up front. Log every transaction (request and response). Avoid connecting to third party databases directly. Clearly outline the responsibilities. (next slide)
- 23. Taking care of responsibilities
- 24. Project file organization Depends on scale and environment Learn about symlinks! Separate system from site root if possible Separate application from site root if possible Separate public (or assets) Use what works for you
- 25. Source control management Just do it. Git/ SVN/ Mercurial/ Bazar: Use what works for you We chose SVN because of general acceptance Use sensible commit messages
- 26. Extending Classes (base classes) Base Controllers will make your life easier For details: Jamie Rumbelow Use MY_Controller Use different base controllers according to the purpose of the (sub)application Alternatively use modules
- 27. MY_Controller
- 30. DB Routing / MY_Router How to match database records with controllers that do not exist. If a controller exist, the controller will be executed. Else it will do a db lookup. Make a table that has the external url eg http://mysite.tld/home with an internal controller e.g. pagecontroller/page/1 Make exceptions for things like news, blog items etc. in the router file For heavy traffic websites, make a pre-system cache hook.
- 34. Exceptions
- 35. Tackling the layout / template issue Default template Overwrite when needed with variations Little template partials like navigation, sidebars etc. Every partial can be associated with model(s) and/or view(s). INCMS uses db records to define the relation between pages and partials. Complete separation of logic en layout (mvc) Making a new layout for a site is easy.
- 37. Issues with ‘standard’ solutions 80% was easy (click ‘n go) 15% was hard (modify base code/ write workarounds or custom modules/plugins) 5% was not doable (restrictions by standard solution) Standard solutions that did work were either expensive or far too complex for the end user We hope that Ellis Labs will provide the ‘ultimate’ solution with Expression Engine 2.0
- 38. ICF (Isset Content Framework) NOT a CMS Generating editable content sections. Using default template most of the time, specific templates when necessary. Best of both worlds: making basic content pages easy, making complex pages doable. (using standard CI framework). 80% of a website is just content. 20% of a website is custom made. No restrictions! Think custom ajaxified ‘shiny’ contact forms clients love to torture developers with.
- 40. Logging Especially important when making middleware. Helps when playing ‘the blame game’. Log incoming, outgoing requests. Log email / sms / whatever. Logging is cheap but provides valuable debug information. Logging 404 can help determine routing issues, SEO issues, hacking attempts. Logging executed queries can help find bottlenecks. Logging to a DB makes analyzing data easy.
- 41. Example E-Mail Logging ‘Build’ the email to send Save it to a database Pass it to an email queue / cronjob Update the record when send Log if any errors occur
- 42. Example Email Database Scheme
- 44. Security Sanitize input, escape output. Be aware of XSS (CI provides some security). Be aware of Cross-Site Request Forgery (CSRF). Be aware of (MySQL) typecasting when using Active Record.
- 45. Example 1 - PyroCMS
- 46. Example 2 - SyntaxCMS
- 48. How to prevent CSRF Any destructive action should always be taken with a POST (update and delete). Cross Site POST is easy so gives no security. Use a token to verify that the send POST data is coming from the website. Michael Wales wrote extensively about it: http://www.michaelwales.com/codeigniter/protecting- against-csrf-exploit
- 53. Making sense of SEO / SEM efforts Keeping track of the position for a given landing page in combination with a search string Monitoring Google PageRank Measure cause and effect listing milestones in conversion / visitor timeline. Relate all search strings to conversions. Adding search strings to a campaign that are cheaper but also make a conversion Exclude search strings from a campaign that are expensive but never make a conversion.
- 54. You can (in a few months) Visit sedindex.com (next monday) Pre register Find more information We will get back to you in January 2010
- 55. Questions ? Thanks for listening. We hope you enjoyed it