sachskaylee / helios Goto Github PK

Rich Text Editor on iOS is broken -> Format Buttons don't work.

Add a way to create a custom menu. (e.g. links, ...)
I initially hoped to get away without this feature, but this is a bit too essential to exclude.

A bug is currently preventing users from uploading new avatars. Regular file upload for e.g. posts and pages is not affected.

As of now, the API has a session state for logging in and out. As we aspire to create a proper RESTful API this is not good.

Instead we should use an authorization header which is submitted for every request. This might even allow us to completely eliminate the use of cookies.

:)

Add a way to directly select a theme from bulmaswatch to use for helios without having to manually edit a sass file.

A CMS is nice, but without a proper way to create pages aside from blog posts it isn't too useful.

We need to properly plan this feature, but I think that creating a stable API has priority as this is a major feature addition.

We need to be able to drag and drop files into the form file upload.

kek

Add Tags to posts and allow to filter by them.

Currently parameterized routes can only be rendered using SSR. This is not optimal and can be disruptive for UX.
We probably wish to use a library for this task.

Support adding an image as website banner instead of just text.

This should be tied to #36

Logging is all over the place at the moment.

Some uses a third party library, others console.log and some just writes to stdout.

We need a unified solution that integrates as well as possible into other systems.

It's not a fun experience.

Interestingly enough the page works perfectly in IE with JavaScript disabled, but not while enabled.

Allow users to upload media to Helios and embed it through the editor itself.

This is confusing testers.

Next.js has announced official AMP support. It would be a shame not to implement this into Helios.

Currently the full post is displayed both on the profile and the user about page. Especially for the latter this might be too long.

We need to insert a "Read more..." link after a certain configurable length.

This is due to greenlock-express (the underlying library we use to generate SSL certificates) does not support binding to IP addresses, and does not plan on doing so(https://git.coolaj86.com/coolaj86/greenlock-express.js/issues/26). Until a replacement can be found you'll need to NAT traffic if you want to run more than one website on the same machine.

It would be awesome if users could add comments to posts, displaying the user name of the commenter.

Don't have multiple systems for uploading file. Combine them all into one central system.

This will also require us to add some user based folders.

If you let Helios run on e.g. Port 8080 and 8443 and then NAT incoming trraffic from 80 and 443 to it its canonical URLs(<link rel="canonical" /> in the source) still have Port 8080 and 8443 in them.
This did not seem to cause any bugs but definetly is suboptimal behaviour.

Print some warnings about potential configuration errors, etc...

We currently use react-addons-text-content to extract the text of React nodes. This does not work well with nested nodes.

Figure out a better way to extract strings from React components, as this would allow us to actually have a title in our app. Wow.

Images are a rather essential part of blogging and website editing. So we need image support in the editor.

We currently store them in a file. This is bad for twelve factor apps. Since we intend to fully support Docker one day we musts move away from this.

For Example Plesk -> WIll help you with this one :)

When logged in as a user the user may not see all menu points they are allowed to use. This does not occur for the admin.

This also requires us to consider how to save users: Always lower case them? Respect case but check for duplicates by ignoring case?

As of now we only support either no HTTPS or HTTPS via Let's Encrypt. The founding for custom certificates in already there, but there is no user facing way to embed them.

We have a foundation for a Docker image, but it is dated, most likely broken and was crafted in a hurry.

Columns have to be filled with content, or they fail to render.

There has been a request to add password protected files/posts/pages to Helios.

This feature will be implemented in a later version.

Font Awesome has some strange issues from time to time. Sometimes the icons are rendered as question marks and we get an error message related to React hydration.

This is probably due to SSR. Investigate this further and fix it, or use a different icon library.

We need more components than just Card and Columns for the initial release.

Plans:

• ☑ Card
• ☑ Hero
• ☑ Code Editor
• ☑ Columns