DanielFlaum
commented
3 years ago My default strategy:
Attack each kind of page in turn, beginning with the most numerous pages and ending with the most unique pages.
Start with item pages because they are the first uploadable product produced by the other workers and so are the lowest hanging fruit. Proceed onwards to collection pages when enough items are gathered that the team can turn attention to them.
These first two kinds of pages should give me enough experience, momentum, and content to turn to navigability and accessibility. From there, consider the special purpose pages (since these will need to be built in coordination with writers elsewhere on the team).
Finish with the homepage, and then audit to ensure accessibility.
In the software engineering course, students are taught that software projects must choose a process and a methodology. These are necessary to help teams of developers and other stakeholders stay organized and produce a high quality product.
But they are likely overkill for this project, where there is a single developer wearing multiple hats. Negotiate a simpler strategy, so that Dr. Hildebrandt and Dr. Smith understand how Daniel plans and carries out development and how that connects to the progress they can see. This strategy can then be more easily modified over the course of the project if needed.