diff --git a/README.md b/README.md index 86836f6..c11036c 100644 --- a/README.md +++ b/README.md @@ -17,8 +17,6 @@ The methodology is based on the principles of ___strictly separating___: - Release tasks from build tasks. - Dynamic content from static content. -These principles are inspired by [The Twelve-Factor App](https://12factor.net/). - ## Concepts The following concepts define the core requirements for an _Immutable Web Application_. They are framework and infrastructure agnostic. @@ -226,6 +224,12 @@ _Immutable Web Applications_ methodology builds on several trends in web applica - __Maturing Application Patterns & Practices:__ Backend applications and services are converging around a set of best practices that support portability, scalability, and high availability. This trend has dramatically increased the tools and services available, especially related to containers and container orchestration. Many of these practices are just now starting to be applied to static single-page web applications. +## Influences + + - [__The Twelve-Factor App__](https://12factor.net/): This methodology for building web apps is based on _separation of concerns_ in order to achieve portability and robustness. _Immutable Web Apps_ separate several of the same concerns in order to achieve similar objectives. + + - [__JAMstack__](https://jamstack.org/): The _Immutable Web Apps_ methodology is completely aligned with the [best practices](https://jamstack.org/best-practices/) of the JAMstack. + ## Future Work _Immutable Web Applications_ is not yet actively supported by any application framework, tools, or services. Most static, single-page applications should be able to adopt the _Immutable Web Applications_ methodology by making several minor structural changes to the codebase, build process, and infrastructure. Until there is widespread support, however, web applications that use advanced [code-splitting](https://webpack.js.org/guides/code-splitting/) techniques may find adoption to be complicated or impractical.