Build a Website that ingests, processes and displays RSS Feeds

OVERVIEW I’d like help developing a LAMP Stack web app that works with RSS Feeds. It ingests articles shared through RSS (using web hooks and the Superfeedr API), hands off new articles to Alchemy API for processing, stores the result and then displays them for a user who can filter them by the available meta data. DETAILS I see the system having several parts: 1. The RSS Feeds The RSS Feed collection part should use SuperFeedr. I have a basic (free) account set up. I need an admin page that talks to the API to show which feeds I'm subscribed to and add and delete others. Superfeedr uses web hooks to let you know when new articles are published. This will have to be configured (and you’ll have to write me some instructions on how to set this up on my server). When a new article comes in, the web hook will have to tell the script to process it (see the next step). Every article that comes in should be processed by Alchemy API. 2. Processing new articles When a new article comes in through the SuperFeedr web hook, we send it to be processed via Alchemy API. I have a basic (free) account set up with them. For each article I’d like to store: —The PERMALINK URL, TITLE, AUTHOR and PUBLICATION DATE-TIME (if available) from the RSS Feed —The EXTRACTED TEXT, list of CONCEPTS with RELEVANCE SCORE, IMAGE URL from Alchemy API —Date and time stamp of the transaction I’d like to have the data stored in a local MySQL database. You’ll have to send me a basic model that I can import into my database and some kind of config file where I can add a username and password of the database. I’d like the option of turning on email notifications containing: —The contents saved for each transaction along with the time it took to process it —An error log for each failed transaction 3. Results View By default, this page should show the most recently processed articles in chronological order (most recent first), and scroll infinitely (loading blocks of X (10?) articles automatically when the bottom of the page is reached). See attached image “[login to view URL]”. For each article, the page should show the URL for the site from which it comes, an image (normalized into a square) if there is one, the title and as much of the article will fit in the remaining space, with an ellipsis (“…”) at the end. See attached image “[login to view URL]”. There is a menu that shows the Concepts (which I call “topics”) captured from Alchemy API. When the user clicks on this “Topics” menu, they see all the topics that have been identified in the past 7 days (this period of time should be easily editable). The menu may need to scroll. Each topic is followed by the total number of occurrences of that topic in the period (in parentheses). The menu can be sorted alphabetically, but the default sort is by largest number of occurrences (I call that "most popular"). If the list is already sorted alphabetically, and the user hits the alpha sort control again, then the sort should toggle to reverse-alphabetical. Likewise with the most occurrences control. When a topic is selected from the menu, it becomes a filter that is added, one at a time, to the the list of filters… See attached image “[login to view URL]”. One or more topic filters can be active at any time. They should function as an AND, meaning that if the topics selected were cats, dogs and chicks, the articles returned should all contain all of those concepts and be listed in chronological order. There is also a search string field. This simply filters for the string in the extracted body copy of the article and has nothing to do with the topic. 4. Reading View Click on an article in the results view and come to the reading view. See attached image “[login to view URL]”. Save should push the permitting url to Instapaper. Share should use some standard sharing interface such as Add This.