You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As many know, blog post support is where we definitely fall short on erlef.org. There's a lot of history, but the TL;DR is that we created something that is non-dev friendly, further, even if you are a dev it's not a good experience. You must create a new markdown file in the repo, put in your markdown, fire up the app (and all the setup that goes along with that), rinse, wash, repeat. Assets that can be embedded into the post must be added to the repository, etc. Then you must open a PR, then we must do a deployment. This is sub-optimal, especially for a non-developer, and doubly so if you don't have access to the deployment, and must depend on someone to do it for you if you need to make quick change as an example.
We will have more and more dev and non-dev persons needing or wanting to add blog posts to the site and the barrier to entry is simply too high. If the barrier to entry is too high, people will not bother creating a blog post at all.
The components needed to make a simple blogging system are mostly there, but probably need some smoothing out. It may even be some components are sub-optimal for what we want. For example, TUI editor is currently in place, but Quill.js maybe provide a better experience and may be easier to work with in regards to adding additional features (file uploads as an example).
Objective(s)
Discuss and get consensus on creating a project with a budget to get blog support done.
The text was updated successfully, but these errors were encountered:
Background
As many know, blog post support is where we definitely fall short on erlef.org. There's a lot of history, but the TL;DR is that we created something that is non-dev friendly, further, even if you are a dev it's not a good experience. You must create a new markdown file in the repo, put in your markdown, fire up the app (and all the setup that goes along with that), rinse, wash, repeat. Assets that can be embedded into the post must be added to the repository, etc. Then you must open a PR, then we must do a deployment. This is sub-optimal, especially for a non-developer, and doubly so if you don't have access to the deployment, and must depend on someone to do it for you if you need to make quick change as an example.
We will have more and more dev and non-dev persons needing or wanting to add blog posts to the site and the barrier to entry is simply too high. If the barrier to entry is too high, people will not bother creating a blog post at all.
The components needed to make a simple blogging system are mostly there, but probably need some smoothing out. It may even be some components are sub-optimal for what we want. For example, TUI editor is currently in place, but Quill.js maybe provide a better experience and may be easier to work with in regards to adding additional features (file uploads as an example).
Objective(s)
The text was updated successfully, but these errors were encountered: