recentpopularlog in

robertogreco : versioncontrol   5

Guidelines Behind Prose Diffs
"• The units of meaning is not the "line", but the word, sentence, paragraph, section.
• Editing a word/sentence/paragraph/section is different than moving it elsewhere.
• If a sentence or paragraph or section changed, you would want to show which specific parts of it changed, instead of highlighting the entire larger unit.
• It would likely be helpful to show the change in context, possibly as a before/after toggle.
• Markup would be very difficult to parse. (Open/close tags across sentences, etc.) But markdown would be all right.
• There are trivial changes, meaningful changes, and then meaningful changes that you want to call out.
• Adding line breaks don’t matter, unless it forms a new paragraph."
allentan  writing  editing  howwewrite  versioning  versioncontrol  2014 
august 2014 by robertogreco
Rendered Prose Diffs · GitHub
"Today we are making it easier to review and collaborate on prose documents. Commits and pull requests including prose files now feature source and rendered views."
via:kissane  github  versioncontrol  git  tools  writingtools  writing  onlinetoolkit 
february 2014 by robertogreco
DrupalCon Portland 2013: DESIGN OPS: A UX WORKFLOW FOR 2013 - YouTube
"Hey, the dev team gets all these cool visual analytics, code metrics, version control, revision tagging, configuration management, continuous integration ... and the UX design team just passes around Photoshop files?

Taking clues from DevOps and Lean UX, "DesignOps" advocates more detailed and durable terminology about the cycle of user research, design and production. DesignOps seeks to first reduce the number of design artifacts, to eliminate the pain of prolonged design decisions. DesignOps assumes that the remaining design artifacts aren't actionable until they are reasonably archived and linked in a coherent way that serves the entire development team.

This talk will introduce the idea of DesignOps with the assumption that the audience has experience with a basic user research cycle — iterative development with any kind of user feedback.

DesignOps is a general approach, intended to help with a broad array of questions from usability testing issues, documentation archiving, production-time stress, and general confusion on your team:

What are the general strategies for managing the UX design process?
How do you incorporate feedback without huge cost?
What happened to that usability test result from last year?
How much space goes between form elements?
Why does the design cycle make me want to drink bleach?
WTF why does our website look like THIS?
* Features turnkey full-stack (Vagrant ) installation of ubuntu with drupal 7 install profile utilizing both php and ruby development tools, with all examples configured for live css compilation"
chrisblow  contradictions  just  simply  must  2013  drupal  drupalcon  designops  fear  ux  terminology  design  audience  experience  shame  usability  usabilitytesting  work  stress  archiving  confusion  relationships  cv  canon  collaboration  howwework  workflow  versioncontrol  versioning  failure  iteration  flickr  tracker  creativecommons  googledrive  tags  tagging  labels  labeling  navigation  urls  spreadsheets  links  permissions  googledocs  timelines  basecamp  cameras  sketching  universal  universality  teamwork  principles  bullshitdetection  users  clients  onlinetoolkit  offtheshelf  tools  readymadetools  readymade  crapdetection  maps  mapping  userexperience  research  designresearch  ethnography  meetup  consulting  consultants  templates  stencils  bootstrap  patterns  patternlibraries  buzzwords  css  sass  databases  compass  webdev  documentation  sharing  backups  maintenance  immediacy  process  decisionmaking  basics  words  filingsystems  systems  writing  facilitation  expression  operations  exoskeletons  clarification  creativity  bots  shellscripts  notes  notetaking  notebo 
may 2013 by robertogreco
The Git Parable
"The following parable will take you on a journey through the creation of a Git-like system from the ground up. Understanding the concepts presented here will be the most valuable thing you can do to prepare yourself to harness the full power of Git. The concepts themselves are quite simple, but allow for an amazing wealth of functionality to spring into existence. Read this parable all the way through and you should have very little trouble mastering the various Git commands and wielding the awesome power that Git makes available to you."
tutorials  howto  tips  versioncontrol  tutorial  programming  git  via:tealtan 
february 2012 by robertogreco
Git Reference
"This is the Git reference site. This is meant to be a quick reference for learning and remembering the most important and commonly used Git commands. The commands are organized into sections of the type of operation you may be trying to do, and will present the common options and commands needed to accomplish these common tasks.

Each section will link to the next section, so it can be used as a tutorial. Every page will also link to more in-depth Git documentation such as the offical manual pages and relevant sections in the Pro Git book, so you can learn more about any of the commands. First, we'll start with thinking about source code management like Git does."
via:tealtan  tutorials  howto  cheatsheet  versioncontrol  development  programming  tutorial  documentation  reference  git 
february 2012 by robertogreco

Copy this bookmark:

to read