|
1 | | -# Intro |
| 1 | +--- |
| 2 | +title: Freenit framework for Svelte and FastAPI development |
| 3 | +description: Freenit is a web development framework that combines a visual designer, Svelte frontend tooling, FastAPI backend tooling, and reusable snippets to speed up product delivery. |
| 4 | +--- |
2 | 5 |
|
3 | | -Freenit is framework made to automate all your WEB dev work. It is made of tree |
4 | | -parts: |
| 6 | +# Freenit framework for Svelte and FastAPI development |
5 | 7 |
|
6 | | -* Designer to speed up design and UI work |
7 | | -* Frontend library based on Svelte |
8 | | -* Backend library based on FastAPI |
| 8 | +Freenit is a framework for automating modern web application development. It combines three parts: |
9 | 9 |
|
10 | | -The idea is to automate and integrate as much as possible and let you be just |
11 | | -creative and concentrate on important stuff. Usual workflow is to use designer |
12 | | -as drag and drop tool for UI and export it as code. While working on it, saving |
13 | | -your work in `.json` format enables you to save it in git and easily "rewind" |
14 | | -to the UI design at a certain point. When code is exported from such `.json` |
15 | | -file, it is pixel-perfect UI, but still not perfect code. Running |
16 | | -`npm run format` will help. You will still need to adjust the code to add |
17 | | -integration with backend, but it is in the best shape generic code can be. Once |
18 | | -you reshape the code to your liking, `data` variable in such code can serve as |
19 | | -format of messages frontend expect from backend. The backend work is usually in |
20 | | -two parts: DB models and API endpoints. In all of this code snippets will help |
21 | | -you if you use VSCode or LunarVim (list of supported editors will expand over |
22 | | -time). |
| 10 | +* A visual designer to speed up UI and design work |
| 11 | +* Frontend tooling based on Svelte |
| 12 | +* Backend tooling based on FastAPI |
23 | 13 |
|
24 | | -All of this is just words. Dive into tutorial to see what Freenit is really |
25 | | -about. |
| 14 | +The goal is to automate the repetitive parts of product development so you can focus on implementation details that matter. A common workflow is to build UI in the designer, save it as `.json`, version that file in git, and export the result as Svelte code. The exported code is intended to be pixel-accurate and easy to reshape for your application. After that, you can connect it to backend data models and API endpoints, with reusable snippets helping on both sides of the stack. |
| 15 | + |
| 16 | +This documentation explains the designer, frontend, backend, and snippet workflow in one place. |
26 | 17 |
|
27 | 18 |
|
28 | 19 | ## Bootstrap the Project |
|
0 commit comments