Comments on The Language of Modular Design

16 Reader Comments

Back to the Article
  1. The Organize chapter of Modular Web Design (2009) discusses techniques for naming and creating taxonomies of compponents and their variations, and the Discover chapter also addresses a useful workshop to decompose and prioritize a system’s parts. http://www.amazon.com/Modular-Web-Design-Components-Documentation/dp/0321601351

    Copy & paste the code below to embed this comment.
  2. I guess that this desire for modular design started with UNIX, back in the 70’s.
    Since then, it’s been a race towards the perfect modules, although we never have them. But it’s better to have a bad module, than no module (although there might be situations where you are better of starting from the beginning).

    Copy & paste the code below to embed this comment.
  3. As a blogger, I love modular design. It makes non-design people to easily edit minor stuff without having to edit much. Thanks for this informative post.

    Copy & paste the code below to embed this comment.
  4. Well it actually seems pretty nice used in template pages! Anyway, I really loved the part where you talk about the interaction between devs and designers since there is always a problem of efficiency! Both parts should know how things work & are built before any creation.

    Copy & paste the code below to embed this comment.
  5. Once you name something you constrain its value.  The value should come from its function, and given a name only if it has value.

    Copy & paste the code below to embed this comment.
  6. Awesome article! Kinda branching off of the idea of modular UI components, I’d love if you would take a look at a project I’ve been working on. I’m trying to create a framework by which many different applications(which are not necessarily written in the same language) can present UI components in a simple and consistent way. Here’s the repo!

    Copy & paste the code below to embed this comment.
  7. Real excited about the future of modular design, especially with Web Components.

    Copy & paste the code below to embed this comment.
  8. Having spent 99% of my development and design time in enterprise scale organizations - I suppose I sort of took this approach for granted. Generally, the first question I ask myself when a new component/interaction is requested : “Where does this interaction differ in needs and function from the components we have already established?”

    followed by “does it warrant it’s own variation? where does the inflexibility lie? how could this be marginally changed to still meet business goas while improving reuse?”

    I suppose the suggestion could be used for smaller shops : approach site components more like wordpress shortcodes, than a dreamweaver template.

    Copy & paste the code below to embed this comment.
  9. Excited to try some of these approaches, my only reservation as a designer is balancing the use of modules with a concept of the pages as a whole.

    You say “Until then—even after all of our experiments—we were still thinking in pages” To me this implies that a consideration for pages isn’t required, whereas I would argue that it is balancing this modular approach with an overall concept of how the modules knit together.

    Visual design is about balance, and hierarchy, which can only be considered when these modules come together, for example on a page.

     

    Copy & paste the code below to embed this comment.
  10. As a blogger, I love modular design.
    thanks for your Post

    Copy & paste the code below to embed this comment.
  11. Looks really interesting

    Copy & paste the code below to embed this comment.
  12. The saying that “naming things” is one of the hardest computer science problems rings very true, and this article states why so elegantly.  I’ve found with my clients that it’s almost like inception: once you name a module or page template, it’s so very difficult to reinvent it.

    Copy & paste the code below to embed this comment.
  13. I’m not sure that I agree with everythin, but great article !

    Copy & paste the code below to embed this comment.
  14. awesome atricle!! cheers!

    Copy & paste the code below to embed this comment.
  15. The basic idea underlying modular design is to organize a complex system (such as a large program, an electronic circuit, or a mechanical device) as a set of distinct components that can be developed independently and then plugged together. Although this may appear a simple idea, experience shows that the effectiveness of the technique depends critically on the manner in which systems are divided into components and the mechanisms used to plug components together. The following design principles are particularly relevant to parallel programming.  Your blog is helpful to improve the performance. I enjoyed reading your blog.

    http://www.cybnetics.com

    Copy & paste the code below to embed this comment.
  16. I love modular design. Most of the UIs I have created had modular layout. It makes easier to edit for me.

    Copy & paste the code below to embed this comment.
  17. Sorry, commenting is closed on this article.