What features would you like to see?

[markseuffert]

Hello everybody out there using Datenstrom Yellow. We are moving towards a 1.0 version and it would be great to collect more ideas. I think the application feels lightweight and fast. Although it is designed for small websites, some people use it with hundreds of pages. What would you like to see? Anything not working or missing that you need? What do you like/dislike?

[schulle4u]

There have been a few ideas on Discord and in previous discussions that might be worth mentioning here again. Installing extensions in the browser has been talked about as a Christmas present for years, right? 😁

We also had a bit more discussion about semantic HTML. Personally, I would like to see default layouts use more semantic HTML elements instead of nesting everything in div elements. Div elements are still useful and even needed for extensions, but the basic structure of a website can be designed just as well with semantic elements such as <header>, <nav>, <main> or <footer>. Of course, there is no reason not to use the existing CSS classes to keep all themes compatible. After all these elements make the code more readable, improve accessibility, and, last but not least, should make it easier to port existing CSS frameworks/themes to Yellow.

[PetersOtto]

I am actually very happy with Yellow. If life were a musical request program, I would wish for three things.

1. at the moment you can only update all or no extensions via the Edit extension. It would be nice if you could make a selection here.

2. at the moment only official extensions can be updated via the update extension. It would be nice if you could also do this with your own extensions.

3. easy organization (replace, move, delete ...) of the media files in the browser would be nice.

😀

[xrat]

I, too, am very happy with Yellow.

Things, hacks and other features I frequently add by changing the code or including them in my personal extension/plugin are:

• Extend Markdown syntax
• Add a keyboard shortcut to edit a page (I use Ctrl-E)
• Add my own custom.css for minor mods of the public Yellow themes I use
• Make TOC collapsible
• Log login fails and successes (in my case to syslog)

One bigger issue I have is related to how Yellow changes filenames and paths of pages. While I understand why Yellow does rename files, it happened to me too often that links broke because pages got renamed without anybody noticing at the time it happened and when it could have been quickly reverted. However, I have not yet come up with a good alternative.

One more specific issue: Does the regex in normaliseToken, i.e. /^[\d\-\_\.]+(.*)$/ need to be so broad? For instance, I couldn't have a page named "2fa" or "2factorauthentication".

[pftnhr]

I would be very happy if the edit panel could be better designed so that I can ensure that all the buttons that are important to me are also accessible in portrait mode on mobile. And maybe an option for inline editing when I'm logged in.

[pftnhr]

I would like to be a little more precise:

By inline editing I mean something like double clicking on a page or post and you can edit the content directly in the page or post without having to click on "Edit" at the top. As it currently stands, it only works well on a computer. If you want to maintain content on a mobile device, it is extremely cumbersome, especially if you want to add images.

And I would be happy if the editor could be customised via a template that is then also located in the 'layouts' directory, for example.

[GiovanniSalmeri]

Yellow 1.0 is great news! I too am very happy with Yellow and actually I use it also for not-so-small sites (Dialegesthai has almost 1200 pages and 60 MB of text) and it works perfectly also for them. Kudos to the developers for the wonderful work!

As regards ideas for anything missing: I think that the core (with the core extensions) is excellent as it is. Perhaps a file manager (see #66 and #130) would be a much welcome complement to Edit for those who prefer to modify a site in their browser instead of using a text editor + FTP.

All the other things that come to my mind belong in the extensions. Perhaps it would be useful to maintain a public list of ideas for new extensions?

[auer-kk]

I would like to see a revised sorting/grouping of pages (by title/tag) that works with special characters like (german) umlauts.
Example: Using shortcuts like [wikipages]/[wikitags] or calling $pages->group(…) right now sorts those umlauts to the end
[Ax, Bx, Cx, Äx]. My expected/wanted sort order would be [Ax, Äx, Bx, Cx] instead.

[Brotkasten-a11y]

A fix for a general issue with markdown parsing would be nice: If you write an email address with a longer domain than 3 charakters like a '.vision' domain (e.g., [email protected]), the markdown extension generates a link like [email protected]ion, leaving the 'ion' part outside the link.