| --- |
| title: 'LLM Embeddings Explained: A Visual and Intuitive Guide' |
| emoji: 🚀 |
| colorFrom: yellow |
| colorTo: purple |
| sdk: static |
| pinned: true |
| license: apache-2.0 |
| header: mini |
| app_file: dist/index.html |
| thumbnail: >- |
| /static-proxy?url=https%3A%2F%2Fcdn-uploads.huggingface.co%2Fproduction%2Fuploads%2F647f805de9c81260ff8881ee%2F8v52lNo2sFtNySUlVnXF4.png%3C%2Fspan%3E%3C!----%3E%3C%2Ftd%3E%3C%2Ftr%3E%3Ctr id="L13"> | | short_description: How Language Models Turn Text into Meaning, From Traditional |
| --- |
| |
| Check out the configuration reference at https://huggingface.co/docs/hub/spaces-config-reference |
|
|
|
|
| Instruction to install and run locally |
|
|
| ```bash |
| npm install |
| npm run build |
| npm run dev |
| |
| // If you want to change something change it in src/.... |
| |
| // Once you are finished |
| npm run build |
| // And commit the dist folder |
| ``` |
|
|
| ## Loading HTML fragments: |
| There are two way to load HTML fragments: |
| 1. Compile them into html during build time |
| 2. Fetch them and insert them during run-time |
|
|
| ## When to use what |
| - Use compile time fragments only on parts which you want to ensure are seen by every user right after page load (e.g logo) |
| - Use run-time fragments for everything else so that the final HTML is of reasonable size (<1MB idealy) |
|
|
| ## How to add a new fragment |
| - Add it to the `src/fragments` folder (e.g. `src/fragments/banner.html`) |
| - For run-time fragments, add {{{fragment-name}}} to appropriate place in `src/index.html` (e.g. {{{fragment-banner}}}) |
| - For compile-time fragments, add <div id="fragment-name"></div> to `src/index.html` where you want to insert the fragment (e.g. <div id="fragment-banner"></div>) |
|
|
|
|
| ## How to know which fragments are available |
| - Run `npm run dev` and look at the console for available fragments |
