Theatre seem to be using Myriad Pro for things (bottom of posters). The logotype is Akkurat (SU has licence)

Myriad is a commercial font, Adobe TypeKit licence will be required to use on site ($50 USD/year) bit of a PITA.

I seem to remember SU has some licence for Akkurat, we should investigate this.

If there aren't any shows there should probably be some content on the home page...

Make a page, hidden from robots & with no navigation, which is designed for displaying on the screens in the foyer. Should have show information, and pretty pictures (maybe a smugmug slideshow of some description).

For show data we will use a collection of pages and mirror a subset of the fields used for history project pages (https://history.newtheatre.org.uk/docs/shows/).

What additional data would be nice to have for the "online programme"?

• Images
• Director/producer notes
• Cast notes
• Cast(/crew) headshots
• Sponsors

Advantage of using same data file as HP is easy migration from website to HP.

Having 8 shows for StuFF all saying '17th June' is not helpful!

Pushing the poster and title info into its own row, and the .card-body its own row would probably make better use of the page.

Display a link to a Bootstrap modal under 'Reserve tickets' displaying a table as per pricing.yml
Conditional relating to the season of the show
modal:
if in house
display in house and all
if fringe
display fringe and all
if stuff
display stuff
else
display please email foh@ for ticket pricing information

The SU website can handle iframes. Is it stupid levels of overkill to incorporate this into a Jekyll page for better formatting, consistent date and committee management, and better version control?

It is currently hard-coded twice to appear in a different position within the card depending on the device width. This is really awful and requires updating things twice for a single change.

Need to figure out a way to improve this.

They take a hecka long time to load

Current behaviour: Has a day heading with the single occurrence
Desired behaviour: Distribute the occurrences over the days

This feels non-trivial and particularly niche.

We're not allowed to break links between the current and the new site. All links should be kept the same or redirect to the new link.

• Build a list of links
• Don't break them

Write a description of the site for SEO copy, must be between 150 - 160 characters.

Use the external events link in the API

There should be a way to get to the gallery on the website, don't know where exactly though

Display the constitution on the website (the full text, not a link to a pdf)

iPads don't like the table of contents following, so change the breakpoint to make it less icky

Very low pri, http://humanstxt.org/, https://history.newtheatre.org.uk/humans.txt

Emma is going to creat one for Ritual from last year, will then replace on homepage and can it be added to the footer.

Gels site http://gels.newtheatre.org.uk could be rebuilt as a very minimal jekyll site in a separate repo built and run completely with GitHub pages (i.e. no travis, no staircase server)

Single file _data/gels.yml would look like:

- gel:
  code: L201
  color: #C3E1FB
  stock:
    - sheet: 3
    - cut: 17

&c

Site would be built, either a pure HTML output or same with JavaScript fun added in.

Could be extended for gobos.

A way/page for people to have a public NNT calendar which they can sync to their own

Add a google map link for us in the footer so people know where we are, also add directions to nearest car parks and where the car parks are.

User Groups

• NNT members, acting as punters
• NNT members, acting as members
• Prospective NNT members
• Non-members as punters
• Staff as punters
• Public as punters
• Alumni as alumni
• Alumni as punters

List non-exhaustive. Each one of these groups has specific needs and will want different information. This was partially the reason for the members site - separation of members and punters. Decision will have to be made where on the spectrum the site is 'pitched at'.

Returns a blank iframe
@davidtaylorhq - is this something you can look into?

Allow the option to have content before and/or after the ticket listing.

This should be by means of an include {% include ticket-listing.html %} which inserts a div with the appropriate id (mini-list or whats-on), so it can be included in between content sections, should that be desired.

The ticket JS should then work out if that div already exists: populate it if so, or add a new div at the end of the content section if not.

External, StuFF and In House are all the same colour. This should be improved; Fringe currently sticks out as an odd one out.

The following need making

• SVG of NNT Logo, white on black
• SVG of NNT Logo, black on white
• Big PNGs of above

1. Identify users, set any brand changes, research

• See #8 (user groups).
• Research those user groups (talk to them)
• Explore and identify any brand changes early.

2. Plan / Wireframe

Lo-fi design steps, using research gathered in 1

• Write site requirements
• Sitemap, hierarchy of information. Have only as many pages as needed.
• Paper based page wireframing (this seems an alright guide: http://sixrevisions.com/user-interface/website-wireframing/)

3. Design and build

We'll get to that later, do some more planning.

4. Launch

5. Tune

Site is built well so later changes are easy to so. Site lasts a long time!

/rant, I may add to this later, http://www.smashingmagazine.com/ has some great articles on this process

Display this; is already in the ticket API

Currently display as Fri 1-Fri 1 March. Fix that.

MailChimp list, the signup for it is here http://newtheatre.org.uk/about-us/mailing-list/ and it does automatically when you book tickets.

It's not been sent to since June 2015 and has the larget number of confirmed subscribers.

Decide what to do with this.

Pressing the SU icon in the footer, and then pressing back results in a blank icon. Seemingly iPad-only.
(Suggestion: iPad hasn't found the rollover image)

With the rebuild being a static site (probably) the current method of connecting www to ticketing won't work (is a server side thing). Ticketing site should output to JSON (rather than the current HTML), www site should load this content client side via an AJAX call.

newtheatre/nt-tickets#8

/production-resources must redirect
Also the show pack is missing

Make it look prettier, looks rather balls at the moment

Decide on what it should be and update all information

Add a link after h1s on pages with a ToC to go back to the top of the page

Add social media links to FB and Twitter in footer so can be access on all pages

Commit to a staging branch, this is built and published to dev.newtheatre or similar. Then merged into master when approved/checked nothing has broken. Thoughts?

• Set up travis
• Set debug var on site, switches robots.txt to deny all

Currently it is 3 clicks to find out what time a show is on, which is obviously not ideal.

Update and improve the documentation for lay-editors.

Empty page exists here. Didn't feel like converting the existing page into markdown right now.

@nhyty Can you have a read over and edit while transpiling into markdown?

Should have a placeholder image in static for when the image is not set

• Stick some images on smuggy
• Adapt https://github.com/robwierzbowski/jekyll-picture-tag to work for smugmug
• Use polyfill for universal support https://github.com/scottjehl/picturefill
• Document

Spec site for HTML picture element: http://responsiveimages.org/

Support:

• Add times
• Photos

I've stuck the committee listing in a data file.

Get headshots into an unlisted album on smuggy and get the image IDs into a headshot var in the data file.

Looks a bit pants on mobile

We need a 404 page, it needs to be useful, it can be funny. No penguins.

Will add a list f pages being rewritten/updated by committee, hopefully done by start of the new season.