References and Jargon

These links and terms help with understanding enchilada's general approach:

Jargon

General

• Base: The default, resting position or lowest hierarchical element.
• Resting: The initial, default/inert state.
• Parent: A collection of things.
• Child: Things that are used to make up a parent.

Building

1. Base: The basic, "core" aspects of the project. Used to set defaults and fallbacks.
2. Element: Elements are the smallest pieces used to construct the larger parts of the interface. Typically assigned to HTML tags (ex: a video play button).
3. Component: Components are collections of Elements used to perform a single action (ex: a video player bar).
4. Object: Objects are collections of multiple Components used to perform a task (ex: a video player).
5. Layout: Layout is anything used to position the larger areas of the site (ex: the wrapper for the video player area).

Deploying

1. build: The first of three steps, used to get the site's different aspects up and running.
2. test: The second of three steps, used to optimize and audit what has been built, to see if it will work when made live.
3. deploy: The third of three steps, used to conduct any final optimizations and push the site live.

References

General

• The Front-End Checklist
• Web Developer Checklist
• Writing a Great README

Copywriting

• Ask yourself this when crafting content:
  • What?
  • With what?
  • Why?
  • Where?
  • How?
  • When?
  • How often?
  • For whom?
  • What next?
• Inverted Pyramid: Writing for Comprehension
• 7 guidelines for writing accessible microcopy
• Here's the CIA's "Phoenix Checklist" for thinking about problems
• 18F Content Guide
• 50 questions to ask while developing user and technical documentation
• Three Requirements of Good Microcopy
• A simple approach to improving form design
• Creating a Copywriting Style Guide: A better way to create content
• Crafting a Design Persona
• Designing inclusively
• Design with Difficult Data
• Effective UI Texts: Words to Avoid in Writing
• Hofstede’s cultural dimensions
• Introduction to Disability Terminology
• Is this my interface or yours? A piece about perspective
• Making a case for letter case
• My 6 Point Microcopy Checklist for Non-UX Writers
• UX Writing: The case for user-centric language
• Weak Words Kill Experiences
• Web copy techniques that alienate users, and why not to use them
• What is readability and why should content editors care about it?
• Writing Accessible Content
• A Thorough Guide to Website Copywriting

CSS/Sass

• BEMIT: Taking the BEM Naming Convention a Step Further
• Edit SCSS directly from your browser? Yes, you can do that!
• Enduring CSS: writing style sheets for rapidly changing, long-lived projects: Project Organisation
• How Our CSS Framework Helps Enforce Accessibility
• Mixins Better for Performance
• The ten commandments of sane style sheets
• Scaling CSS Components with BEM, REMs, & EMs
• How we’re using Component Based Design

Server

• Common .htaccess Redirects