Editing MDN with VIM
UPDATED: New screenshot with html filetype! Thanks Screwtape for the tip in the comments!
Yes, it's possible! If you're like me you want to spend as much time in vim as possible. While I appreciate CKEditor on MDN, I personally prefer to edit text in vim, and I think many developers might agree. And since MDN should include content written by developers for developers, here's a way to edit your favorite web developer docs (that would be MDN), using vim. (In my case, MacVim)
- Install the It's All Text Firefox addon.
- Go to the IAT preferences
- set your editor to vim (MacVim.app in my case)
- set your hotkey. (alt+command+e in my case, now that I'm used to Firefox Dev Tools "Inspect" and "Console" keyboard hotkeys)
- Go to the MDN article you want to edit. (Apps/Getting Started in my case)
- Click Edit (duh)
- Click Source
- Type your hotkey!
- Drink beer and edit away!*
- :wq
* groovecoder is not responsible for whatever Sheppy might do to you if you actually edit MDN while intoxicated.
Note: For MacVim you may need to set the "After last window closes: Quit MacVim" preference so it puts you right back to Firefox when you :wq.
MDN 2.3
Released February 28th. We are moving to weekly releases on MDN so these posts are hard to keep up. I will probably start combining releases. And I'm just going to link to the MDN 2.3 bug list instead of linking individual bugs.
- Wiki
migrate tags from MindTouch to Kuma
(Re-)enable tag display and editing
remove extra redirect for locales
verify code samples work post-migration - BrowserID
fix login infinite redirect bug - HTML5 & Apps MWC pages
Paul and Craig cranked out the new HTML5 and Apps landing pages in time for MWC
While Paul was with us he created ScrumBugs! I love it! I always appreciated the way we did Agile/Scrum/XP/whatever at SourceForge.net, and I've been forcing pushing for Mozilla WebDev to adopt some of the same practices. And I just really like pretty graphs! Can you tell?! :)
MDN 2.4 & 2.4.5
We're calling our first weekly sprints 2.4 and 2.4.5, but I think next we'll just move to 2.5, 2.6, ... until we all meet up in New York for MDNYC. At that point we'll probably abandon bugzilla milestones and just use the whiteboard to organize bugs into sprints based on release dates. Until then, here's what we're working on for 2.4 and 2.4.5.
- BrowserID
Hopefully killing all the remaining BrowserID bugs so we can concentrate on wiki - Wiki
Les is rocking lots of KumaScript work
Migrate file attachments
Wiki code syntax highlighting
Refine UI for tag editing
Activate continuous migration on staging server for MDN doc community
MDN 2.2
- BrowserID
bug 721171 to draw Sign in buttons with progressive enhancement - should hopefully fix our search results snippets too! ><
bug 719945 to link to browserid on the demo submit page - MindTouch wiki migration
prepare for localized page migration (bug 717380)
scripting architecture (bug 715253) - More
I'm excited about kumascript - lmorchard's prototype for implementing server-side scripting in kuma to replace DekiScript. I'm glad we're using JavaScript. I was a little surprised that MediaWiki chose Lua for their new scripting language (is it ironic that DekiWiki and its Lua-based DekiScript has roots close to MediaWiki and now MediaWiki is going to Lua-based scripting too?). JavaScript just makes sense for us - a community of web developers writing web developer docs.
MDN 2.2.5
- An HTML5 landing page (bug 712387) that summarizes all of Mozilla's HTML5 content and initiatives
- Redesign Apps landing page in time for MWC (bug 726166, bug 726167, and bug 725757)
MDN 2.3
- wiki migration
migrate tags (bug 710722 and bug 722567)
migrate code samples (bug 725359)
migrate file attachments (bug 725358)
migrate localized docs (bug 710724) - More
MDN 2.1
We're doing better at keeping away from big new features while we try to work on the wiki migration, so there's no big item in today's release notes.
- More BrowserID cleanup
bug 715723 was really annoying - Sign in was broken from wiki pages
bug 715811 should help users who've forgotten which email address they use on MDN - MindTouch wiki migration
James did a thorough job on bug 710734 to expand the markup allowed in kuma
Les did some more great working discovering all MindTouch namespace pages (bug 710753) and script template usage (bug 714804)
Craig fixed up a bunch of CSS issues we've discovered as we migrate real content (bug 710737) - More
MDN 2.2
- More MindTouch wiki migration work
Les is drawing up a proposed architecture for KumaScript to replace DekiScript (bug 715253), made the bugs to migrate tags (bug 721143), and wrote code to migrate redirects (bug 710721)
I shirked the 'locale' bug 717380 onto James :)
I'm working with IT to add the migration script to a cron job on our staging server (bug 721072) so the doc community can see the progress so far - An HTML5 landing page (bug 712387) that summarizes all of Mozilla's HTML5 content and initiatives
- More
MDN 2.0
Wow, that's how much of a non-event a "2.0" product release is these days. I forgot to publish this when we pushed 2.0. Might as well publish before our 2.1 push today. :)
- BrowserID cleanup (bugs 715708 and 714915)
- MindTouch migration script - authors (bug 710714) and revision history (bug 710715)
- More
MDN 2.1
- Set up 'master' and 'next' branches and corresponding stage servers on allizom.org (bug 710747)
- Wiki content migration & work
- Architecture for migrating MindTouch DekiScript templates into Django JavaScript templates (bug 715253)
Small sprint this time, but Les made some great progress on our wiki migration. I'm forcing myself to do a migration script bug this sprint so I learn enough of that code to follow his architecture and contribute what I can.
