[07:30] <davidcalle> morning dholbach, what's up? o/
[07:30] <dholbach> salut mon ami
[07:30] <dholbach> still working on the versioning bits
[07:30] <dholbach> and getting closer
[07:30] <davidcalle> <3
[07:31] <dholbach> I figured out the logic to use and added the "this is version X" bit already
[07:31] <dholbach> now I'll add the "here are links to other versions of the doc" bits
[07:31] <dholbach> then add it to the template
[07:35] <davidcalle> dholbach: I don't know if you remember but the first iteration had this in a box, top left of the content. I'm wondering if it shouldn't be moved directly as a small row above the content. Eg. a dropdown selector, with some js that takes you to the new location when the version is changed. *thinking out loud*
[07:36] <dholbach> I'm happy with whatever presentation works best :)
[07:36] <davidcalle> Yeah
[07:36] <dholbach> dropdown could work well, yes
[07:36] <dholbach> as long as it's obvious and clear
[07:57] <davidcalle> dholbach: pretty! -> https://developer.staging.ubuntu.com/admin/
[07:57] <davidcalle> dholbach: thanks for finding how to enable this ^
[07:59] <dholbach> much better
[09:06] <dholbach> davidcalle, I pushed the version extension bits to https://code.launchpad.net/~dholbach/developer-ubuntu-com/importer-versioning/+merge/294202 now, what's still missing is: a test or two and making use of the data in the template - both shouldn't be too hard
[09:06] <dholbach> but I'll be out now for lunch and an appointment
[09:06] <dholbach> just wanted to keep you posted on the progress :)
[12:16] <tsimonq2> is it just me or does https://insights.ubuntu.com/2016/05/11/another-ubuntu-hackathon-with-a-blend-of-convergence/ have broken CSS on the "BQ M10 Ubuntu Edition" link?
[12:16] <tsimonq2> and the rest of the links in the article too
[12:16] <tsimonq2> (except for the "Tuner app" link)
[12:17] <davidcalle> tsimonq2: like an orange arrow too big and hiding part of the word?
[12:18] <tsimonq2> davidcalle: yes
[12:18] <tsimonq2> like a wavy thing
[12:18] <davidcalle> tsimonq2: if that's the case, I've seen it in the past, but not anymore
[12:18] <davidcalle> tsimonq2: browser?
[12:18] <tsimonq2> Chromium 49.0.2623.108
[12:19] <tsimonq2> oh now it's fixed...?
[12:19] <tsimonq2> huh
[12:19] <tsimonq2> weird
[12:19] <davidcalle> tsimonq2: well, I've seen it on other articles
[12:19] <davidcalle> tsimonq2: so yeah, some css having a hard time loading, I'd guess
[12:19] <tsimonq2> davidcalle: I have to head off to school, thanks for your time :)
[12:20] <davidcalle> tsimonq2: enjoy! ;)
[12:43] <dholbach> davidcalle, can you help me find the gadget-snaps page in the pages list and help me move it back to snappy/start/gadget-snaps?
[12:43] <dholbach> I'm a bit confused
[12:43] <davidcalle> wat o_O
[12:44] <dholbach> it's apparently at /en/start/gadget-snaps/ right now
[12:44] <davidcalle> https://developer.ubuntu.com/en/snappy/start/gadget-snaps/
[12:44] <dholbach> but I can't find that path in the pages list
[12:45] <davidcalle> dholbach: I do
[12:45] <dholbach> maybe it's some unpublished changes?
[12:46] <davidcalle> https://developer.ubuntu.com/admin/cms/page/ IoT > Get started > Gadget snaps
[12:46] <dholbach> click on the view button
[12:46] <dholbach> and it'll take you to https://developer.ubuntu.com/en/start/gadget-snaps/?edit&language=en
[12:46] <dholbach> (I found it now too)
[12:47] <davidcalle> Oh, fun
[12:47]  * davidcalle tries something
[12:47] <dholbach> trying "revert to live"
[12:47] <dholbach> cool, that fixed it
[12:47] <dholbach> thanks for helping out
[12:49] <davidcalle> dholbach: lol, I published the changes at the same time
[12:50] <davidcalle> dholbach: I'm trying to put it back at the end of the subpages list, but it's a pain
[13:03]  * dholbach hugs davidcalle 
[13:03] <dholbach> we should bring back the docs days and clean up the CMS a bit
[13:03] <dholbach> there's a ton of useless articles or test entries
[13:06] <davidcalle> dholbach: worth a look, yeah, I've done some of it when the tree bug was fixed, but only on the top level, I haven't looked deeper
[13:06] <dholbach> some zen gardening for the entire team :-)
[13:10] <davidcalle> dholbach: idea: we kill all redirects pages and instead, on the 404 page, we use the failing path on the serach engine to look for matching results. eg. "You are trying to access foo, this page does not exist anymore or has been moved, here are pages with similar names: ..."
[13:12] <dholbach> that'd be wonderful
[15:39] <dholbach> davidcalle, I'm getting a bit closer, the logic to add the version extension is working, but it looks like it loses the data when publishing the page
[15:39] <dholbach> I'm trying to figure out http://docs.django-cms.org/en/latest/how_to/extending_page_title.html#handling-relations right now
[15:39] <davidcalle> dholbach: what do you mean "loses the data" ?
[15:40] <davidcalle> Oh, I see, page extension data
[15:40] <dholbach> davidcalle, so basically you have a page and decide you want to add the data, so you create a versionextension, set the values, add it to the page
[15:40] <dholbach> yep
[15:40] <dholbach> and during publishing (or somewhere else) it goes AWOL
[15:41] <dholbach> just wanted to give you an update :)
[15:41] <dholbach> once that's done, we can play around with: http://docs.django-cms.org/en/latest/how_to/extending_page_title.html#in-templates
[15:41] <davidcalle> Thanks <3
[15:42] <davidcalle> dholbach: yeah, that could be a new template RawHTMLVersioned or something
[15:43] <dholbach> let's figure that out tomorrow :)
[15:44] <davidcalle> +1
[16:02] <dholbach> all right... I give up for today
[16:02] <dholbach> see you all tomorrow :)