Skip to content

Workshops Layout #75

@lawrennd

Description

@lawrennd

@timothygebhard Love the work you've done tidying up the style etc. I've back-incorporated it into the old sites.

On that front, there's a bunch of websites that sit on this style/layout combination which I've been iterating across the years.

I took the opportunity recently to tidy up the 'inheritance structure' of that using the remote themes capability Jekyll now has.

The 'remote theme' is here: http://github.com/lawrennd/proceedings.git

I know, it's a bit of a mess ... it's merging multiple different websites in an effort to make them consistent ... including AISTATS, PMLR, DALI, Advances in data Science. My thought is that mess can be tidied up later, but for the moment it will start acting as a unifying force across these different outlets. I'm hoping to use this to get a better achive of a number of meetings at some point (or to enable someone else to do that).

I've had a look at your new workshops _layout, and can totally see where you're coming with it. But, it is effecting the underlying layout structure which messes with the consistency stuff I'm doing above. So I think we need to have a structured think about how we can get some of your nice ideas into the central layout without breaking the consistency with other sites.

There are a couple of minor things. E.g. I standardized on 'institute:' not 'affiliation:' for author lists ... I think I wavered between the two, but I don't think it's worth revisiting.

But then there are more major things. Like the philosophy bethind what's what. I agree that the multitrack/singletrack thing is a little confusing, but it would be good to think about how to move away from it without breaking compatability.

Also I get the move to _workshops instead of the abuse of _posts that I started with, but I would like to think a bit about if we're making such a move, how we can do so in a way that means we can maintain compatability.

I had a go at doing some of this on my own, but realised it was too complicated to merge the visions.

So I had the following suggestion of a way forward.

Would it make sense to revert to the old style as far as layouts go? And then iterate towards the new style collaboratively, attempting to maintain backwards compatability with the other sites?

FOr a compatiable site, we can use e.g. dali2019a as an example. Basic idea would be to ensure that for the new site layouts old sites also work just fine.

Sorry for the long issue!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions