Hey @juanma great question, I’m sure there will be people discovering Frontity asking themselves the same thing.
As a company we have the goal of positioning Frontity as the reference framework to build React Frontends for WordPress. There are already other great frontend frameworks like Next or Gatsby that are not specialised on a single backend, we consider that the best way to create a framework that brings something new to the table and adds value to the developers is by focusing on a more specific use case, WordPress in our case.
In addition, the framework is the result of almost two years working with WordPress publishers helping them create React frontends for their sites, so the design of the framework is very influenced by how WordPress works.
So I don’t see creating source packages for other backends becoming a priority in the near future for us as a company.
As I said, It’s not really aligned with our goals and strategy, so we wouldn’t give priority to this development. But if it makes sense for someone else, they could create their own source package and replace ours.
"@frontity/wp-source" is already a package, so it could be replaced by a different source. In any case, I’m sure that the @development-team would be able to give a better explanation of whats are the implications of replacing wp-source with a different source package.