[T3CON13NA] TYPO3 Flow And Neos In Enterprise Applications
•
1 gefällt mir•1,958 views
Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Mehr von Christian Müller
Mehr von Christian Müller (10)
[T3CON13NA] TYPO3 Flow And Neos In Enterprise Applications
- 1. TYPO3 Neos in Enterprise Applications Donnerstag, 30. Mai 13
- 2. Donnerstag, 30. Mai 13
- 3. Our administration team knows a lot about database X, so we want to use that for our application Donnerstag, 30. Mai 13
- 5. Continuous Integration is very important to us Donnerstag, 30. Mai 13
- 6. Same for us So we created a solution Donnerstag, 30. Mai 13
- 7. Ride the Flow, deploy with Surf READY Donnerstag, 30. Mai 13
- 8. Cloud Ready Donnerstag, 30. Mai 13
- 9. Our developers already use another PHP library Donnerstag, 30. Mai 13
- 10. Chances are high that it uses composer Donnerstag, 30. Mai 13
- 11. We need to connect to a lot of external services Donnerstag, 30. Mai 13
- 15. We need sophisticated authentication and security options to protect our data Donnerstag, 30. Mai 13
- 16. Custom Single Sign On READY Donnerstag, 30. Mai 13
- 17. Custom Single Sign On Custom Authentication Methods READY Donnerstag, 30. Mai 13
- 18. Integrate into existing Infrastructure Donnerstag, 30. Mai 13
- 19. Audit Logging Integrate into existing Infrastructure READY Donnerstag, 30. Mai 13
- 20. We need a centralized login system Donnerstag, 30. Mai 13
- 21. Single Sign On Solution WIP Donnerstag, 30. Mai 13
- 22. Our application should have fast response times Donnerstag, 30. Mai 13
- 23. Multi Level Cache Donnerstag, 30. Mai 13
- 24. Multi Level Cache Use the caching infrastructure that suits your project READY Donnerstag, 30. Mai 13
- 25. We want to use a framework that sticks to common standards Donnerstag, 30. Mai 13
- 26. Members of PHP-FIG Donnerstag, 30. Mai 13
- 27. Members of PHP-FIG PSR-0 Donnerstag, 30. Mai 13
- 28. Members of PHP-FIG PSR-0 PSR-1 Donnerstag, 30. Mai 13
- 29. Members of PHP-FIG PSR-0 PSR-1 Composer Donnerstag, 30. Mai 13
- 30. Members of PHP-FIG PSR-0 PSR-1 Composer HTTP Spec support Donnerstag, 30. Mai 13
- 31. Donnerstag, 30. Mai 13
- 32. We want to deliver our assets through Content Delivery Networks Donnerstag, 30. Mai 13
- 33. WIP Donnerstag, 30. Mai 13
- 34. Our content should be synchronized between systems Donnerstag, 30. Mai 13
- 36. The content our application should manage has very specific formats Donnerstag, 30. Mai 13
- 37. Fully flexible content model Donnerstag, 30. Mai 13
- 38. Adjust the structure to your business Donnerstag, 30. Mai 13
- 39. Our marketing wants to keep full control over all content that is edited Donnerstag, 30. Mai 13
- 40. READY Editors never edit the live website Donnerstag, 30. Mai 13
- 41. VISION Publishing workflows can be implemented Donnerstag, 30. Mai 13
- 42. We want to access content from our website in other applications too Donnerstag, 30. Mai 13
- 43. TYPO3CR API allows custom data access READY Donnerstag, 30. Mai 13
- 44. VISION Donnerstag, 30. Mai 13
- 45. Our website should provide Google with semantic data Donnerstag, 30. Mai 13
- 46. Donnerstag, 30. Mai 13
- 47. READY We already provide RDFa exporting capabilities Donnerstag, 30. Mai 13
- 48. Neos supports editors in annotating information VISION Donnerstag, 30. Mai 13
- 49. Training our 200 editors in using a complex CMS backend is too expensive Donnerstag, 30. Mai 13
- 50. READY Donnerstag, 30. Mai 13
- 51. READY What You See Is What You Get For The First Time Donnerstag, 30. Mai 13
- 52. READY What You See Is What You Get For The First Time Reduce cost of training your editors Donnerstag, 30. Mai 13
- 53. Parts of our intranet application need to be integrated into our website Donnerstag, 30. Mai 13
- 55. We need a flexible rendering solution for our module based application Donnerstag, 30. Mai 13
- 57. Donnerstag, 30. Mai 13
- 59. @daskitsunet ‣ likes books, music, tea and more ‣ Flow and Neos Community Contact ‣ Freelance Trainer / Developer ‣ plays the piano ‣ christian.mueller@typo3.org Donnerstag, 30. Mai 13