-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Venues #27
Comments
Then photos and blurby bits on these venues. I would include: Mooch, Den and Live, Studio 7, any halls that have nice photos (potentially one big and one small), Great Hall, the Downs, and maybe some external venues like the Atrium, Colwick and Donington. |
Have a look at this, it's a start to see what people think (as you will notice it's all the same venue and picture, that's because I'm really really lazy) Find it under /about/venues |
I'm not overly keen on using datafiles for this. I would recommend creating each venue as it's own page as it creates much greater flexibility. I only used the data directory for committee as it I deliberately wanted the flat uniform look that it gives you. |
It's quite nice to see each venue on one page and then also a detail view on a separate page I thought. Is it possible to do that with a load of single pages without a data file? |
Yeah fully, you want a custom archetype and then a new layout for the archetype/summary.html. The committee used to be done like this and I changed to the data file option in 638eaa3 due to the simplicity of what I wanted to show (and to prevent having a dedicated page for each person). |
Ok awesome, I'll give it a go |
Venues has been updated to use archetypes, now someone needs to write some lovely words about each venue. |
This looks great. Thanks, Harry. I'm also wondering if you had a plan for the dotty button on each venue's menu card? |
Hit the handy dandy back button in your browser? I could add some breadcrumbs if you wanted, and that was left over from when it was a pop up card, should probably fix that. Also this was meant to be a client only page as a kind of portfolio that's why it has no links to the rest of the site |
@pickleshb Back button works fine, until someone sends you a link to a specific venue in an email or similar |
I agree with David. I also think the venue name should be on the venue page, and higher and larger than the event name. |
So do I, and feel free to play around with it if you want |
Slideshow: Would like progress bars and next/prev buttons. |
Nope. 😛 |
Less is more |
@davidtaylorhq I don't think materialize has the option for arrows in it's sliders, the dots are enough for me |
I agree, I think the dots are enough (not that I've actually pulled & built it because I'm lazy) |
Interestingly, your screenshot has dots in the picture and blue. Mine are below the picture and green. |
@samozzy I blame firefox (at a guess) |
It is you need to compile your sass man On Thursday, March 31, 2016, Sam Osborne [email protected] wrote:
|
@pickleshb But I didn't even edit any CSS... |
@samozzy Yes but I did, and the main css file isn't in version control, so you'll need to compile it and everything will look pretty |
@pickleshb Ahhh this makes sense. |
Made it so that all venues have there own photos so there's no more placeholders any more. Words are still required in some places. Also added the Albert Hall. This also ties to #55 |
One thing that I think would be cool to do is build a public catalog of venues we have worked in, both for a "this is what we can do" thing, and for bigger spaces such as Studio 7, a "this is what can be done in this specific space" type thing.
The idea came about after speaking with Alex Daniel where he wasn't happy for Conferences to use his photos for publicising S7, although whoever does it would need to check with him, TEC branded pages would be a much better thing for both TEC and Alex (as we can control credits easier). Sending people a link to an unlisted page that just showcases the space a little would be a very handy thing to have.
The text was updated successfully, but these errors were encountered: