Well done with this project! I am interested in contributing by converting this into a hybrid mobile app. However, I see the EDLIS is © Copyright June 2015, Ministry of Health & Child Care. Did you get the necessary permission to reproduce this in digital form?

Kind Regards

Describe the bug
In your chapters, all heading encapsulate an a tag. I think this is unnecessary as thats not how and why an tag is supposed to be used there.

The tag defines a hyperlink, which is used to link from one page to another. The most important attribute of the element is the href attribute, which indicates the link's destination.

In this project the multiple headings in the chapters are not links, and thus we have errors in our code due to the tag not having an href. If we are to clean our code to have as few errors as possible, let us remove tag.

We need to add redux to the project so as to manage the state in store.

Dependabot couldn't find a package.json for this project.

Dependabot requires a package.json to evaluate your project's current JavaScript dependencies. It had expected to find one at the path: /package.json.

If this isn't a JavaScript project, or if it is a library, you may wish to disable updates for it from within Dependabot.

View the update logs.

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If possible include screenshots to help explain your problem.

Platform: Where did you see this bug (please remove those what does not apply):

• Google Chrome
• Safari
• Microsoft Edge

Additional context
Please add any other context about the problem here (like the Operating System where you witnessed the bug)

Is your feature request related to a problem? Please describe.
Preferences are reset when the site is reloaded.

Describe the solution you'd like
The user's preferences can be stored in localStorage in the browser and applied when the site is loaded.

Describe alternatives you've considered
IndexedDB and WebSQL are alternative storage but LocalStorage has a cleaner API to store and access the preferences. WebSQL uses a query like language which seems like an over kill for storing an object.

Cookies would also be an alternative but perhaps later for when the site is served from a backend (and not client side) so that security flags can be set from the server side.

Additional context
n/a.

Describe the bug
When a user open the preference pane to change the font size for the first time, the default value of the font size is not the same as the value on the slider. After using the slider, it then has the correct value.

To Reproduce
Steps to reproduce the behavior:

1. Go to the Reading view and click the Preference button (The one with the cog)
2. Click on the button to reveal the Preference Pane.
3. Change the value on the font-size slider
4. See error (On slight change the font will become much larger after which it will move in proportion to the slider)

Expected behavior
The default value on the slider should be equal to the default font-size

Screenshots
If possible include screenshots to help explain your problem.

Platform: Where did you see this bug (please remove those what does not apply):

• Google Chrome
• Safari
• Microsoft Edge

Additional context
Please add any other context about the problem here (like the Operating System where you witnessed the bug)

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

Which chapter is incomplete?
Chapter 3

What is the page of the correct information in the PDF of the guidelines

Chapter 3

Do you want to address the issue? (Delete inapplicable)

1. Yes

Images are missing from the project and need to be added one at a time.

Is your feature request related to a problem? Please describe.
Experience of reading the guidelines would be a lot better if someone could select which section they want to got to from the first page.

Describe the solution you'd like
A dropdown on the homepage that someone can select which chapter they want to head to and they are taken there straight.
.

Convert the entire codebase to typescript in preparation for a lot more functionality and contributions

Describe the bug
When you navigate to an other URL that is not the home directory "/", if you copy and paste the URL into a browser and attempt to visit you get a 404 Error with a message:

The resource you are looking for has been removed, had its name changed, or is temporarily unavailable. visible in the browser
and
HTTP404: NOT FOUND - The server has not found anything matching the requested URI (Uniform Resource Identifier). GET - http://edliz-dev.azurewebsites.net/settings visible from the console

To Reproduce
Steps to reproduce the behavior:

1. Go to the URL 'edliz-dev.azurewebsites.net'
2. Click on the button 'Read Guidelines' on the home screen.
3. Copy the URL you are sent to i.e 'http://edliz-dev.azurewebsites.net/chapters/1' and trying using the same link in another tab or simple reload the page at that point.
4. See error

Expected behavior
Using the same link should send you back to the page you were on before you attempted to reload. e.g 'http://edliz-dev.azurewebsites.net/chapters/1' should send you to chapter 1

Platform: Where did you see this bug (please remove those what does not apply):

• Google Chrome
• Mozilla Firefox
• Microsoft Edge

Additional context
It is hosted on Microsoft IIS/ ASP.net but may be changed to a Linux based server if necessary

Describe the bug
The scrolling track and thumb are small for usage with a mouse. On touch-enabled devices it is okay but when you have to use a mouse it is a bit annoying to have to pinpoint the track using a mouse pointer.

To Reproduce
Steps to reproduce the behavior:

1. Go to "Reading Mode" on a device you use a mouse.
2. Scroll using a mouse.

Expected behavior
A bigger thumb track on devices that are not touch enabled (or at least on larger screens)

Screenshots

Platform: Where did you see this bug (please remove those what does not apply):

• Microsoft Edge Dev on PC (PWA)

Additional context
Windows 10

Describe the bug
Blue links are hard to read when you are in dark mode. The color contrast is really bad.

To Reproduce
Steps to reproduce the behavior:

1. Go to 'Reading View'
2. Navigate to Chapter 36
3. Change to Night Mode
4. See error (Hard-to-read text)

Expected behavior
Color contrast should be better.

Screenshots
If possible include screenshots to help explain your problem.

Platform: Where did you see this bug (please remove those what does not apply):

• Google Chrome on Mac
• Google Chrome on iOS

Additional context

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If possible include screenshots to help explain your problem.

Platform: Where did you see this bug (please remove those what does not apply):

• Google Chrome
• Safari
• Microsoft Edge

Additional context
Please add any other context about the problem here (like the Operating System where you witnessed the bug)

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

There is a typo in the ReadMe. Instead of "Zimbabwe" it is spelt "Zimbwe"

(This is a demo for a Hacktoberfest event in Bulawayo)

Describe the bug
Application freezes when both the navigation panel and the

To Reproduce
Steps to reproduce the behavior:

1. Start the application from the source ( yarn start in the project root directory)
2. Click on 'Start Reading' to enter reading mode.
3. Click the Preference Button (The one with the cog).
4. Click the Hamburger Button at the top left corner.
5. Click the Reading area (Away from both the preference pane and the navigation pane)
6. See Error

Expected behavior
When the Navigation Button (Hamburger Button) is clicked, it is supposed to close the preference pane if it is open. The Preferences Button (cog) is supposed to close the Navigation Button if it is already open. The two are never supposed to be open at the same time.
Clicking away from any of either the Preference Pane or Navigation Pane should close them

Screenshots

Platform: Where did you see this bug (please remove those what does not apply):

• Microsoft Edge Dev

Additional context
This error is seen in development mode only. The application will simply freeze in production.

1. A user should be able to click on the main page and the nav closes
2. When the user selects a page the nav should automatically close.

Describe the bug
Slider thumb on Font Size input is not centred on the runnable track as it is supposed to on Microsoft Edge Browser on Windows 10.

To Reproduce
Steps to reproduce the behavior:

1. Go to 'edliz-dev.azurewebsites.net' on Microsoft Edge on Windows 10.
2. Click on 'Read Guidelines'
3. Click on the Settings Button which will reveal the Preferences tab with the Slider
4. See error

Expected behavior
The Slider thumb (blue circle) is supposed to be in the centre of the track... it is higher than it is at the moment.

Screenshots

Platform: Where did you see this bug (please remove those what does not apply):

• Microsoft Edge 42.17134.1.0 (Microsoft Edge 42.17134.1.0). This issue will not be the same on Edge running on Blink (i.e it is specific to EdgeHTML Rendering Engine)

Additional context
Microsoft is phasing out it's current rendering engine on Windows 10 in favor of Chrome which would get rid of this bug because does not affect Chrome. Still it is not such a huge issue and can be looked at.

Is your feature request related to a problem? Please describe.
I would like to be able to bookmark content that I read often so that I have quick access to it.

Describe the solution you'd like
I can have a collection of bookmarked pages that I can navigate to quickly

Describe the bug
When the site is live in ether the development server or the live version you get a 404 Error for the manifest file.

To Reproduce
Steps to reproduce the behavior:

1. Go to Google Chrome Browser.
2. Navigation to Live Production Site or Live Development Site
3. Add a trailing "/manifest.json" to the URL.
4. See 404 error

Expected behavior
The manifest file is expected to be in the home directory of the site. Going to "https://edliz.azurewebsites.net/manifest.json" must return the manifest file

Platform: Where did you see this bug (please remove those what does not apply):

• Google Chrome

Additional context
The test server is IIS and it is possible that this problem may be the result of the CI/CD pipeline.

Using both Yarn and npm on the same project introduces a some redudancy into the project and we are better off discussing which of the two we would like to use and settle to.

So for example, right now, if you run a push command in an IDE which is using npm as a default package management tool you run into errors because scripts in package.json will attempt to run
"pre-push": "yarn run lint".

So I figure we should just go with one and discard the other.

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If possible include screenshots to help explain your problem.

Platform: Where did you see this bug (please remove those what does not apply):

• Google Chrome
• Safari
• Microsoft Edge

Additional context
Please add any other context about the problem here (like the Operating System where you witnessed the bug)

Is your feature request related to a problem? Please describe.
Looking for content is a bother because users have to go through each section if they do not know where content is.

Describe the solution you'd like
Search bar inside of the navigation pane.

Describe alternatives you've considered
Using indexes as already supplied in the guidelines.

Additional context
An API is in development to make handle search queries.