Closed jujubeja closed 2 months ago
It's an Electron app, so any user-facing elements will be convrted to HTML sooner or later, no? I'm not sure what exactly you want to achieve. Maybe it could convert from Gemtext to Markdown, but the Markdown gets converted to HTML down the line anyway for the rendering process. So I think you might as well convert to HTML directly.
Yeah, the markdown in Agregore is also rendered to HTML so that users may actually read it. I don't think this makes sense for the project.
If you dislike the rendering, you could go into the extensions folder and delete the JS files for the renderer which will effectively disable it and have gemini rendered as text. You can also edit the extension to behave however you'd prefer
No, this is a bad thing.
while rendering Gemini pages as HTML might make them more accessible to some users, it can undermine the core principles and advantages of the Gemini protocol.
Markdown
Rendering Gemini pages as Markdown can be a more favorable approach compared to converting them to HTML for several reasons:
Simplicity: Markdown is a lightweight markup language that is easy to read and write. It retains the simplicity of Gemini's design while allowing for basic formatting, making it accessible for users who prefer a straightforward text format.
Preservation of Content: By converting Gemini pages to Markdown, the essential content and structure can be preserved without the complexities and overhead associated with HTML. This helps maintain the original intent of the content.
Cross-Platform Compatibility: Markdown is widely supported across various platforms and applications, making it easier for users to view and edit content without needing specialized software.
Readability: Markdown files are generally more readable in their raw form compared to HTML. This can enhance the user experience, especially for those who prefer to read or edit text directly.
Version Control Friendly: Markdown files are plain text, making them suitable for version control systems like Git. This allows for easier tracking of changes and collaboration on content.
Minimal Overhead: Unlike HTML, which can include a lot of additional code and elements, Markdown keeps the focus on the content itself, resulting in faster loading times and a more efficient browsing experience.