Home
Meta:
This is the Landing Page, holding the information about navigating through this document. It should also host the feedback from anyone on the RW team wishing to improve this document
... wip
Please use the sidebar (pointed to by the blue arrow below) with the index for this document to directly access any page. For sequential browsing click the Next page link at the bottom of each page. While the pages of this wiki are sorted alphabetically, the sidebar uses logical sorting.
The are several pages that are not fully fleshed out, so it is possible that multiple "sub-items" in the index sidebar point to the same page.
This document describes several different approaches to platform independence in the process of creating and maintaining a RedwoodJS platform-based app, with a particular focus on the development tools on the Windows platform. Since the Windows platform does not have the Unix heritage, offering a very different native interface to Windows applications, it was necessary to create this document, that explains several different approaches to achieve platform independence.
While the User Experience of writing Redwood application is the same on all supported platforms (OSs), some of the development tools vary significantly enough to warrant the creation of a separate document named Developing Redwood applications on Windows platform This approach (having the description of all Windows-based application development contained in a single document) is more user friendly that "peppering" the existing documents short Windows-based sections explaining how to do this in Windows.
RedwoodJS is a platform-independent framework, offering a nearly identical user experience on Linux, macOS, and Windows. In addition, as you can see in this presentation by RedwoodJS co-founder Tom Preston-Werner, it brings "full-stack to JamStack" offering the full support for parallel development of the "front-end" and "back-end" components of your full-stack application.