43

GitHub - Webiny/webiny-js: Serverless CMS (GraphQL + React)

 6 years ago
source link: https://github.com/Webiny/webiny-js
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
neoserver,ios ssh client

README.md


68747470733a2f2f73332e616d617a6f6e6177732e636f6d2f6f776c65722d696d6167652f6c6f676f2f776562696e795f6f776c65725f32303136303232385f3233323435335f6f726967696e616c2e706e67
Web development made easy.

Official Website | Packages

Prettier Discord license SemVer

Branch Build master (latest release) Build Status development (active development) Build Status

Webiny is an open-source platform created for building modern web apps.

Install

More on the installation process soon...

About

Webiny consists of two layers that work closely together.

GraphQL API

API layer works as a Lambda function with Apollo-Server handling all the GraphQL-related stuff. In addition to that we created a simple data-sources wrapper inspired by GrAMPS (and later Apollo data-sources). It helps you develop separate modules (packages) and stitch them together to build one big GraphQL service.

Client layer (SPA)

Our client (SPA) layer is based on create-react-app v2 and Apollo Client. If you ever developed using those tools - you already know Webiny :) As our UI library we are using Material Components, and a very promising project RMWC to get going with Material faster. You can see all the currently available components in our storybook.

Admin app

We provide you with an administration app so you can kickstart your projects much faster and begin developing features for your clients right away. The entire admin app is based on plugins and you can customize everything. Each of the plugin is documented and has a corresponding Flow type to help you while coding.

Project organization

We have decided to use a monorepo organization and have fixed publishing (so when we publish a change, all the packages will be published using that same version).

FAQ

Why not microservices ?

We are planning on going the microservices way but at this point it really is not necessary. The local data-sources approach is already a good separation of business logic which will make migration to microservices much easier later on.

Contributing

Please see our Contributing Guideline which explains repo organization, linting, testing, and other steps.

License

This project is licensed under the terms of the MIT license.


report

Recommend

About Joyk


Aggregate valuable and interesting links.
Joyk means Joy of geeK