Blog

Luis Majano

October 15, 2008

Spread the word


Share your thoughts

This is an announcement that an internationalization translation project is way on its way for the ColdBox documentation. If you go to the official wiki site, you will see two new languages: Japanese and Spanish. The entire docs are being translated now to these languages and should be done by version 2.6 release if possible. Also, a new group has been created for ColdBox Translators. So if you are interested in helping out in the translation process, become an official translator or just help out, please email us at info@coldboxframework.com. Right now we have one Japanase translator and one Spanish translator. So please contribute if you have time.

Add Your Comment

(2)

Nov 26, 2009 11:41:55 UTC

by Marcelo Santana

Estimado Luis, estoy migrando desde Fusebox y me gustaría acceder a la documentación en español, así como tratar de contribuir a su traducción, pero al parecer ahora no es posible visualizarla. Es posible reestablecer el enlace o que me envíes lo que exista de documentación en español?

Gracias.

Feb 18, 2010 23:24:50 UTC

by Luis Majano

Marcelo, disculpa la tardanza en eso. Mandame un email a lmajano@ortussolutions.com para que charlemos sobre como pasar documentacion en español

Recent Entries

Introducing BoxLang AI Explorer: A Local Catalog for Every AI Pattern

Introducing BoxLang AI Explorer: A Local Catalog for Every AI Pattern

Learning a new AI API usually means jumping between scattered documentation pages, guessing at imports, and copy-pasting code that may or may not still work. We wanted something better for BoxLang AI, so we built the BoxLang AI Explorer: a local, browser-based catalog of runnable BoxLang AI examples, organized by category and difficulty, each with guidance, source code, and sample output.

Luis Majano
Luis Majano
August 14, 2026
Community Spotlight: BoxLang Express Brings Node-Style HTTP to the JVM

Community Spotlight: BoxLang Express Brings Node-Style HTTP to the JVM

If you've spent years in Spring Boot, Micronaut, or Jakarta EE, "web framework" usually means a servlet container, an embedded Tomcat or Netty, a build step, and a fat jar before anything answers a request. What if you could skip all of that and still be on the JVM?

Luis Majano
Luis Majano
August 12, 2026