Progress on the Alfresco book

Several readers have asked how the book I’m writing on Alfresco development is coming along. First of all, thanks for asking. It has been quite a project. The first draft of the entire book is now complete. What’s happening now is that a group of technical reviewers from Alfresco, Optaros, and Packt, the book’s publisher, are going through the chapters and providing comments. So far, I’ve been able to turn those around quickly but I anticipate an increasing volume of feedback as we move into the later, more technical, chapters.

I’m pretty excited about how it is coming together. If you like the tone and scope of the Alfresco Developer Series of tutorials you’re going to like the book. The book is full of hands-on examples so it should be really good for people that are new to the Alfresco platform.

It would be great if we could publish by the time the North American Community Conference happens in Washington D.C. on October 9th, but to be honest, I’m not exactly sure what the schedule looks like from here on out. I’ll give another update as we get closer to publication.

12 comments

  1. ukdavo says:

    Thanks for the update. I keep checking at the Packt site to see if it’s available on pre-order.

    Will it cover 3.0 at all? Are you at liberty to publish the ToC?

    Regards

  2. jpotts says:

    Yes, I will cover 3.0 in several ways:

    – All examples work in both 2.2 Enterprise and 3.0 Community.
    – With the exception of the “Customizing the Web Client” chapter, every chapter is applicable to 3.0. There is an entire chapter on web scripts, for example. All of the core repository stuff–the content model, actions, advanced workflow–remains unchanged in 3.0, for the most part.
    – The new SURF framework is covered at a high-level in the Appendix. I will revise the section with additional detail as the framework gels but I think there is enough in there now to get people pointed in the right direction. It’s all web scripts at the core–what’s new in 3.0 is the page and template definition piece that is used to assemble pages from web script-based components.

    Of course the ToC is subject to change but right now it looks like this:

    The Alfresco Platform
    Building, Deploying, and Troubleshooting
    Working with Content
    Handling Content Automatically
    Customizing the Web Client User Interface
    Web Scripts
    Advanced Workflow
    Web Content Management
    Security & Integration
    Building a custom UI: DoCASU
    Appendix

    Thanks for the interest and for reading the blog.

    Jeff

  3. Brandon Hobson says:

    Well, the storyline sounds a little vague, there’s little conflict, and no mention of a protagonist and antagonist. Other than that, it might make a good movie.

  4. JM.Pascal says:

    It’s always a pleasure to read your blog, your tutorial and I’m sure it will be a big pleasure to read your book!

    The ToC seems really complete.

    But one question : Does your example use Java API, PHP API, Javascript API… ? All Alfresco API ?

    Thanks a lot for you work.

    Regards,

  5. jpotts says:

    @Brandon,

    I’ll make you a deal on the option and you can be the screenwriter. I’m thinking it could be a boy meets girl, boy loses girl, boy implements content-as-a-service, girl realizes that all she ever wanted was a universal REST API she could call from her front end web app kind of thing.

    The protagonist should be played as an open-minded, often humorous, Wilco-loving geek who has a thing for unsweetened iced tea.

    Jeff

  6. jpotts says:

    @JM,

    Thanks! Yes, the examples mostly cover Java and JavaScript. There is a lot of Foundation API code in the book because that’s what you use in actions as well as Java-based web script controllers. The JavaScript API is covered most heavily in the chapter on web scripts.

    There are a couple of PHP and Java Web Services API examples with the most extensive ones being the same that were included in the Content Types tutorial.

    I have some short examples in the Appendix that show how to perform the same task using each API. So, for example, how to create an object, how to perform a search, how to set permissions, how to start a workflow, etc., so that people can get an idea of how the Java, JavaScript, and Web Services APIs differ.

    Jeff

  7. mabayona says:

    The combination Advanced Workflow and Javascript/REST would be a most welcome subject since it seems that current wiki and 3.0 feture list misses it.

    For instance, the creation of a site to monitor and control advanced workflows would be a very valuable sample.

    If you need proofreading, do no hesitate contact me.

  8. mabayona says:

    what about a section on using little bit of groovy instead of java?

    Alfresco can be extended to use other languages and the forge includes a project to use a groovy processor.

    I think this would be a good addition.

  9. Heimo Laukkanen says:

    Sounds really cool.

    I wish Packt would have similar early access versions as some other publishers do, as this is definitely something that I would like to get my hands on sooner than later .-D

  10. Renjit Clement says:

    I,am new to Alfresco and have been going through your articles about content modelling and custom actions.It was well explained and was easy to implement.I will keep looking this site for the release of the book. But one question, ‘Will it be of help for a beginner like me ?’ Thank you.

  11. jpotts says:

    @Renjit,

    Yes, it will help beginners. It is aimed at people new to the platform who have installed and played around with Alfresco but are ready to take it to the next level.

    Jeff

Comments are closed.