Difference between revisions of "User:Hawk"
From Documentation
| Line 44: | Line 44: | ||
# Code snippet should demonstrate the correct usage of API. | # Code snippet should demonstrate the correct usage of API. | ||
# Summary at the end. | # Summary at the end. | ||
| − | # Check header, footer, TOC, subsections | + | # Check header, footer, TOC, subsections, references |
# Check overall article's layout. | # Check overall article's layout. | ||
Revision as of 09:20, 20 July 2012
Under Editing
User:Hawk/Tutorial Extension-UnitTest
User:Hawk/Wire Event Listeners
Ready for Publish
Already published
- Small_Talks/2011/December/MVVM_in_ZK6:in_Contrast_to_MVC
- Small Talks/2012/January/Ajax GSP with ZK
- Small Talks/2012/January/Enrich Grails Server Pages (GSPs) with ZK
- Small_Talks/2012/January/MVVM_Extension:_Access_UI_Components_Inside_ViewModel
- Small_Talks/2012/February/MVVM_in_ZK6:_Form_Binding
- Small_Talks/2012/February/MVVM_in_ZK6:_Work_with_Spring
- ZK Developer's Reference/MVVM (whole chapter)
- Small Talks/2012/April/The Dawn of ZK Application Test Suite:Mimic Library
- Small Talks/2012/April/Shining ZATS Mimic
- ZATS Essentials
- ZK Getting Started/Learn ZK in 10 Minutes
Writing Check List
- Describe the purpose or context at the begining.
- To start from a basic, simple concept or fewer concepts.
- 1 paragraph presents 1 idea.
- Picture is better than words.
- Picture should be elegant.
- Picture should present just enough information.
- Give the overall concept first, then the detail of implementation.
- Code snippet should keep as short as possible.
- Code snippet should demonstrate only key concept and remove irrelevant.
- Code snippet should demonstrate the correct usage of API.
- Summary at the end.
- Check header, footer, TOC, subsections, references
- Check overall article's layout.
Template
Note: note message
Warning: warning message
Font design
http://3.7designs.co/blog/2008/06/10-examples-of-beautiful-css-typography-and-how-they-did-it/