![]() Therefore i am guessing we are entering the stage of guiding the on how to structure his PR against: But it would diverge from current way of doing things. That is rather technical solution and we likely shouldn't expect to achieve that on its own? Having a drop down selector to basically switch between more HTML pages. If we want to preserve the current way of doing it. the translatable parts, will be simple files which will be straightforward to that is the part i was talking about in my previous answer. The page will be broken down to the point that the text copy, i.e. In the short term, though, after GSoC ends for me (August 14th) I can present a minimum viable product which will just consist of me converting AR795's homepage repo changes into a series of Django templates. In the long-term, it can also be the foundation for features like single sign-on. Plus, moving the homepage from a simple shared hosting to fully managed server will be nice. It would also let us tap into Django's translation system so we don't have to reinvent the wheel for a lot of features. ![]() This would have the benefit of enabling rich homepage links that don't link to the wiki but instead to a managed page, similar to WordPress, which will allow for high-quality redesigned pages like AR795's new "Home", but for "Overview", "Features", "Download", and so forth. That would be using Wagtail, a CMS for Django. To that end I'd like to restate what I think our long-term homepage goal should be. ![]() And Normand's point about translation support is also very important. I agree with triplus' idea to go with a single HTML page approach for now.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |