As of this post, there are only links to the next chapter at the top of the page. I'm not there when I want to go to the next chapter, because I've scrolled all the way to the bottom. Links at the bottom would make it easier to continue reading.

PMD 6 has re-organized its rule sets, making the old PMD categories JPacman used obsolete.

PR #120 just re-added the best practices, but it would be better to rethink all rules used, and to update the pmd-rules.xml file accordingly.

This relates to the (lack of) JUnit 5 rules for PMD.

We should have the ability to share examples a la jsFiddle. There are some examples that I would like to share with my students without having to recreate them each time.

Links referring to Python_Linux_Vi in the lectures README.md are broken.

Additionally, the links in the README.md file in the Python_Linux_Vi directory are also broken.

It is unclear if data should be added and what is going on with the NEON site mentioned. Remove the excessive details and be explicit about the fact that there is no data being entered.

Exercise expression, task 4 b):
A lot of students write numbers too large to be stored in an Integer and gets the compilation error "integer number too large" instead of the runtime error "java.lang.OutOfMemoryError".

This could be solved by adding a tip telling them not to use a number larger than 2 billion.

Task Description

Add ## Documentation Requirements below the acceptance criteria. This is to make sure we think about what docs to write during task inception.

Acceptance Criteria

• there is a documentation requirement/check in new task templates

Copywrite Requirements

None

Analytics Requirements

None

This will allow students to navigate the repo structure easily, without having to come back to the main repo each time.