Home

Table of Contents

• The Weekly Review
• Release Notes
• .htaccess
• Pomodoros

The Weekly Review

Any tool you use will take effort to keep clean and current, so that you can trust your action choices. The Weekly Review is what ties this whole thing together, ensuring that you have actions for all the active parts of your projects on a consistent basis, so you can trust that what you are choosing from your next action lists is current.

The Weekly Review steps include:

Get Clear

Capture Loose Papers and Materials

Gather all accumulated business cards, receipts, and miscellaneous paper-based materials into your in-tray.

Get "IN" to Zero

Clarify completely all outstanding paper materials, journal and meeting notes, voicemails, dictation, and emails.

Empty Your Head

Put in writing and clarify any uncaptured new projects, action items, waiting for's, someday/maybe's, etc.

Get Current

Review Next Actions Lists

Mark off completed actions. Review for reminders of further action steps to record.

Review Previous Calendar Data

Review past calendar in detail for remaining action items, reference data, etc., and transfer into the active system.

Review Upcoming Calendar

Review upcoming calendar events-long and short term. Capture actions triggered.

Review Waiting For List

Record appropriate actions for any needed follow-up. Check off received ones.

Review Project (and Larger Outcome) Lists

• Evaluate status of projects, goals, and outcomes, one by one, ensuring at least one current action item on each.
• Browse through project plans, support material, and any other work-in-progress material to trigger new actions, completions, waiting for's, etc.

Review Any Relevant Checklists

Use as a trigger for any new actions.

Get Creative

Review Someday/Maybe List of interest.

Review for any projects which may now have become active, and transfer to "Projects". Delete items no longer of interest.

Be Creative & Courageous

Any new, wonderful, hare-brained, creative, thought-provoking, risk-taking ideas to add into your system???

Release Notes

v0.5.0

🚀 Features

• DocsSearch: add hide-color-mode prop (90e73a4), closes #113

🐛 Bug Fixes

• CodeGroup: add missing attrs bind (3dd36cd)

👋 New Contributors

• [@vicknice] made their first contribution in #131

.htaccess

<FilesMatch ".(eot|ttf|otf|woff)">
    Header set Access-Control-Allow-Origin "*"
</FilesMatch>

Pomodoros

Features

• https://github.com/arielsalminen/vue-design-system/wiki
• Set of interconnected patterns & practices for you and your team
• Well thought-out terminology, naming conventions, and hierarchy
• Automated overview of how your design system progresses over time
• Global design tokens in YAML format that you can use inside any component
• Automatic generation of living, user editable documentation
• Easily export and use your Design System as an NPM dependency in another projects
• Create a token, an element, or a pattern, and it’s immediately available across all components
• Pre-configured setup for auto-formatting code on both save and before commit
• Live Reloading, Autoprefixing, SCSS, and helper functions + simple and sane defaults for SVG and Webfont usage out-of-the-box
• Documentation and the app logic are separated, so you can have public docs while the app itself stays private
• And more…

Sections

• Getting Started: How to install and run Vue Design System.
• Terminology: Introduction to the system concepts and its hierarchy.
• Naming of Things: Naming is hard, so it’s good to have clear guidelines.
• Directory Structure: What goes where and why.
• Working with the System: Concrete examples on how to work with Tokens, Elements, Patterns and Templates.
• Editing Living Documentation: How to customize the living system documentation
• Spacing: A framework for creating a predictable and harmonious spacing
• Component Status: Clear labels that reflect the state of completion
• Component QA: How to review new components and keep the quality high
• Contributing: A set of guidelines for contributing to the system
• Code of Conduct: By participating you agree to abide by its terms
• Frequently Asked Questions: How to use icons, how to use font-face, etc.
• Changelog: See releases page for the full changelog

Getting Started

• https://github.com/arielsalminen/vue-design-system/wiki/getting-started

Terminology

• https://github.com/arielsalminen/vue-design-system/wiki/terminology

Naming of Things

• https://github.com/arielsalminen/vue-design-system/wiki/naming-of-Things

Directory Structure

• https://github.com/arielsalminen/vue-design-system/wiki/directory-structure

Working with the System

• https://github.com/arielsalminen/vue-design-system/wiki/working-with-the-system

Editing Living Documentation

• https://github.com/arielsalminen/vue-design-system/wiki/editing-living-documentation

Spacing

• https://github.com/arielsalminen/vue-design-system/wiki/spacing

Component Status

• https://github.com/arielsalminen/vue-design-system/wiki/Component-Status

Component QA

• https://github.com/arielsalminen/vue-design-system/wiki/Component-QA

Contributing

• https://github.com/arielsalminen/vue-design-system/blob/master/CONTRIBUTING.md

Code of Conduct

• https://github.com/arielsalminen/vue-design-system/blob/master/CODE_OF_CONDUCT.md

Frequently Asked Questions

• https://github.com/arielsalminen/vue-design-system/wiki/frequently-asked-questions-(FAQ)

Changelog

• https://github.com/arielsalminen/vue-design-system/releases

Jira

pnpm add @nuxt/ui