[WIP] External Data Sources - Headless Wordpress PoC

[hutchgrant]

Related Issue

Resolves #21

Summary of Changes

Created a new lifecycle called sources, which simply pulls from sources, populates a graph, and then scaffolds out components from each post. In this example, I'm pulling posts from a wordpress instance into graph, creating components and routes, rendering statically using greenwood. This could be applied to other wordpress features, or any other CMS.

Development

You can now test this out using docker via docker-compose.

# to run in detached mode add -d argument
$ docker-compose up

# wait a few minutes for containers to start up and connect to each other
# wordpress should be accessible via http://localhost:8004
# in another shell or same (if running detached)
$ yarn serve

You should now see the wordpress post from http://localhost:8004/test-greenwood-headless-1/ available at http://localhost:8000/test-greenwood-headless-1/ within greenwood

A second post http://localhost:8004/test-greenwood-headless-2/ should be available at http://localhost:8000/test-greenwood-headless-2/ within greenwood

our test wordpress container has a username and password: greenwood which should be set by default with the included sql dump.

TODO

• Working PoC of basic posts in greenwood from a wordpress instance
• Merge and apply conditions so that it works alongside wc-md-loader
• Create an easy to duplicate development environment with wordpress using docker
• refine and modularize lifecycles API so that it can be made into a wordpress plugin, seperate from greenwood core.

[thescientist13]

Just scanning this and looks pretty cool @hutchgrant! Will definitely look to pull this down soon and play around with it.

If things are looking good locally we should plan to try and get a WP LightSail instance up in AWS and we can do it for "real".

From there we can work on making it a plugin, refactoring, and all that jazz once the release/0.4.0 branch gets merged in master and brings in all the monorepo stuff.

[thescientist13]

closing this for now since a big refactor is underway. This issue will definitely be re-visited as part of the Roadmap to 1.0 Project, after the release of the refactor.