wilandwil 7675e08455 Fix / Brought forward Stylize Toggle UI from #477 (#567)
> i have read the code of
[PR477](https://github.com/storytold/GottaGoFast/pull/477
), the things that were done to the editor is already in our code, so
the lipsync part should be fixed. However, the ui updates are not, this
branch is too old and we must not merge it, although it says no conflict
but when i pulled it to my local, i realize will override some editor
code that we probably don't want to override.

only the ui updates to the toggles are now brought forward here in this
PR

Co-authored-by: wil <wil@storyteller.ai>
2024-07-02 09:38:26 -04:00
2024-05-23 11:25:44 -04:00
2024-06-24 15:56:02 -04:00
2024-07-02 09:37:18 -04:00
2024-04-25 15:33:12 -04:00
2024-06-18 23:59:51 -04:00
2024-03-23 16:00:11 -04:00
2024-06-12 14:08:56 -04:00
2024-04-18 20:20:56 -04:00
2024-03-20 11:41:13 -04:00
2024-06-13 01:12:52 -04:00
2024-03-19 21:29:29 -04:00
2024-05-17 00:22:34 -07:00
2024-05-27 16:16:59 -04:00
2024-06-27 15:25:01 -04:00

Storyteller GGF

Coding Rules and Styles

Short Style Guide TS React and Engine:

No use of lets

No basic for loop operators.
Use the collection operators and array operators.

React Side / No modules over 200 lines. ( loose rule )

Don't do:
if (condition) return;

Do:
if (condition) {
	return;
}

No use of any type.
If you can use chat gpt to create the interface.

Branches

  • main - The main branch is the production source of truth.

    Changes to main will automatically build, but will not auto-deploy to production. You'll have to promote changes to production using the Netlify control panel.

    Merge your code to main frequently. If you have to have a long-lived set of changes, ask yourself whether it might be better to feature flag your code off and land it to main rather than fight rebasing against the whole team.

  • studio-staging - The staging auto-deploy branch.

    You do not ever need to interact with this branch. Changes to main will automatically be pushed to studio-staging and auto-deployed to https://studio-staging.studio.storyteller.ai . You can test changes that have landed in main here before promoting them to production.

  • studio-testing - The testing branch.

Anyone can push their changes to this branch for testing in a production-like environment. Since it is built and hosted on https://studio-testing.studio.storyteller.ai , you won't face CORS issues, same-site cookie issues, or have to use a local development proxy. (This doesn't obviate the need for a development proxy for fast development iteration, but is a fantastic way to test your changes in a "production-like" environment.)

Force push to this branch by using git push -f origin studio-testing

API Docs

Server API docs live here: https://storyteller-docs.netlify.app/

Local Testing & Development

Set up .env and the Proxy Server

Copy & paste the env settings from .env-local-proxy to .env, (if the file .env do not exist, simply create one at the root of this project's folder beside the other env settings files).

The settings from .env-local-proxy directs all requests to localhost:3000, this will relieve us from having to deal with CORS between various services.

Then, start the proxy server in the folder /proxy. Before running the proxy for the first time, run:

npm i

To start the proxy run:

npm run dev

If the proxy fails, make sure your node version is 18.18. If you need to change the node version run npm rebuild once before re-running npm run dev

Run the Code Locally

To setup and run this project's code locally:

npm install
npm run dev

Other Documentation

Here is the Swagger documentation for the backend endpoints

This project uses Remix for routing and Tailwind for styling:

On Netlify, we use functions:

Languages
Rust 59.4%
TypeScript 39.3%
JavaScript 0.7%
Python 0.2%
Shell 0.2%
Other 0.2%