✅ Beta Roadmap & Progress

[luisherranz]

Github project here: https://github.com/frontity/frontity/projects/1

Feel free to edit this post when you finish something.

Roadmap

• Repository organization

  • - To monorepo or not to monorepo.
  • - Configure releases with lerna.
  • - Configure Travis.
  • - Configure Jest.
  • - Configure TypeScript.
  • - Configure Conventional Changelog.
  • - Include an examples folder and refactor @frontity/core urls.

• Build phase

  • - Babel configuration for module, es5 and node [#PR].
  • - Wepack configuration for development and production [#PR].
  • - Produce both es5 and module bundles [#PR].
  • - Integrate Koa inside server [#PR].
  • - Create production dev script [#PR].
  • - Create production build and serve scripts [#PR].
  • - Generate all entry files with correct package imports for each mode.

• Serve phase

  • - Hot Module Replacement [#PR].
  • - Integrate with Loadable Components (code splitting) [#PR].
  • - Serve both es5 and module bundles.
  • - Serve static files from Koa [#PR].
  • - Make server bundle ready for serverless [#PR].
  • - Import the correct packages on each bundle.
  • - Load settings on demand.
  • - Render Root and Fills components from packages.
  • - Integrate SSR with Emotion.
  • - Integrate SSR with React-Helmet.
  • - Create default templates (both html and amp)
  • - Create store for the settings.
  • - Create store for the build.
  • - Create Overmind store in the server.
  • - Create Overmind store in the client.

• State Manager

  • - Create connect.
  • - Integrate state.
  • - Integrate actions.
  • - Integrate libraries.

• @frontity/file-settings

  • - Decide on a final schema.
  • - Create types for frontity.settings.js.
  • - Create APIs to get packages and settings in the SSR.

• @frontity/wp-source

  • - Figure out how to do the URL discovery.
  • - Decide on a data schema.
  • - Create APIs to fetch and retrieve data.

• @frontity/tiny-router

  • - Create APIs to set and get router state.
  • - Make it work with browser’s history.

• @frontity/mars-theme

  • - The theme can render the home.
  • - The theme can render lists of categories and tags.
  • - The theme can render posts.
  • - The theme can render pages.

• Typescript

  • - Create the Settings type.
  • - Create the Package type.
  • - Create the Connect type.

• Docs

  • - The docs have an Introduction section.
  • - The docs have a Getting Started section.
  • - The docs have a guide to create a new theme.

• CLI

  • - Should have a frontity create command.
  • - Should have a frontity dev command.
  • - Should have a frontity build command.
  • - Should have a frontity serve command.

[luisherranz]

I’ll start!

I’ve been working with Mario in the forum and also thinking a lot about all the things we need to figure out for the v1.0 launch.

I’ll open more posts for each topic so we can:

• Start all the discussions and design.
• See the roadmap ahead and set our goals.

[orballo]

I’ve been writing down info on react-imported-component and loadable-components to decide what to use.

I’ll be trying those libraries and build a basic project with them to understand how they work.

[luisherranz]

I’ll keep opening posts for each topic we need to work on or think about.

[David]

I’ve been investigating how to organize our repositories in order to use multirepos and semantic release and today I’m going to deploy and configure a WordPress server which it is intended to be the CMS of our organization webpages.

[luisherranz]

Amazing. Once you finish with that, can you set up the main repo frontity/frontity with Lerna?

[orballo]

I’ll be trying out loadable-components.

[David]

Yes, sure! I’ve finished configuring the WP server, and also the single-sign-on authentication to login in WP using the Discourse credentials, just to give it a try.

[luisherranz]

I’m working with @SantosGuillamot trying to figure out how to catch Discourse events to send them to GTM.

And I’ll be opening more posts today:

• Our old build store (no idea how to name it yet).
• The Settings API.
• The Source API.

[orballo]

I’ll be working on a post about all the requisites we’ll need to fulfil in other to have 100/100 score in every category of Lighthouse.

[David]

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.

[luisherranz]

Yesterday I didn’t have time to create these posts:

• Our old build store (no idea how to name it yet).
• The Settings API.
• The Source API.

but I’ll try to find time today to do so.

[orballo]

Today I finished with the investigation on Lighthouse.

[luisherranz]

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.

[orballo]

I’ll be setting up the eslint config in frontity.

[luisherranz]

I’ve been working in these two posts:

• How to resolve dynamic imports in Webpack
• The Settings API [WIP]

Today I want to finish How to resolve dynamic imports in Webpack (I have an idea to solve it).

[orballo]

I’ll be investigating how to manage our monorepo of WP plugins. PHP modules, dependencies between packages, tests, composer…

[luisherranz]

Last weekend I worked on the first scripts of the framework in this PR:

[WIP] Add framework scripts (dev, build, serve)

I want to get it to a point where either Edu or David can take over and finish the SSR.

[David]

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.