Even though I don't really want to start a discussion about technologies, I agree with Justin that most of vim.org's content is static and doesn't need a server-side framework. FWIW, kernel.org is made with a static site generator.
The plugins section is obviously different and would need quite a bit of server-side code. It think this part is more sensitive in terms of security and spam-prevention. My question is how to move this forward? Is it at all realistic to get buy-in by the core developers outright or is it more sensible to build some form of proof of concept first to show how things could work? Leonard -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
