Manual editing of file names

[imhalid]

I connected the repository generated with Lumen to my blog site, effectively turning it into an online CMS. However, there is an issue: the file names appear to be generated based on timestamps. Since I use the file name as the slug, this causes some problems on my end.

I believe it would be better if the file name could be set manually or customized. What do you think?

thinking....

I haven’t reviewed the code yet, but I’ll take a look at how this could be implemented. A few potential concerns came to mind, although I’m not certain about them.

For example, would renaming the generated file later cause any issues?

• We could require the user to enter a file name at the beginning, but that might not be ideal from a UX perspective.

• Another option would be to add a setting that allows users to choose between manual and automatic file name generation. However, this could create confusion for new users.

• Alternatively, after creating the file and writing its content, we could prompt the user to choose a file name right before saving. That might be more efficient than asking at the beginning, since the context would be clearer.

• The title entered in the properties (if made mandatory) could automatically be converted into the file name. This seems more efficient, but resolving issue Property editor #449 would likely be necessary for this approach.

edit: Ah, I just realized this issue was already opened #346 by @colebemis. I hadn’t noticed it before. Sorry about that.

[Muhammad-Aqib-Bashir]

This is a great idea, and allowing users to rename files is excellent. From a UI/UX perspective, I suggest having a setting that lets users choose whether to be prompted to name note files on the first save. This option should be enabled by default. When enabled, the user will be asked to provide a name for the note. If disabled, the system will automatically use the note’s title as the file name (or timestamp), and if there is no title, it will fall back to using a timestamp or the first few lines of the note.

For renaming after the note is created, we can allow the user to double-click the file name, which would convert it into an editable field (e.g., [ old-name ].md) displayed at the top-left (where the name of the file appear). The user can then edit it directly, and the change will update the file name without disrupting the interface.

However, introducing a renaming feature could potentially affect the Git repository structure?

[colebemis]

This is already possible. Check out the ... menu:

[Muhammad-Aqib-Bashir]

Okay, thanks, @colebemis. I was working on renaming that way; it can be undone.

Recording.2026-02-14.095238.mp4

Also implemented a settings option to prompt for a file name on first save. What do you think about that?

[colebemis]

@Muhammad-Aqib-Bashir Nice, I like the inline editing. That's cool!

Not a fan of adding a setting. Changing the file name should be easy but I don't think we need a prompt for it.

[Muhammad-Aqib-Bashir]

@Muhammad-Aqib-Bashir Nice, I like the inline editing. That's cool!

Not a fan of adding a setting. Changing the file name should be easy but I don't think we need a prompt for it.

Thank you for the appreciation ☺️

The option in Settings will allow users to choose whether the app should prompt for a file name when saving a new note for the first time or automatically use a timestamp as the file name. By default, it will prompt for a file name. If this option is unchecked, the app will skip the prompt and use a timestamp instead.

I was also thinking about adding a function that automatically normalizes file names to kebab-case. This would make the URLs cleaner and more readable, and it would also help keep the repository well organized and consistent.

[colebemis]

I'm don't love additional settings or pop up prompts so I'm leaning against having that as an option. If you can just double click the file name to edit, what's the added benefit of a prompt?

[imhalid]

I don’t think there’s any issue with saving a newly added file using a timestamp or something like “new page.” Being able to rename it inline by clicking on the file name is sufficient for the user, in my opinion. The flow works very well in Notion, for example.