A look into the future #51
D-Inventor
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Surprise! We've got some goodness for you here! Well... not yet, but we have some awesome plans that I would like to share with you on how we're going to make the URL Tracker even more awesome than it already is. The plan is to take the URL Tracker through several phases of improvement to end up with the most awesome plugin you've ever seen!
Let's have a closer look:
Phase 1: The appetizer
The first phase is a small set of changes to improve the experience before we get started on the big changes. This entails some increased filtering on the registered 404 NOT FOUND results to reduce clutter and to make space for the results that really matter. No more interface full with api endpoints and wordpress bots.
Phase 2: Reimagining the database
The database is currently a big factor that holds us back from improving the URL Tracker. Obviously, a database about redirects and client errors should have tables for redirects and client errors, so why this hasn't been so since the beginning is a mystery to me. This poses a big challenge though. We need to transition from a single table with both redirects and client errors to a system with 2 or more tables. That means not only changing the schema, but somehow also transfer the data from the old table to the new tables. As much trouble as it may be, it'll definitely be worth it, it will significantly reduce the memory footprint of the URL Tracker as well as significantly improve the performance of database queries. We've noticed with over 1.000.000 records in the database, occasionally the database times out and that's not only undesirable, but simply unnecessary.
Phase 3: The opt-in modules plugin structure
A URL Tracker is nice, a modular URL Tracker is better. Why restrict you to something we made? If you would like certain features differently, why should we prohibit you from making it better? No reason, so that's why we want to introduce the opt-in plugin structure. This means separating the cache from the core logic, the backoffice from the web library, the notification handlers from the UI and more.
Am I supposed to install all these plugins by myself? No, you're not. simply installing the UrlTracker package will install all the default modules for you so that you don't have to worry about anything. If you want to use different modules, or make a module yourself, then you can install just the packages that you need.
Phase 4: The redesign
The fourth and final phase is a big change in the UI. You may or may not have already noticed the issues about the redesign. We would really like to get some feedback on those still, so do make sure you check them out and share your thoughts on them!
Anyway, we're going to implement the new design in this phase. We're going to move from just 404 NOT FOUNDs to a more generic "recommendations" model. What does that mean? It means that you'll not only see which URLs are not found, you'll also see how important it is for you to solve, what kind of resource the URL means, more statistics on visits on this URL. Not only that, we'll also be able to give other kinds of recommendations, like removing unused redirects, double redirects / circular redirects and what ever else we can come up with. All of that and also a more accessible UI with less clutter, less stress and more productivity
So as you can see, the URL Tracker has a bright future ahead of itself, with many awesome developments on their way. What are your thoughts on the future of the URL Tracker? What is your favourite feature of the URL Tracker? Do you think it's awesome? Leave a comment here and share your thoughts!
Beta Was this translation helpful? Give feedback.
All reactions