Hi luvit! I'm writing to introduce myself and talk about some of the work we're planning to improve Luvit's Web presence for Luvit 2.0. My name is Ken and I'm a UI engineer at Rackspace, although I'm doing this mainly on a volunteer basis. Tim has brought me on to produce a clean and unified design across the Luvit home page, the upcoming blog and any future web properties that should carry the branding of the project.
If you're interested and want to provide feedback early in the process, there's a thread at luvit/blog.luvit.io#1 <https://github.com/luvit/blog.luvit.io/issues/1> with further discussion and some screenshots of the new prototype. Everyone is welcome to participate! Just expect some shuffling around of the website code in the coming weeks as we're still figuring out the workflow. One particular concern I want to raise is whether we should have online API documentation on the luvit.io site. From a developer experience as well as a general usability perspective, this is something that I very much want. We've discussed generating API docs in the past - see luvit/luvit#16 <https://github.com/luvit/luvit/issues/16> and luvit/luvit#258 <https://github.com/luvit/luvit/pull/258>. Is anyone willing to pick up where Rob left off? Thanks and looking forward to working with you all! - Ken -- You received this message because you are subscribed to the Google Groups "luvit" 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/d/optout.
