emilymaitan / pae_em4 Goto Github PK

ToDo:

• update the ProjectController to query the API for a project by ID

Depending on the final API functionality,

• update the project.twig novelty and popularity (min/max) values -- probably set static variables in Project.php for this
• update the project.twig to display a graph (or several) - or remove the graph placeholder

Implement the search bar in the nav. Write a controller that handles (parses, cleans etc.) search queries. Remember that all user input is evil... 🙉

Up to now, dependencies in the htdocs folder are handled manually.
I should look into using npm to keep them up-to-date.

Chaining projects together. This task is entirely optional.

• similar projects
• recent searches
• you might also like - functionality

Filter for projects by clicking on a date from the calendar.

Create the base classes for querying the API:

• IApiConnector - interface for swapping out the API or creating a mockup implementation
• RestApiConnector - for talking with the REST API

Additional classes for parsing JSON and XML files.

• iParser interface to adapt to changing API data formats
• JsonParser and/or XmlParser

Optionally,

• implement a mock API connector

Names may vary. 😉

Dynamically generated table containing all projects added the the DB today.

ToDo:

• update the SearchController to query the API for projects by name
• update the SearchController to query the API for projects by date

Depending on what functionality the API will finally offer,

• implement REST-like /projects/year/month/day search

Currently, all requests for projects are sent to the same demo page.
Fine for a mockup, but I eventually want to implement proper routing. The URL pattern should be:
\projects\{id}_{name}
because I believe name alone will not suffice as unique identifier.

Files that need to be edited/created: config.php, a proper project routing handler. I might have the Project Controller do it.

The footer is currently always displayed, but I'd like it to be static on the bottom.
Boostrap footers are apparently sticky by default, so I need a clean workaround.

Set up the project page. Necessary steps include...

• update config.php for routing
• create a new controller class
• create a new twig template

Display novelty and popularity index for each project. I might use bootstrap's progress bar for this.

ToDo:

• update the HomepageController to query the API status
• update the HomepageController to query the API for today's projects

depending on how the API data turn out, ...

• update homepage.twig to trim overly long descriptions to a reasonable size
• update homepage.twig to not display ALL projects, OR implement pages

Currently, the calendar in the homepage via which you can search projects by date is not fully implemented yet. On click, it does redirect to the correct URL, but since I have not yet implemented routing, controller nor the twig-template, the "404 not found" page-text will be displayed.
I will implement this controller once I plug the API in.