[09:24] <cub> zequence: I was reading the old PR strategy and wonder if there is any automation involved when updating the web site:
[09:25] <cub> "Website & Social Sites: Post an article on the Ubuntu Studio Website. This post is published on facebook, twitter, identi.ca and the website at once."
[09:25] <cub> At once...is it automatic somehow or just a reminder to post it on all channels at once?
[11:21] <cub> The web site theme is not very responsive. And I just noticed that knome had changed the theme for Xubuntu. I think we should consider this in the coming overhaul of the web site.
[11:24] <cub> I think a move to a new theme by 15.10 would be quite possible with a major change in design and art for 16.04. The only feedback we have received on the web site (that I'm aware) of has been complaints so perhaps an update is due even earlier than the next LTS
[11:25] <cub> only thing is the process to actually upload to the server and to be able to quickly fix any post-errors that was not discovered beforehand
[11:37] <zequence> cub: There's no automation, so it's not exactly at once
[11:37] <zequence> There is a plugin, which I think is now installed that could let you do that though
[11:38] <zequence> Anyone who would like to do work on the web site theme, just give it a go.
[11:38] <zequence> People to talk to, for help and assistance: knome, madeinkobaia
[11:39] <zequence> madein can help with artwork
[11:54] <zequence> Also, there are blueprints for the website, which should be used to organize the work
[11:54] <zequence> But, don't think anyone has the time now
[11:57] <cub> I was thinking of me. As I'm doing a couple of wordpress sites at the moment my php skills are fresh. In a couple of months, who knows? ;)
[11:58] <cub> I think automatic posting on channels are to be avoided. Better to be able to tweak the posting for each target. but more on that in what I prepare for the PR strategy mail I'm writing
[11:59] <cub> I was thinking, unless we have strong attachement to the current web site design, we could tweak the Xubuntu one (like before) and be up and running in time for 15.10
[11:59] <cub> zequence: I assume you never heard back from the guy talking about doing art work for the web page?
[12:00] <cub> it was some time ago
[12:15] <zequence> No, he hasn't been heard of since
[12:16] <zequence> I think we should aim higher than copying Xubuntus theme, if possible
[12:17] <zequence> I have also been doin a bit of php lately. But, I'm not anywhere near having time for that yet, and don't know how long until I have
[12:18] <cub> Yes, another aim for 16.04 but some change for 15.10, was my thinking
[12:18] <zequence> Right now I'm working on listing packages for backporting. I tried a lot of ways to list packages with apt tools, but finally I found it easier to just build my own, downloading package lists from apt repositories directly
[12:19] <cub> to do our own theme from scratch requires more work and knowledge than I have
[12:19] <zequence> It would be good for it to be mobile friendly in either case
[12:30] <cub> yup, it feels a bit old to not have a mobile friendly web site in 2015
[12:31] <cub> going back to doing our own theme, it's not just to create it, it needs to be maintained as well. More efficient to use a common theme and do customizations to it in a child theme. And get all updates "for free"
[12:38] <zequence> If it works, I can easily see it being untouched for at least 2 years at a time
[12:39] <zequence> Though, wordpress may make it fail of course
[12:39] <zequence> (workdpress updates, I mean)
[12:39] <zequence> But, I wouldn't know about that
[12:41] <cub> there are security updates even for themes sometimes
[12:50] <zequence> Yes, and therefore I think it is of course best to keep things minimal, if doing it yourself
[12:50] <zequence> But, the design don't have to suffer though
[12:51] <zequence> I'm making a tool that I'm calling apt-search for now. It will be able to search from any debian type archive
[12:56] <zequence> Time to head home
[16:37] <cub> holstein, are you online?
[16:46] <cub> sent an email instead