Development docs home.

To do

Outstanding work- development

As at 07/11/2022

  1. Needs museum favicon - do later in dev cycle. Difference is currently useful
  2. Add underline class or similar to Wesley Knowles link on Local History >> Research Group card
  3. Make images in *.md files into easy to edit component
  4. Subscribe to Newsletter code
  5. Make changes to current site to allow existing shop site to link in sensibly - effectively New header and footer matching new site with existing Wordpress shop in body of page ????
  6. Redo e-commerce shop in ? (Shopify?) and accept increase costs. Build protype for testing and allow Tech group to decide. ????
  7. Confirm Microsoft Clarity meets needs or investigate Hotjar as alternative
  8. GDPR cookie confirmation - needed?
  9. Improve Other Things To Do page
  10. Does page specific SEO meta data need to be added to each page? Investigate.
  11. Agree “who can change or add what”. Different technical ability needed to alter Layout (header/footer/menus) than change a FAQ. Must avoid random “add this” stuff, otherwise over time bloat and redundancy will creep in. One option would be to allow ‘end users’ to draft Mardown pages but require Tech Team to take the page, vet it and add to site. Tech team currently RNC + BP
  12. Once decided new site will replace current site need detailed plan to move from current ISP, domain managers to ???
  13. Change procedures for source changes to enforce branching and merging so changes can be better managed. Currently simple pull/push from Master branch - rethink this to make sure really simple for content maintainers
  14. add a “Comment on this site” so Museum members/general public can report faults an raise suggestions for content
  15. Move everything from being in rcollins@redmug.co.uk accounts (Cloudflare, Git Hub etc) to being under nantwichmuseum.co.uk
  16. Change news component to be driven by news-data.json type file
  17. Change whats-on-exhibitions page to be driven by exhibitions.json type file
  18. Change buildings page to be driven by buildings.json type file
  19. Change whats-on-walks schedule to be driven by data.json file
  20. Change whats-on-talks schedule to be driven by data.json file
  21. Add finish-date to data.json object properties
  22. Check all products have delivery-charge-group set
  23. Do not show walks, talks, exhibitions one past finish date
  24. Review (for size & performance reasons) all property names (e.g. stop storing full url, move all otions to single string etc)
  25. Sort out format for created and edited Move to UNIX time?
  26. Add edit mode to pages generated by *.json and provide end user suitable simple editor for adding, amending and deleting the data
  27. Add support for draft:true|false
  28. Search page to support - Match out of order. Allow search words in any order. A needle of ‘town nant’ and ‘nant town’ would both return the same results

Outstanding work - content

  1. Improve photos
    1. Better school group photo
    2. Better access photo
    3. The English Civil War Re-enacted booklet cover proportions are wrong (too tall)

Add pages beneath Local History

  1. Nantwich Salt
  2. The Great Fire
  3. English Civil War - Battle of Nantwich
  4. Shoes & Clothing
  5. Nantwich Fairs
  6. Making Farmhouse Cheshire Cheese
  7. Nantwich Buildings (and approx 15 sub pages/shop links)
  8. Famous Nantwich People (and approx 12 sub page/shop links)
  9. Nantwich Apothecaries

Add pages beneath Community

  1. Membership
  2. Research Group
  3. Guest Exhibitions

Other content thoughts

  1. Redo the Blue Timeline page and make interactive
  2. Redo the Nantwich Shoe Factory Trail *.pdf (19MB!)

Documentation needed

Aim to be able to take tech savvy volunteer that’s never seen the site to make edits and additions to content and then deploy to live site.

  1. Document set up so other people can clone the repository and contribute to content. Initial work done. Needs more detail based on Bill’s experience
  2. Guides to edit page content
    1. Distinguish between _.md pages and _.astro pages
    2. Editing existing markdown page
    3. Editing landing page ‘news’ and links
    4. Editing *.astro page (e.g. What’s on) This will be a frequent change page adding new Talks, Exhibitions and Walks.
  3. How to deploy changes to live site
  4. How search works