[Hold] Platform: Remove Custom option from 'build it with me' workflow type selector (#449)

Author: Paul-Cornell

platform/workflows.mdx

@@ -21,10 +21,6 @@ The Unstructured Platform provides two types of workflow builders:
 - [Automatic](#create-an-automatic-workflow) workflows, which use sensible default workflow settings to enable you to get good-quality results faster.
 - [Custom](#create-a-custom-worklow) workflows, which enable you to fine-tune the workflow settings behind the scenes to get very specific results.
 
-All Unstructured accounts can create automatic worklows.
-
-To create custom workflows, you must request Unstructured to enable your account first. [Learn how](#create-a-custom-worklow).
-
 ### Create an automatic workflow
 
 <Warning>
@@ -151,7 +147,7 @@ To create an automatic workflow:
        </Accordion>
    </AccordionGroup>
 
-9. The **Reprocess all** box applies only to the Amazon S3 and Azure Blob Storage source connectors:
+9. The **Reprocess all** box applies only to blob storage connectors such as the Amazon S3, Azure Blob Storage, and Google Cloud Storage connectors:
 
    - Checking this box reprocesses all documents in the source location on every workflow run.
    - Unchecking this box causes only new documents that are added to the source location since the last workflow run to be processed on future runs. Previously processed documents are not processed again, even if those documents' contents change.
@@ -172,168 +168,9 @@ To create an automatic workflow:
     To see your existing connectors, on the sidebar, click **Connectors**, and then click **Sources** or **Destinations**.
 </Warning>
 
-There are two ways to create a custom workflow:
-
-- Through [Build it with me > Custom](#build-it-with-me-custom). This option enables you to fine-tune the kinds of settings that are in **Basic**, **Advanced**, and **Platinum**.
-- Through [Build it myself](#build-it-myself). This option offers a visual workflow designer with even more fine-tuning than the **Custom** option.  
-
-#### Build it with me - Custom
-
-1. On the sidebar, click **Workflows**.
-2. Click **New Workflow**.
-3. Next to **Build it with me**, click **Create Workflow**.
-
-   <Note>If a radio button appears instead of **Build it with me**, select it, and then click **Continue**.</Note>
-
-4. For **Workflow Name**, enter some unique name for this workflow.
-5. In the **Sources** dropdown list, select your source location.
-6. In the **Destinations** dropdown list, select your destination location.
-
-   <Note>You can select multiple source and destination locations. Files will be ingested from all of the selected source locations, and the processed data will be delivered to all of the selected destination locations.</Note>
-
-7. Click **Continue**.
-8. In the **Optimize for** section, click the **Custom** option, and then click **Continue**.
-
-   <Note>
-      If the **Custom** option is disabled, inside the **Custom** option click **Notify me**, and follow the on-screen directions to complete the request. 
-      Unstructured will notify you when your account has been enabled with the **Custom** option. After you receive this notification, click the 
-      **Custom** option, and then click **Continue**.
-   </Note>
-
-9. In the **Strategy** area, choose one of the following:
-
-    - **Fast**: Ideal for simple, text-only documents.
-    - **High Res**: Best for PDFs, images, and complex file types.
-
-      <Note>
-          During **High Res** processing, any detected text-based files are processed and billed at the **Fast** rate instead.
-      </Note>
-
-    - **VLM**: For your most challenging documents, including scanned and handwritten content.
-
-      You must also choose a VLM provider and model. Available choices include:
-
-      - **Anthropic**: **Claude 3.5 Sonnet**
-      - **OpenAI**: **GPT-4o**
-
-      <Note>
-          During **VLM** processing, any detected files that are not PDFs or images are processed and billed at either the **High Res** or **Fast** rate instead. 
-          Of those non-PDF and non-image files, all text-based files are processed and billed at the **Fast** rate instead. The other files are processed and billed at the **High Res** rate instead.
-      
-          When you use the **VLM** strategy with embeddings for PDF files of 200 or more pages, you might notice some errors when 
-          these files are processed. These errors typically occur when these larger PDF files have lots of tables and high-resolution images.
-      </Note>
-
-    [Learn more](/platform/partitioning).
-
-10. In the **Image Summzarizer** drop-down list, choose one of the following:
-
-    - **None**: Do not provide summaries for any detected images in any of the files.
-    - **OpenAI GPT-4o Image Description**: Use GPT-4o to provide summaries for any detected images in any of the files. [Learn more](https://openai.com/index/hello-gpt-4o/).
-    - **Claude 3.5 Sonnet Image Description**: Use Claude 3.5 Sonnet to provide summaries for any detected images in any of the files. [Learn more](https://www.anthropic.com/news/claude-3-5-sonnet).
-
-    [Learn more](/platform/summarizing).
-
-11. In the **Table Summzarizer** drop-down list, choose one of the following:
-
-    - **None**: Do not provide summaries for any detected tables in any of the files.
-    - **OpenAI GPT-4o Table Description**: Use GPT-4o to provide summaries for any detected tables in any of the files. [Learn more](https://openai.com/index/hello-gpt-4o/).
-    - **OpenAI GPT-4o Table to HTML**: Use GPT-4o to convert any detected tables to HTML format. [Learn more](https://openai.com/index/hello-gpt-4o/).
-    - **Claude 3.5 Sonnet Table Description**: Use Claude 3.5 Sonnet to provide summaries for any detected tables in any of the files. [Learn more](https://www.anthropic.com/news/claude-3-5-sonnet).
-
-    [Learn more](/platform/summarizing).
-
-12. Check the **Include Page Breaks** box to include page breaks in the output, if the file type support it.
-13. Check the **Infer Table Structure** box to extract any detected table elements in PDF files as HTML format into a `metadata` output field named `text_as_html`.
-
-14. In the **Elements to Exclude** drop-down list, select any element types to exclude from the output.
-15. In the **Chunk** area, for **Chunker Type**, select one of the following:
-
-    - **None**: Do not apply special chunking rules to the output.
-    - **Chunk by Character** (also known as _basic_ chunking): Combine sequential elements to maximally fill each chunk. Also, specify the following:
-
-      - **Include Original Elements**: Check this box to output the elements that were used to form a chunk, to appear in the `metadata` field's `orig_elements` field for that chunk. By default, this box is unchecked.
-      - **Max Characters**: Cut off new sections after reaching a length of this many characters. The default is **2048**.
-      - **New After n chars**: Cut off new sections after reaching a length of this many characters. This is an approximate limit. The default is **1500**.
-      - **Overlap**: Apply a prefix of this many trailing characters from the prior text-split chunk to second and later chunks formed from oversized elements by text-splitting. The default is **160**.
-      - **Overlap all**: Check this box to apply overlap to "normal" chunks formed by combining whole elements. Use with caution as this can introduce noise into otherwise clean semantic units. By default, this box is unchecked.
-        
-    - **Chunk by Page**: Preserve page boundaries. When a new page is detected, the existing chunk is closed and a new one is started, even if the next element would fit in the prior chunk. Also, specify the following:
-        
-      - **Include Original Elements**: Check this box to output the elements that were used to form a chunk, to appear in the `metadata` field's `orig_elements` field for that chunk. By default, this box is unchecked.
-      - **Max Characters**: Cut off new sections after reaching a length of this many characters. This is a strict limit. The default is **500**.
-      - **New After n Characters**: Cut off new sections after reaching a length of this many characters. This is an approximate limit. The default is **50**.
-      - **Overlap**: Apply a prefix of this many trailing characters from the prior text-split chunk to second and later chunks formed from oversized elements by text-splitting. The default is **30**.
-      - **Overlap all**: Check this box to apply overlap to "normal" chunks formed by combining whole elements. Use with caution as this can introduce noise into otherwise clean semantic units. By default, this box is unchecked.
-
-    - **Chunk by Title**: Preserve section boundaries and optionally page boundaries as well. A single chunk will never contain text that occurred in two different sections. When a new section starts, the existing chunk is closed and a new one is started, even if the next element would fit in the prior chunk. Also, specify the following:
-    
-      - **Combine Text Under n Chars**: Combine elements until a section reaches a length of this many characters. The default is **0**.
-      - **Include Original Elements**: Check this box to output the elements that were used to form a chunk, to appear in the `metadata` field's `orig_elements` field for that chunk. By default, this box is unchecked.
-      - **Max Characters**: Cut off new sections after reaching a length of this many characters. This is a strict limit. The default is **2048**.
-      - **Multipage Sections**: Check this box to allow sections to span multiple pages. By default, this box is unchecked.
-      - **New After n Characters**: Cut off new sections after reaching a length of this many characters. This is an approximate limit. The default is **1500*.
-      - **Overlap**: Apply a prefix of this many trailing characters from the prior text-split chunk to second and later chunks formed from oversized elements by text-splitting. The default is **160**.
-      - **Overlap all**: Check this box to apply overlap to "normal" chunks formed by combining whole elements. Use with caution as this can introduce noise into otherwise clean semantic units. By default, this box is unchecked.
-
-    - **Chunk by Similarity**: Use the [sentence-transformers/multi-qa-mpnet-base-dot-v1](https://huggingface.co/sentence-transformers/multi-qa-mpnet-base-dot-v1) embedding model to identify topically similar sequential elements and combine them into chunks. Also, specify the following:
-
-      - **Include Original Elements**: Check this box to output the elements that were used to form a chunk, to appear in the `metadata` field's `orig_elements` field for that chunk. By default, this box is unchecked.
-      - **Max Characters**: Cut off new sections after reaching a length of this many characters. This is a strict limit. The default is **500**.
-      - **Similarity Threshold**: Specify a threshold between 0 and 1 exclusive (0.01 to 0.99 inclusive), where 0 indicates completely dissimilar vectors and 1 indicates identical vectors, taking into consider the trade-offs between precision (a higher threshold) and recall (a lower threshold). The default is **0.5**. [Learn more](https://towardsdatascience.com/introduction-to-embedding-clustering-and-similarity-11dd80b00061).
-
-    Learn more:
-        
-    - [Chunking overview](/platform/chunking)
-    - [Chunking for RAG: best practices](https://unstructured.io/blog/chunking-for-rag-best-practices)
-
-16. In the **Embed** area, for **Provider**, choose one of the following:
-
-    - **None**: Do not generate embeddings.
-    - **Azure OpenAI**: Use Azure OpenAI to generate embeddings. Also, choose the model to use:
-
-      - **text-embedding-3-small**, with 1536 dimensions.
-      - **text-embedding-3-large**, with 3072 dimensions.
-      - **Ada 002 (Text)** (`text-embedding-ada-002`), with 1536 dimensions.
-
-      [Learn more](https://learn.microsoft.com/azure/ai-services/openai/concepts/models#embeddings).
-
-    - **TogetherAI**: Use TogetherAI to generate embeddings. Also, choose the model to use:
-
-      - **M2-BERT-80M-2K-Retrieval**, with 768 dimensions.
-      - **M2-BERT-80M-8K-Retrieval**, with 768 dimensions.
-      - **M2-BERT-80M-32K-Retrieval**, with 768 dimensions.
-      
-      [Learn more](https://docs.together.ai/docs/serverless-models#embedding-models).
-
-    Learn more:
-        
-    - [Embedding overview](/platform/embedding)
-    - [Understanding embedding models: make an informed choice for your RAG](https://unstructured.io/blog/understanding-embedding-models-make-an-informed-choice-for-your-rag).
-
-17. The **Reprocess all** box applies only to the Amazon S3 and Azure Blob Storage source connectors:
-
-    - Checking this box reprocesses all documents in the source location on every workflow run.
-    - Unchecking this box causes new documents that have been added to the source location, as well as existing documents in the source location that have had their contents or titles changed, since the last workflow run to be processed on future runs. Other previously processed documents are not processed again.
-
-18. Check the **Retry Failed Documents** box if you want to retry processing any documents that failed to process. 
-19. Click **Continue**.
-20. If you want this workflow to run on a schedule, in the **Repeat Run** dropdown list, select one of the scheduling options, and fill in the scheduling settings. Otherwise, select **Don't repeat**.
-21. Click **Complete**.
-22. If you did not set the workflow to run on a schedule, you can [run the worklow](#edit-delete-or-run-a-workflow) now.
-
-#### Build it myself
-
 1. On the sidebar, click **Workflows**.
 2. Click **New Workflow**.
 3. Click the **Build it myself** option, and then click **Continue**.
-
-   <Note>
-      If the **Build it myself** option is disabled, inside the **Build it myself** option click **Notify me**, and follow the on-screen directions to complete the request. 
-      Unstructured will notify you when your account has been enabled with the **Build it myself** option. After you receive this notification, click the 
-      **Build it myself** option, and then click **Continue**.
-   </Note>
-
 4. In the **This workflow** pane, click the **Details** button.
 
    ![Workflow details](/img/platform/Workflow-Details.png)
@@ -342,7 +179,7 @@ There are two ways to create a custom workflow:
 6. If you want this workflow to run on a schedule, click the **Schedule** button. In the **Repeat Run** dropdown list, select one of the scheduling options, and fill in the scheduling settings.
 7. To overwrite any previously processed files, or to retry any documents that fail to process, click the **Settings** button, and check either or both of the boxes.
 
-   The **Reprocess all** box applies only to the Amazon S3 and Azure Blob Storage source connectors:
+   The **Reprocess all** box applies only to blob storage connectors such as the Amazon S3, Azure Blob Storage, and Google Cloud Storage connectors:
 
    - Checking this box reprocesses all documents in the source location on every workflow run.
    - Unchecking this box causes new documents that have been added to the source location, as well as existing documents in the source location that have had their contents or titles changed, since the last workflow run to be processed on future runs. Other previously processed documents are not processed again.

snippets/quickstarts/platform.mdx

@@ -104,7 +104,7 @@ allowfullscreen
                 these files are processed. These errors typically occur when these larger PDF files have lots of tables and high-resolution images.
               </Note>
 
-        9. The **Reprocess all** box applies only to the Amazon S3 and Azure Blob Storage source connectors:
+        9. The **Reprocess all** box applies only to blob storage connectors such as the Amazon S3, Azure Blob Storage, and Google Cloud Storage connectors:
 
            - Checking this box reprocesses all documents in the source location on every workflow run.
            - Unchecking this box causes new documents that have been added to the source location, as well as existing documents in the source location that have had their contents or titles changed, since the last workflow run to be processed on future runs. Other previously processed documents are not processed again.