What's it look like to create a dashboard within the WordPress admin for analyzing Google Analytics data across 900 blogs across 25 multisite instances? It involves designing a user-friendly interface, leveraging the WordPress REST API, implementing a plugin for data retrieval, and addressing challenges like rate limits and authentication.

CSS-Tricks is a go-to destination for web designers and front-end developers seeking insights into CSS techniques, web design trends, and best practices. Through a rich collection of articles, tutorials, and code snippets, CSS-Tricks equips developers with the knowledge and tools needed to create visually stunning and user-friendly websites. Whether you're looking to master CSS layout techniques, explore responsive design principles, or stay updated with the latest CSS features and browser compatibility issues, CSS-Tricks offers practical guidance and inspiration for elevating your web design skills.

CSS-Tricks

This post discusses the implementation of a dashboard in the WordPress admin area to browse Google Analytics data for approximately 900 blogs, spread across 25 WordPress multisite instances. The author covers the use of the WordPress REST API, the decision-making process between using JavaScript and PHP, handling rate/time limits, security measures, custom database design, and caching strategies. The post also highlights the challenges of making concurrent HTTP requests and the advantages of asynchronous JavaScript for this task.

WordPress Multi-Multisite: A Case Study

The part where we say, “Oh Right, CORS.”

Auth, Part 2: I’ve been known to auth myself

Really interesting and well explained article !
All I kept thinking about , and please don’t take it the wrong way , was how much revenue ( approximately ) 900 blogs would make ?

I love the fact that people keep coming up with more creative/complex ideas of how to use WP.

When I first discovered WordPress, Multi-Site peaked my interest since I had a technical background.
I even tried it on several client sites, including a German Beer company that had 90 subsites for every country their beer had a presence in.
What I learned, is STAY AWAY FROM MULTI-SITE Netoworks:
<ol>
<li>A significant amount of Premium Plugins dont support Multisites</li>
</ol>
2)I learned the hard way, that even Premium Plugins thats stated they supported Multi-Site Networks, never really tested their plugins to work out all the bugs that WOULD ALWAYS POP UP.
3)Even the Big names in Hosting and those that claim that they support Multi-site networks, would gremlin the Htaccess file and always rewrite it even outside of the area they were not supposed to touch. They woud then claim Multi-Sites were “Complicated” and I needed to hire a developer. I WAS THE DEVELOPER.
<ol start="4">
<li>Hosting providers that claimed they integrated with Cloudflare, yeah that was a disaster when Multi-sites were introduced.</li>
</ol>
5)Several years ago even Cloudflare had serious issues with Multi-Sites (not sure what status is now).
<ol start="6">
<li>
Even the Premium Backup and recovery plugins, you would always have to but the most expensive “Elite” package, to be able to back up, recover and CLONE Multi-sites.
</li>
<li>
NONE OF THE HOSTING PROVIDERS I USED, Were able to provide a staging environment for Multi-site networks.
</li>
</ol>
Honestly best thing to do is to NOT USE IT, and go with seperate wordpress installs on sub domain or sub directory.