Closed Bug 800573 Opened 13 years ago Closed 12 years ago

Create 'L20n by example'

Categories

(L20n :: Evangelism, defect, P2)

x86_64
Linux
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: stas, Assigned: stas)

References

Details

I'm inspired by https://gobyexample.com/. Read more about it here: http://mmcgrana.github.com/2012/10/introducing-go-by-example.html It would be great to have a repository of examples like this for L20n. We actually have something similar: https://wiki.mozilla.org/L20n/Toolbox but it's outdated and would need to be rewritten in part. Looking at https://gobyexample.com/arrays it's actually quite similar to our docs (generated by docco): http://l20n.github.com/l20n.js/lib/l20n.html
Blocks: l20n-beta
Assignee: nobody → jbeatty
Priority: -- → P2
Target Milestone: --- → 1.0
Yeah, I really really like what Bret Victor does to code. It's outstanding. Here's a different, not as good, but pretty okay, example: http://code.hazzens.com/d3tut/lesson_1.html On the other hand, let's not let our docs look like this: http://code.google.com/p/crack-language/
Language for syntax highlighting: closure
Target Milestone: 1.0 → 1.0 beta
Blocks: 852287
No longer blocks: l20n-beta
Assigning to myself. I'll try to write 5 more chapters this week. I'm working in the following etherpad: https://l20n.etherpad.mozilla.org/byexample
Assignee: jbeatty → stas
Target Milestone: 1.0 beta → 1.0
Matjaž added the remaining chapter, but the appendices remain to be written.
Appendices are now also written: https://github.com/l20n/l20n.org/commit/8babe5c326cdee38d11ab5c57c70893a1d2a1921 I think we should join the following two chapters, they are solving the same problem: http://l20n.org/learn/context-data-and-localization-logic/ http://l20n.org/learn/genders/ We should just remove the second one and name the first one Genders as suggested in bug 916353.
Now that bug 916353 is fixed, I think we can fix this one too?
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.