search

caprenter / bcb-website

A place to track issues about the bcb website
GNU General Public License v3.0
0 stars 1 forks source link

Project Pages #164

Open caprenter opened 3 years ago

caprenter commented 3 years ago

We create project pages on the website for times when we need to feature a theme across a period of time, e.g. Black History Month, Pride, etc etc.

This is a ticket to document that process.

Planning

The more time we have the better. It really helps if there is a shared plan that covers, before, during, and after the event. The plan needs to consider how the web, and social media will be incorporated into the work of the initiative.

The sooner this is shared with the web team the better.

Raw material

We will need: Branding Images Copy (website and social media) A broadcast schedule (dates and times) Audio (before and/or after) Copy about people involved, and content of shows, and the wider initiative Links to other sources of information

Process

The people organising the project are not generally the people putting the information out on the web. They need to establish a process to pass their material to the people publishing it. Clear communication lines need to be established - it's easier if there is a single person identified to do this.

The people publishing it will probably only have a few hours a week to do the work, and will establish that e.g. Monday afternoon is when they can do their work.

A google doc is a good way of sharing that information, creating task lists, and so on We will probably turn that into GitHub tasks

Staff/Volunteer resources

Generally there is a not a lot. @notshi has done the 'website work' for a while now.

caprenter commented 3 years ago

It might be better to move this to a google doc, but wanted to get started. We can of course move it, and use this issue to reference it. See what you can do @notshi

notshi commented 3 years ago

Thanks, @caprenter

A google doc is great for posterity and a rolling document but having this github issue as reference is also good for further discussions and context. Separating the 'website work' to here also helps the volunteer doing it focused on that side of things.

The BCB website gets updated Monday afternoon so any new information will be updated then. Please only refer to one section that applies to you.

Instructions for Event organisers

Here is an example project page for reference. Point 7. is optional and only suggested if the event has a small programme selection.

  1. Logo and photos for event Colours and fonts used, if possible and large photos / logos are great
  2. Event details Date / Time / Location(s) / Link(s) to website or social media
  3. Copy for event A paragraph for the main project page and a short description (10 - 15 words)
  4. Schedule of programmes Date / Time / Title / Description / Presenter(s) / Guest(s)
  5. Photos of Presenter(s) If photos are not supplied, we will use a social media profile photo where available
  6. Links to Presenter(s) BCB profile or social media profile
  7. Optional CC the volunteer when emailing finished audio tracks to BCB This is most helpful for small projects (<10 programmes) as there is no need for BCB staff to organise this

BCB staff provided content

The following includes content that BCB should provide for two different parts of the website. Section refers to a widget in the main sidebar.

Content for section Name of event Day and date of event Short description of event (10 - 15 words) Image of event (can be a logo or a photo)

Content for event page Name of event Day and date of event Location of event (if applicable) Description of event (introduction or a paragraph) Large image of event (can be a logo or a photo) Schedule of programmes Names of participants Names of shows Date and time of shows Description of shows Photos of shows (can be a zoom screenshot of participants or just the host / logo) Social media links of participants Audio of shows Links to participant profiles if they are a BCB member Links to programme on Listen Again

Website work for Volunteer

It really helps if there is a shared plan that covers, before, during, and after the event.

Majority of these steps are the same over the complete course of an event / project. Steps that are italicised include content from shared documents; ie. raw materials, from BCB.

Bear in mind that there is quite a number of things to do in the Before stage, namely making sure the project page is live and ready for the launch of the event so it would be a good sanity check if all content that is needed to be on the website is finalised at least ONE day before launch. Otherwise, the content will be updated in the next week.

Before Design a layout for the event/project page Design image headers, if needed Check for content Convert content into HTML and CSS Download and fix images / media Upload images / media to the website Include metadata and credits for images / media Put the content on the page Convert content into layout Check for bugs and typos Make sure all links, media and images are working Publish new project page to the website Add new page with provided copy as a section on the landing page of the website Remove or move older sections (projects > 1 years) Include new page in main Projects page Copy and save HTML of removed section Update mobile page with new section Update Github project issue (includes raising any issues) Update Github repo with new CSS

During Check Github for issues raised Check for content Check schedule and listen again for media Convert content into HTML and CSS Download and fix images / media Upload images / media to the website Upload media to archive.org Embed media link from archive.org Include metadata and credits for images / media Put the content on the page Convert content into layout Check for bugs and typos Make sure all links, media and images are working Update Github project issue (includes raising any issues) Update Github repo with new CSS

After Check Github for issues raised Check for content Check schedule and listen again for media Update any dates, timings from schedule if they are wrong Convert content into HTML and CSS Download and fix images / media Upload images / media to the website Upload media to archive.org Embed media link from archive.org Include metadata and credits for images / media Put the content on the page Convert content into layout Check for bugs and typos Make sure all links, media and images are working Update Github project issue (includes raising any issues) Update Github repo with new CSS