Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make folder notes be index.html of their folder #110

Open
KosmosisDire opened this issue May 23, 2023 · 5 comments
Open

Make folder notes be index.html of their folder #110

KosmosisDire opened this issue May 23, 2023 · 5 comments
Labels
approved This issue has been approved and will be implemented in the future enhancement New feature or request

Comments

@KosmosisDire
Copy link
Owner

Have an option that would export folder notes as index.html in their folder. this would allow access to them under a folder rather than a .html file which fits the way most people use them: as some kind of overview of the folder as a whole.

For example:

vault/books/books.html

would now have the url:

vault/books/

@KosmosisDire KosmosisDire added the enhancement New feature or request label May 23, 2023
@aubreyz
Copy link

aubreyz commented May 23, 2023

I'd suggest not making too many extraneous things that can be achieved in a more controlled way.
You could easily do this as a user by creating a file "index.md" in whatever relevant folders you choose and then putting a dataview query on that page to query all files in that path.

Otherwise you are going to also have a means of specifying which folders need an index.html because it is not going to be every one.

The much harder (and more important) issue is to have some way to allow the user to specify some sort of top bar or sidebar so that they can actually reach the key tables of content or areas without having the usual explorer.

@aubreyz
Copy link

aubreyz commented May 23, 2023

 ```dataview
 LIST
 WHERE contains(file.folder, this.file.folder)
 ```

@KosmosisDire
Copy link
Owner Author

KosmosisDire commented May 23, 2023

I'd suggest not making too many extraneous things that can be achieved in a more controlled way.

Thanks for the suggestion. This won't necessarily make it into the plugin, but I do want to log possible features so they won't be forgotten.

You could easily do this as a user by creating a file "index.md" in whatever relevant folders you choose and then putting a dataview query on that page to query all files in that path.

You may have misunderstood the feature. This would not create any files, nor would it add any content to those folder notes. Instead this would just change the url in the url bar for already existing folder notes, where a folder note is a note with the same name as it's parent folder. Folder notes are a commonly used organisational method that are supported by many 3rd party plugins.

While the user can choose to name a bunch of files index.md, I want to approch the plugin in a way that provides a feature without the user being required to modify their vault. If I had 30 folder notes (like some people do), I would not want to have to rename all of them to index.md. Additionally, once you have done that it will break a number of other plugins that support folder notes, and it will no longer be clear what the note is, espcially if it is a shared vault. Finally, adding this feature is a very small change to both the codebase and the settings so there would be no downside to adding the feature for anyone.

Otherwise you are going to also have a means of specifying which folders need an index.html because it is not going to be every one.

You do not have to specify which notes are folder notes at all because folder notes are by definition notes with the same name as their parent folder. This feature changes only the folder's URL in the browser bar, so there would be no reason to apply this to only some folder notes. Why would you want some folder notes to be referenced by the .html and some by the folder, that is very inconsistent. If you do want to do that, then you have described a workaround yourself.

Thank you for the feedback, let me know if you have any more thoughts :)

@KosmosisDire
Copy link
Owner Author

@aubreyz The much harder (and more important) issue is to have some way to allow the user to specify some sort of top bar or sidebar so that they can actually reach the key tables of content or areas without having the usual explorer.

I have already fully completed the development of the vault file tree (see #30), so no need to worry about that. It will come out in the next release.

@Regenhardt
Copy link

This could be done using redirects if they are implemented.

@KosmosisDire KosmosisDire added the approved This issue has been approved and will be implemented in the future label Aug 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved This issue has been approved and will be implemented in the future enhancement New feature or request
Projects
Development

No branches or pull requests

3 participants