Hi.. +1 This is nice idea!. Yeah we can go with developer only template switcher by placing new template files separately. I think making things responsive is not hard for many of existing template components. I just tested it by using chrome's DOM editor see https://i.imgur.com/3zOxXVQ.png making width responsive + media queries would work for many (I mean without changing the structure of existing DOM)
Some components may have additional effort for making responsive eg - Discussion comments (We might need to add show comments button to see replies for smaller screens) I will also like contribute this responsive support work Cheers! On Wed, Oct 24, 2018 at 1:16 AM Dave Brondsema <d...@brondsema.net> wrote: > On 10/23/18 1:55 PM, Ingo Hornberger wrote: > > Hi Dave! > > > > If I understood your ideas right, I'd love to see that. I putted quite a > > lot of work into the styles to get my allura instance mobile ready. And > the > > result is by far not clean. > > > > Yea, we also made a few attempts at just changing CSS styles to support > mobile > and it just didn't work very well. > > > But the biggest advantage would be, that I can change every page. So I > can > > make more easily make adaptations to the view of specific tools. > > > > But wouldn't it also mean that you have to maintain two versions of Jinja > > templates for quite a while? > > Yes, that is correct. So during the process any fixes or updates would > have to > apply to both versions. Hopefully the whole process doesn't take too long. > > There's also a possibility that once we get some pages completely done and > working well enough that we could use the new responsive versions for those > pages and the original versions for other pages. And then the pages that > are > enabled with the new responsive version would not need to keep their old > templates around. However, we are a long way from that, and there may be > challenges with CSS rules that apply to all pages. > > > > > Regards, > > Ingo > > > > > > > > > > Am 23.10.2018 17:38 schrieb "Dave Brondsema" <d...@brondsema.net>: > > > > Right now allura pages are all fixed width, but it would be good to have > > them > > all be responsive web pages, particularly down to small mobile screen > sizes. > > We've had a ticket at > https://forge-allura.apache.org/p/allura/tickets/8093/ > > for > > this for a while, but it is a challenging task to figure out how to > update > > all > > the pages. > > > > Kenton & I have brainstormed on this a bit, and now have an idea for how > > this > > could go. Here's what we were thinking. A new *theme* in Allura only > can > > control some HTML on the "chrome" (header/footer) of the page and CSS > > changes. > > This isn't enough - every page has its own HTML markup that will need to > > change, > > and some pages have inline CSS rules too. > > > > So, the first step would be to make a template override directory where > we > > can > > start placing new html files. This would be disabled by default. I'll > be > > merging a proof-of-concept of this shortly. > > > > Then we'll need a new theme to provide the header/footer/etc in a > responsive > > structure. And then its a long process of updating all the individual > pages > > html/css and shared components/functionality to the responsive setup. > > > > For actually making it responsive, Kenton & I would propose we use the > > Foundation framework https://foundation.zurb.com/sites It has served us > > well > > already on SourceForge and we can share some patterns and code I think. > > Foundation also uses SASS instead of plain CSS. This gives a more > powerful > > tool > > for authoring CSS, although it adds a css compile step. I think its > worth > > it > > though, especially since it should make it easier to customize Allura > > theming > > (change a font everywhere, or change a color palette everywhere, etc). > > > > Any feedback is welcome, and we hope this is an idea that sounds good to > > others, > > and that others can help with it before long too. > > > > We'll post more updates as our initial work gets under way, and as soon > as > > there's a good foundation in place for others to jump in and help too. > > (We're > > still doing a lot of testing / proof-of-concept work to see how it'll go) > > > > > > > > > > -- > Dave Brondsema : d...@brondsema.net > http://www.brondsema.net : personal > http://www.splike.com : programming > <>< > -- Regards, *Shalitha Suranga*
