Issue with Asset Referencing in Markdown Files Upon Upload

[greiner-marcus-auticon]

Description:

When uploading a markdown file that includes pictures or other assets, the assets are initially placed in a root folder (e.g., Public), while the markdown file itself is placed in a subfolder (e.g., Public/mymarkdown/mymarkdown.md). This causes issues with referencing the assets correctly from the markdown file.

Steps to Reproduce:

1. Upload a markdown file (mymarkdown.md) that includes pictures or other assets.
2. Observe that the assets are placed in the Public folder.
3. Notice that the markdown file is placed in the Public/mymarkdown/ folder.
4. Attempt to reference the assets from the markdown file.

Expected Behavior:
The markdown file should be able to reference the assets correctly even if they are placed in a different folder (e.g., Public/assets).

Actual Behavior:
The markdown file cannot correctly reference the assets because they are placed in different directories.

Proposed Solution:
Implement a mechanism that allows markdown files to correctly reference assets regardless of their placement. One possible approach is to configure the upload process to place assets in a designated folder (e.g., Public/assets) and update the markdown references accordingly.

Example:

• Markdown file location: Public/mymarkdown/mymarkdown.md
• Asset location: Public/assets
• Markdown reference should be updated to: ![image](../assets/image.png)

Additional Context:
This issue affects the organization and accessibility of markdown files and their associated assets. Ensuring correct referencing will improve file management and user experience.

Environment:

• Version: [Specify the version of the application]
• OS: [Specify the operating system]
• Browser: [Specify the browser, if applicable]

Screenshots:
If applicable, add screenshots to help explain your problem.

Labels:

• Bug
• Documentation

Assignees:

Priority:
Medium