Skip to content
Louis Pilfold edited this page Mar 13, 2017 · 1 revision

Goals

  1. Create a professional looking online presence for the Feast charity.
  2. Make Feast charity contact details easy to find online.

Assumptions

  1. The site does not need any interactive functionality (no login etc).
  2. The site does not need the content to be editable by a layperson.
  3. The site content only needs to be edited very rarely.

Assets

  1. No tech restrictions. Open source software ecosystem can be leveraged.
  2. Louis, providing mostly knowledge & guidance.
  3. Alice, providing ???
  4. Mike, providing ???-Contact with Web page owner Coding :DAwesome :)

Limitations

  1. There is no budget.
  2. This is a learning project for Mike.
  3. Hannah the stakeholder has low technical knowledge

Specification steps

Someone needs to communicate with the stakeholder (Hannah) to get these resolved:

  1. Get a list of required pages on the website. (home page, contact page, etc)
  2. Any essential copy for each page needs to be written (i.e. home page should say "Feast is ...etc")
  3. A visual language needs to be acquired. Does Feast have any existing branding? Do they have a logo?

Technical architecture

If the website content is not to change we can use a static site generator to build the website. This will dramatically simplify the project and reduce time to go live, remove most ongoing costs, and means we don't need to babysit servers.

If we do this it's basically a simple front end site. HTML, SCSS, maybe a tiny bit of Javascript.

Costs

About Β£6 per year, presuming assumptions are correct so we can use a Jekyll site

  1. Domain name: Β£6 per year? Depends on the TLD used. (we should also set Hannah up an email account using this domain). Let's buy from gandi. not godaddy.
  2. File hosting for the compiled site: Β£0, we shall use github pages
  3. CI server: Β£0, we can use the free tier of Travis CI or Circle CI.

The only real expense is developer time.

Clone this wiki locally