content/devlog/2025.smd

@@ -16,14 +16,6 @@ You can [subscribe to this page via RSS]($link.page('devlog').alternative('rss')
 devlog entries in the [archive](/devlog/).
 
 
-## [configurable file types]($section.id("2025-07-14T18:55:02+02:00"))
-
-You can now modify the configuration of file types. There is a new command `Edit file type
-configuration` that will open a config file the defaults for a file type which you can change and
-save. Changes take effect on restart of flow. This means you can finally change your language server
-and formatter configuration and add file extensions without having to build flow yourself.
-
-
 ## [improved backtraces for segfaults]($section.id("2025-07-01T20:00:00+02:00"))
 
 I've cloned the std.debug segfault signal handlers and added the ability to reset the terminal

content/index.smd

@@ -132,13 +132,6 @@ Configuration is mostly dynamically maintained with various commands in the UI.
 It is stored under the standard user configuration path. Usually `~/.config/flow`
 on Linux. %APPDATA%\Roaming\flow on Windows.
 
-There are commands to open the various configuration files, so you don't have to
-manually find them. Look for commands starting with `Edit` in the command palette.
-
-File types may be configured with the `Edit file type configuration` command. You
-can also create a new file type by adding a new `.conf` file to the `file_type`
-directory. Have a look at an existing file type to see what options are available.
-
 Logs, traces and per-project most recently used file lists are stored in the
 standard user application state directory. Usually `~/.local/state/flow` on
 Linux and %APPDATA%\Roaming\flow on Windows.