https://github.com/appsmithorg/foundry
A collection of apps smithed in the foundry. Browse templates, sample apps, designs, and other resources, from Appsmith and the Appsmith community.
https://github.com/appsmithorg/foundry
blogs designs js-snippets sample-apps templates tutorials videos
Last synced: 4 months ago
JSON representation
A collection of apps smithed in the foundry. Browse templates, sample apps, designs, and other resources, from Appsmith and the Appsmith community.
- Host: GitHub
- URL: https://github.com/appsmithorg/foundry
- Owner: appsmithorg
- License: mit
- Created: 2022-09-06T13:14:26.000Z (about 3 years ago)
- Default Branch: main
- Last Pushed: 2024-09-28T13:07:39.000Z (about 1 year ago)
- Last Synced: 2025-04-02T19:07:55.632Z (6 months ago)
- Topics: blogs, designs, js-snippets, sample-apps, templates, tutorials, videos
- Language: JavaScript
- Homepage: https://www.appsmith.com/community
- Size: 6.93 MB
- Stars: 52
- Watchers: 12
- Forks: 17
- Open Issues: 4
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Appsmith Foundry Custom Library
This is a collection of utility functions for common tasks in JavaScript. This module includes functions to work with arrays, objects, and generate unique IDs. It's designed to be simple to use and can be easily integrated into your Node.js, browser-based projects or Appsmith apps.
*Note: This method requires a public Github repository.*
## Installation
You can clone this repo using Git to create and modify:
```sh
git clone git@github.com:appsmithorg/foundry.git
```
Once cloned, you will need to install the Node modules to get it ready for usage. This should only be needed the first time (unless you add extra modules).
```sh
npm install
```
Alternatively, you can follow the tutorial to set your own foundry up from scratch. (coming soon)
## Usage
1. Create a new sub-directory in the `libraries` folder. This should be the name of your custom library.
2. Create an `index.js` file in that folder, and copy your code in there. Currently, this is expected to be an Appsmith JSObject.
3. Run `npm build` to generate the UMM file and a helpful README for your library.
4. Commit and push your changes to a public Github repo.
Your library is ready for usage using JSDelivr. See the generated README for the link.
## Repo management
Each library should be added to its own folder in the `libraries` directory as a single `index.js` file. This is intended to support simple libraries that are contained in a single file with few or no dependencies. The default expectation is that you can directly cut/paste an Appsmith JSObject into your `index.js`.
The repo used `@rollup` to process your code into a UDM file, and expects to use JSDelivr for CDN delivery.
### Scripts
- **build** - runs both the UMD & the readme file generation commands. In essence, it is the same as running `umd.generate` & `readme.generate`. This is the default command to update your repo when you add or update a library.
```js
npm run build
```
- **readme.generate** - used to generate a readme file for each library. It uses the `jsDocLite` library in this repo to parse the JSDoc comments out of the library `index.js` file. It will iterate over each library and save the README to that directory.
```js
npm run readme.generate
```
- **umd.generate** - used to generate the UMD code versions in the `dist` directory. This will iterate over every folder in the `libraries` directory and use the `index.js` in each one. The name of the folder will be the name of the library.
```js
npm run umd.generate
```
## Libraries availble
Here are the libraries available in this repo and how to use them. All of them are availble using JSDelivr so you can import them into your Appsmith app.
## `jsDocLite`
This is a simple library that uses basic JSDoc style docblocks to comment your code and generate docs. We are actually using it in this repo to automatically generate a README for each library. It doesn't offer full JSDoc support, but the basics are good.
- [documentation](https://github.com/appsmithorg/foundry/tree/main/libraries/jsDocLite)
- [commenting guidelines](https://github.com/appsmithorg/foundry/tree/main/libraries/jsDocLite/COMMENTING.md)
- usage:
```sh
https://cdn.jsdelivr.net/gh/appsmithorg/foundry@main/dist/jsDocLite.umd.js
```
-----
### FAQ
1. *Can I remove the libraries in the original repo?*\
Yes! The `build` command currently expects the jsDocLite library to be available. It uses the JSDelivr version of the library, so you can safely remove it from your clone of this repo.
2. *Why does this method require a public Github repository?*\
Firstly, JSDelivr has a native Github integration that makes it easy for us to create a CDN URL without any registration or setup. Secondly, in order to work, both JSDelivr and the app need to be able to access the library over a public connection.
3. *Why did you create a JSDocLite library instead of using JSDoc?*\
Partly because JSDoc is a bit overkill for our use case, and partly because we wanted a simple JSDoc parser that can be used client side... such a thing doesn't exist. Mostly - for fun.
### Dev dependencies
- npm
- You will need the Rollup node modules for doing the UMD generation
- The readme.generate command relies on the jsDocLite library, which is included as a CDN call to JSDelivr.
### Todo
- jsDocLite
- Allow it to work with multiple comment lines
- add @todo
- Make readme generator easier to use with a template
## Contributing
Contributions are always welcome! Open an issue or a PR!
## License
[MIT](https://choosealicense.com/licenses/mit/)