concept model http://default/ en Views 2 module concept model http://default/pieces/views-2-module-concept-model <div data-history-node-id="245" class="h-entry node node--type-piece node--view-mode-fulltext ds-1col clearfix"> <div class="clearfix text-formatted field field--name-field-sub-title field--type-text field--label-above"> <div class="field__label">Sub title</div> <div class="field__item"><p>My first concept model</p> </div> </div> <div class="field field--name-field-image field--type-image field--label-hidden field__item">/sites/default/files/styles/large/public/Views-sitemap.png?itok=L_1FwD9U</div> <div class="clearfix text-formatted field field--name-body field--type-text-with-summary field--label-hidden field__item"><p>The redesign for version 2 of the essential Drupal module Views was one of my first impactful contributions. Much of the functionality is (still) over my head but somewhere in 2008, after many long conversations in IRC I arrived at a diagram that clarified a lot. I didn’t know of the term concept model then, hence the “sitemap” title.</p> <p>In simple terms, you use Views to create lists of things. It lets you define what kind of thing to list, where to present it, how to format the list and how to format each item in the list. </p> <p>What this concept model achieved was mapping the system objects to these simple what, where, how questions. It helped many people understand much better what this new version would be able to do.</p> <p>I love to do this kind of <a href="http://default/pieces/scenario-using-content-workspaces">visual</a> <a href="http://default/pieces/content-workflow-initiative-what-workspace">clarification</a>.</p> </div> <div class="field field--name-taxonomy-vocabulary-1 field--type-entity-reference field--label-inline"> <div class="field__label">Tags</div> <div class="field__items"> <div class="field__item"><a href="http://default/tag/drupal" hreflang="en">Drupal</a></div> <div class="field__item"><a href="http://default/tag/drupalgive" hreflang="en">drupalgive</a></div> <div class="field__item"><a href="http://default/tag/concept-model" hreflang="en">concept model</a></div> </div> </div> <span class="hidden"><a href="https://brid.gy/publish/twitter"></a></span> <div class="node__links"> <ul class="links inline"><li class="comment-forbidden"></li></ul> </div> </div> Thu, 11 Aug 2016 21:38:38 +0000 Roy 245 at http://default A scenario for using content workspaces http://default/pieces/scenario-using-content-workspaces <div data-history-node-id="242" class="h-entry node node--type-piece node--view-mode-fulltext ds-1col clearfix"> <div class="clearfix text-formatted field field--name-field-sub-title field--type-text field--label-above"> <div class="field__label">Sub title</div> <div class="field__item"><p>Preparing the launch of a new campain.</p> </div> </div> <div class="field field--name-field-image field--type-image field--label-hidden field__item">/sites/default/files/styles/large/public/workspace%20scenario.gif?itok=633ivOvk</div> <div class="clearfix text-formatted field field--name-body field--type-text-with-summary field--label-hidden field__item"><p>An example of how to use content workspaces to <a href="http://yoroy.com/pieces/content-workflow-initiative-what-workspace">prepare multiple content items that you want to publish</a>.</p> <p>Say you want to launch a new campaign (product launch, a sales promotion, a fundraising drive). This means creating new content, updating existing items to link to that new content and maybe archiving some elements of a previous campaign as well. With content workspaces you can create, review, test all these changes on a copy of the live site. When everything is in place and ready to go live, these changes can be published to the live site and you've launched your campaign.</p> <ol> <li>Setup: create a workspace</li> <li>Create (add, change, archive, delete) content as needed</li> <li>Review your work. While working inside your workspace, the content on the live site will likely have changed. Blog posts were added, products were updated, typos got fixed, etc. So, you can import (“pull”) these changes into your workspace. Maybe these changes interfere with your own work. Now is the time to fix those conflicts.</li> <li>Happy with your work you set the workspace to “needs review”. This sends a notification to your team lead or editor who reviews your work as well. If it needs works till, she can set it back to “needs work” which means you’re back at step 2 to make the necessary changes.</li> <li>All is well and ready to be published. First a final “pull” of any changes from the live site to make sure there are no conflicts, then the actual publishing of all the new items and changes you prepared in the workspace get “pushed” to the live site.</li> </ol> </div> <div class="field field--name-taxonomy-vocabulary-1 field--type-entity-reference field--label-inline"> <div class="field__label">Tags</div> <div class="field__items"> <div class="field__item"><a href="http://default/tag/drupal" hreflang="en">Drupal</a></div> <div class="field__item"><a href="http://default/tag/ux" hreflang="en">ux</a></div> <div class="field__item"><a href="http://default/tag/drawing" hreflang="en">drawing</a></div> <div class="field__item"><a href="http://default/tag/workflow-initiative" hreflang="en">workflow initiative</a></div> <div class="field__item"><a href="http://default/tag/concept-model" hreflang="en">concept model</a></div> </div> </div> <span class="hidden"><a href="https://brid.gy/publish/twitter"></a></span> <div class="node__links"> <ul class="links inline"><li class="comment-forbidden"></li></ul> </div> </div> Mon, 08 Aug 2016 21:44:25 +0000 Roy 242 at http://default Content workflow initiative: what is a workspace? http://default/pieces/content-workflow-initiative-what-workspace <div data-history-node-id="241" class="h-entry node node--type-piece node--view-mode-fulltext ds-1col clearfix"> <div class="clearfix text-formatted field field--name-field-sub-title field--type-text field--label-above"> <div class="field__label">Sub title</div> <div class="field__item"><p>Similar to git branching but for content</p> </div> </div> <div class="field field--name-field-image field--type-image field--label-hidden field__item">/sites/default/files/styles/large/public/workspace%20definition.gif?itok=MsIvJkaN</div> <div class="clearfix text-formatted field field--name-body field--type-text-with-summary field--label-hidden field__item"><p>A workspace is a copy <em>of</em> the live site, that exists <em>in parallel to</em> the live site.</p> <p>Use a workspace when you want to prepare multiple new content items, that you want to go live at the same time, in a controlled manner.</p> </div> <div class="field field--name-taxonomy-vocabulary-1 field--type-entity-reference field--label-inline"> <div class="field__label">Tags</div> <div class="field__items"> <div class="field__item"><a href="http://default/tag/drupal" hreflang="en">Drupal</a></div> <div class="field__item"><a href="http://default/tag/workflow-initiative" hreflang="en">workflow initiative</a></div> <div class="field__item"><a href="http://default/tag/concept-model" hreflang="en">concept model</a></div> <div class="field__item"><a href="http://default/tag/drawing" hreflang="en">drawing</a></div> </div> </div> <span class="hidden"><a href="https://brid.gy/publish/twitter"></a></span> <div class="node__links"> <ul class="links inline"><li class="comment-forbidden"></li></ul> </div> </div> Sun, 07 Aug 2016 21:47:53 +0000 Roy 241 at http://default