Yesterday I was moving the old repositories to clean up the organization on GitHub and start with the new repositories. I have also created a monorepo and I have been investigating a bit how to execute scripts with Lerna just after launching a new version.
What I’ve seen is that people use the postversion script in the package.json, as explained in npm-scripts, to perform that task, and not something Lerna-specific.
Yesterday I didn’t have time to create these posts:
but I’ll try to find time today to do so.
Today I finished with the investigation on Lighthouse.
I’ve been working with Pablo setting our goals for the first two months so didn’t have time yesterday either. I hope today is the day to finish at least 1-2 of those posts.
I’ll be setting up the eslint config in frontity.
I’ve been working in these two posts:
Today I want to finish How to resolve dynamic imports in Webpack (I have an idea to solve it).
I’ll be investigating how to manage our monorepo of WP plugins. PHP modules, dependencies between packages, tests, composer…
Last weekend I worked on the first scripts of the framework in this PR:
I want to get it to a point where either Edu or David can take over and finish the SSR.
I’m working right now in setup a monorepo for the wp-org plugins, using Lerna. I was a bit stuck trying to update the plugin’s version in the .php file after bumping them in the package.json but I think I have an idea to solve it.
I’ll be figuring out how to work with composer and monorepos, unless something more important comes up.
Today I’ll be working on how frontity sources should work.
Yesterday I was working mostly on solving how to combine serverless (only one file for the server bundle) with code splitting in The Frontity Server Architecture: Serverless.
I’ll keep working on that today, I think I have an idea to make it work.
Still working on the Settings API.
Yesterday I was looking at both WordPress REST APIs (wordpress.org and wordpress.com) and I found something funny with the last one.
If you are using wp.com REST API it seems that you can’t make a GET /sites/$site/media call without authentication, which is bad. 
Also, when you retrieve posts using a GET /sites/$site/posts call, the attachment attribute will contain up to 20 attachments, no more, as explained below.
| parameter | type | description |
|---|---|---|
attachment |
Object | Hash of post attachments (keyed by attachment ID). Returns the most recent 20 attachments. Use the /sites/$site/media endpoint to query the attachments beyond the default of 20 that are returned here. |
I’m going to investigate if there’s something else that can be done, but at the moment it seems that the only way to get all media items in a post (if it has more than 20) is to use authentication.
I keep working in the first scripts, and I almost got serverless working as well. I hope to have it finished today.
Still working on the Settings API.
Yesterday I was working in a communication with @SantosGuillamot and @Reyes and today I’ll try to merge the npm run dev script and help @David and @orballo with the Settings API, the Source API, Overmind and TypeScript.
I’m writing the final schema for the Settings API.
I want to take a look at the way we produce bundles to see if we can make one client bundle per mode and per site as outlined here: How to resolve dynamic imports in Webpack