<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
<div apple-content-edited="true" class="">Jay, </div>
<div apple-content-edited="true" class=""><br class="">
</div>
<div apple-content-edited="true" class="">This is a great start.</div>
<div apple-content-edited="true" class=""><br class="">
</div>
<div apple-content-edited="true" class=""><b class="">Monthly web pub meetups</b></div>
<div apple-content-edited="true" class="">An important first step would be for WebPub to go back to having monthly meetings. The lack of communication among yourselves has really hurt. And it prevents newcomers to MIT from finding out about WebPub in the first
place. The meetings don’t have to be organized around a speaker. People should just make short 5-10 minute presentations to show anything new that they’re working on, and also to ask questions.
</div>
<div apple-content-edited="true" class=""><br class="">
</div>
<div apple-content-edited="true" class=""><b class="">Finishing Drupal Cloud</b></div>
<div apple-content-edited="true" class="">Yesterday I posted two screencasts to walk people through building sites on Drupal Cloud. They’re not great but the nerd in me always finds it interesting to see how other people work.</div>
<div apple-content-edited="true" class=""><br class="">
</div>
<div apple-content-edited="true" class="">
<div apple-content-edited="true" class=""><b class="">Lesson 1 </b></div>
<div apple-content-edited="true" class="">Creating a new content type (projects) and views. </div>
<div apple-content-edited="true" class=""><a href="https://youtu.be/Fu_MjGCNsJA" class="">https://youtu.be/Fu_MjGCNsJA</a></div>
<div apple-content-edited="true" class=""><br class="">
</div>
</div>
<div apple-content-edited="true" class=""><b class="">Lesson 2</b></div>
<div apple-content-edited="true" class="">Continuation of Lesson 1, showing some CSS theming with css injector module, and also Block management.</div>
<div apple-content-edited="true" class=""><a href="https://www.youtube.com/watch?v=dXwJrlKp9Rw" class="">https://www.youtube.com/watch?v=dXwJrlKp9Rw</a></div>
<div apple-content-edited="true" class=""><br class="">
</div>
<div apple-content-edited="true" class="">I planned to walk through the full site creation process, but now I’ve decided to make a short screencast to show what’s missing from Drupal Cloud. It would be so easy for IS&T to spend two weeks and finish this platform.
Nothing would represent a security risk. And small fixes would make the difference between a 2009 platform that of limited use and a 2015 platform that’s robust and user-friendly.</div>
<div apple-content-edited="true" class=""><br class="">
</div>
<div apple-content-edited="true" class="">Ed</div>
<br class="">
<br class="">
<div>
<blockquote type="cite" class="">
<div class="">On Sep 22, 2015, at 4:55 PM, Jay Sitter <<a href="mailto:jsitter@mit.edu" class="">jsitter@mit.edu</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
Hi everyone,
<div class=""><br class="">
</div>
<div class="">It was great to see so many people interested in the state of web development at MIT coming out to talk. As Ed said, communication is key.</div>
<div class=""><br class="">
</div>
<div class="">Also to repeat Ed, it seems like we were all coming from many different places, but I think there were some themes that we can extract from our discussion.</div>
<div class=""><br class="">
</div>
<div class="">Before I go into more detail, though, I’d love to just get a general feel for how interested the people on this list are in getting together to think about how our development processes could be improved. A quick reply indicating your interest
level would be appreciated!</div>
<div class=""><br class="">
</div>
<div class="">My main takeaways from the discussion:</div>
<div class=""><br class="">
</div>
<div class="">1) <b class="">The help/Q&A community around Drupal Cloud and development in general could stand to be improved.</b> Can this be addressed technologically (using something other than the Drupal Cloud forum), or is it a matter of spreading awareness
of existing technologies and engendering a culture of reaching out for help and helping others?</div>
<div class=""><br class="">
</div>
<div class="">2) <b class="">A means for knowledge- and code-sharing could help everyone and prevent duplicated effort.</b> For instance, one person who was in attendance is using Joomla for secure document sharing, since that isn’t provided by Drupal Cloud,
and another person pointed out that this *can* be done in Drupal (though not in Drupal Cloud), relying on content_access and other module(s). More open and frequent communication among developers and webmasters in different departments could allow for serendipitous
meetings like this, potentially leading to better, longer-term solutions to development challenges.</div>
<div class=""><br class="">
</div>
<div class="">3)<b class=""> Drupal Cloud could use some better, more robust theming options.</b> People seemed to like the idea of dragging content as presented in Ed’s Open Atrium demo; there’s a general agreement that the default themes aren’t as attractive
as they could be, though they get the job done; and responsive design is definitely something that people would like to see.</div>
<div class=""><br class="">
</div>
<div class="">4) <b class="">How can we help prevent "code rot"?</b></div>
<div class=""><br class="">
</div>
<div class="">There’s more to discuss, of course, but I think this is a good start.</div>
<div class=""><br class="">
</div>
<div class="">More generally, is this kind of communication/collaboration something people on this list are interested in? Meeting on central campus every month is maybe something we could think about, where we could share our current projects, new things we’ve
learned, ask for help with problems, etc.</div>
<div class=""><br class="">
</div>
<div class="">Hope to hear from you!</div>
<div class=""><br class="">
</div>
<div class="">Best,</div>
<div class="">Jay</div>
<div class="">
<div class=""><br class="">
--<br class="">
Jay Sitter<br class="">
Web Designer & Developer<br class="">
Massachusetts Institute of Technology<br class="">
Office of Communications, Resource Development<br class="">
(617) 715-5170<br class="">
600 Memorial Drive, W98-352B<br class="">
Cambridge, MA 02139-4822<br class="">
</div>
<br class="">
On Sep 21, 2015, at 10:30 AM, Edmund Carlevale <<a href="mailto:ecarl@MIT.EDU" class="">ecarl@MIT.EDU</a>> wrote:<br class="">
<br class="">
<blockquote type="cite" class="">Hello,<br class="">
<br class="">
I’ll be making my presentation later today, a more straightforward demo than I had originally intended but still hopefully useful. I just posted a blog post that outlines the talk. <a href="http://drupalgroup.mit.edu/" class="">http://drupalgroup.mit.edu/</a>. I
hope you’ll be able to be there.<br class="">
<br class="">
Regards,<br class="">
<br class="">
Ed<br class="">
<br class="">
Blog<br class="">
<br class="">
"Re-Imagining Web Development @ MIT" - presentation outline<br class="">
Posted by Ed Carlevale on September 21, 2015 [edit]<br class="">
I originally intended today's presentation as a review of where MIT is now in terms of web development, followed by a presentation of an alternative approach. But I can say really simply now where MIT is, leaving me to spend the bulk of my presentation showing
something better.<br class="">
<br class="">
Basically, MIT has two options for bringing in new websites: single-site single-client development, or Drupal Cloud. <br class="">
<br class="">
The single-site approach is unmaintainable. The sites are built by an outside developer and handed over to their MIT client, usually a program's communication manager, to manage. The developer oftens works on a contract basis to maintain the site and make needed
changes. And the communication's manager maintains the site. The essential flaw in this process is that new MIT sites reinvent the wheel over and over again, building the functionality (people, projects, publications, news events, blogs, media galleries),
that should long ago have been packaged and made available to the MIT community in some sort of centralized process.<br class="">
<br class="">
Drupal Cloud I discuss in the blog post from yesterday. <br class="">
<br class="">
So what I'll be presenting today is my approach, which basically presents the concept of an MIT distribution, then demonstrates the power and functionality that it is possible to build on top of that basis.<br class="">
<br class="">
1. Panopoly. I start by introducing Pantheon's Panopoly distribution, because it is becoming the standard base for most other distributions by virtue of its brilliant use of Panels and Panelizer.<br class="">
<br class="">
2. Then I demo the Open Academy distribution, originally built by Chapter 3 for UC Berkeley (I believe), which is built on top of Panopoly and adds standard (ahem, Drupal Cloud) academic features like Publications, People, Events, and News.<br class="">
<br class="">
3. And then I come to the primary thing I want to present, which is the Open Atrium distribution. Open Atrium builds on top of Panopoly, so it's basic structure should be very familiar. But it adds the most brilliant feature set and interface I've seen on any
website. The distribution has been adopted by the United Nations as their primary platform, and that makes perfect sense to me.<br class="">
<br class="">
Over the past year I've used Atrium as the basis of my own sites, and have added the features that I think belong on an MIT distribution, the most important of which is a documentation intranet. The fundamental flaw with nearly all web development is that there
is no documentation, neither for users nor developers. Sites are built and handed off, but as soon as anyone from the original team leaves, the site becomes unmaintainable. Virtually every stand-alone site I’ve seen at MIT has gone through this life-cycle
spiral. <br class="">
<br class="">
The other key problem with our current approach is that so much effort is being wasted in recreating the wheel, in building functionality that should take an hour at most, not the entire development budget. So virtually every site at MIT is happy to post events,
news items, and people, and call it a day. Some are more attractive than others, but their functionality and development is a direct version of their html base. Revolutions have happened in how sites are built, in what they do. But MIT has simply updated html
to php. There is so much that could be happening with academic websites, especially in large research centers, and none of it is happening beyond decent looking sites that show events, people, and news items, and call it a day.<br class="">
<br class="">
So the presentation today is about demo-ing a more efficient structure. It's not the manifesto I had in mind when I originally thought of this presentation. But I think it represents a better way forward.<br class="">
<br class="">
_______________________________________________<br class="">
WebPub mailing list<br class="">
<a href="mailto:WebPub@mit.edu" class="">WebPub@mit.edu</a><br class="">
<a href="https://mailman.mit.edu/mailman/listinfo/webpub" class="">https://mailman.mit.edu/mailman/listinfo/webpub</a><br class="">
</blockquote>
<br class="">
</div>
</div>
_______________________________________________<br class="">
WebPub mailing list<br class="">
<a href="mailto:WebPub@mit.edu" class="">WebPub@mit.edu</a><br class="">
https://mailman.mit.edu/mailman/listinfo/webpub<br class="">
</div>
</blockquote>
</div>
<br class="">
</body>
</html>