Loading


Please wait...

Reconsiderations


Before the release of Birth, I had been updating this website to align with the brand redesign and add content relating to the new release. After using the current framework of the website, I realised it wasn't as inefficient as I previously thought. I appreciated my future-proofing of the website's structure a lot more.

For this reason, I feel the need for a new website from scratch is less needed as of now. In future, when I add and produce more content, and want to add more features, the need for a new website will let the project resume. Until then, the new website is paused for development indefinitely.

This doesn't mean a new website will never come, it will just not come any time particularly soon.



Why Make a New Version of the Website?


When I first made this website, it started off very simple. As it progressed, I wanted to add other features and elements to improve it. When I implemented these features, I did it in a way that wasn't fully professional or robust. This meant that the result was very fragile and couldn't adapt to other types of content.


Because of this, although the current website works, it doesn't work perfectly. There are performance issues and it becomes increasingly harder to implement new features.


So, I have decided to create a new version of the website from scratch. I'm building this version from the very foundations, to create the most robust and adaptable version I can. This will make the website perform better, look better, and will allow me to make quick and easy changes whenever I need.


I also aim to make the website more accessible to those who use screen-readers, those who are colourblind, blind, deaf, or don't have access to a keyboard or a mouse.


What are My Goals?


My goals for the new version of the website are:

  • Create a more robust framework
  • Create a more adaptable framework
  • Make the site look better (styling)
  • Make the site scale better on all screens
  • Make the site scale better when zooming in browser
  • Add more accessibility for the following:
    • Deaf
    • Varying levels of blind
    • Colorblind
    • Those with screen-readers
    • Those without a keyboard
    •         or:

    • Those without a mouse

How will I achieve them?


My plans to achieve these goals are:

  • Build a framework using as little dependencies as possible
  • Create a standard structure for the storage of information and content relating to the website
  • Create a framework that can read this structure
  • Create a framework that allows any variation of this structure
  • Allow the use of custom non-standard code within the structure
  • Create a default layout that is adaptable to the screen size, resolution and aspect ratio
  • Create styling rules that adapt to the current browser zoom level to keep a clean and clear layout
  • Create a default colour scheme with a minimum contrast following accessibility requirements
  • Create multiple colour schemes that also follow minimum contrast requirements
  • Create accessible colour schemes such as high-contrast and colourblind-friendly schemes
  • Create a quick and easy-access menu to navigate through the site using mouse-only or keyboard-only
  • Add content within background code that allows screen-readers to read and navigate the site easily
  • Add both visual and audible prompts and alerts relating to events on the page
  • Create an accessible mode with larger buttons, text and images
  • Create a clear and large navigation menu in accessibility mode

  • And, for mobile users:

  • Create a better-laid-out mobile version of the site
  • Add colour schemes above to the mobile version
  • Add touchscreen events to the website
  • (Possibly in future) add gestures to make the website easier to use on mobile
  • Make accessibility mode very large, clear and easy to use for any screen size (especially smaller screens)

Timeframe


Clearly, this is a lot to implement - especially from scratch. So the timeframe for the release of this new version is currently unknown; it could be any time between 6 months to a year or more. I will work to the best of my ability to build the new version as quickly as possible. In future, I will release a better timeframe estimate.


Once the foundations are laid down and the basic parts of the website have been built, I will allow users of the site to help beta-test the new site. Essentially, there will be a switch in the corner of the page, which will allow navigation to the beta version of the new site, where you can test out features and give feedback and bug reports to help speed-up development of the website.


Until then, I will be posting updates below, to give an idea of where I am in development. I will also post announcements on the home page and here when anything major happens, such as the beta release or full release of the website.


While the beta site is open, you will still be able to access the old site. Once beta testing is closed, the beta site will be taken down for a period of time while final changes are made and the full site is ready for release. Then, there will be a scheduled downtime of the site - meaning it will be unaccessible - while the new site is switched over to the new version and checks are complete.



Finally, I hope you are just as excited as I am for the new site! It will perform better, look better and be better.


Updates
Development Paused

Posted on the 28th of April 2022 at 12:53


Nested Dynamic Header Complete

Posted on the 6th of April 2022 at 20:47


A dynamic header has been completed, allowing pages to be displayed in the header and accessed easily.
A nesting design has also been added, allowing sub-pages to be linked in the header as well.

Base Complete

Posted on the 30th of January 2022 at 19:36


The initial file structure has been built! Pages across the website will use a set of base files defining the core page framework, style and functionality.
This will help keep consistency between all pages to ensure a positive user experience.

Offline Page Base Complete

Posted on the 24th of January 2022 at 16:11


An offline page has been built which, when you first connect to the website, is saved to your computer's storage. When you are offline, this page will be shown instead of the full-content website. This will help with user experience and interface consistency.

In future, more parts of the website may be cached to be available offline, but the focus of development has now shifted to other, more urgent areas of the website.

Development started!

Posted on the 25th of October 2021 at 0:00


Development on the new version of the website has been started!