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
I feel like the setup right now is... tedious to say the least.
Having to edit a JS file is not only annoying, but also difficult and maybe confusing if you're not having too much knowledge of JS (like I do).
Personally, I feel like it could be more user-intuitive to have the different entries split up into their own Markdown files inside a dedicated folder.
Through that would it allow a more easy to understand setup (Create a new file with content) while still allowing configuration through stuff like the markdown frontmatter.
To give an example, this JS entry...
constentries=[{id: 'cat',categories: ['cat'],color: 'green',faicon: 'cat',datetime: '2021-01-01 05:00',title: 'Cats are very good',image: {link: 'http://placekitten.com',src: 'http://placekitten.com/200/300',alt: 'A placeholder kitten',caption: 'Kitten!',},body: "The best thing in the universe is a cardboard box. Chirp at birds catasstrophe for meowwww for hiding behind the couch until lured out by a feathery toy for morning beauty routine of licking self sugar, my siamese, stalks me (in a good way), day and night lick the other cats. Pushed the mug off the table shove bum in owner's face like camera lens or tickle my belly at your own peril i will pester for food when you're in the kitchen even if it's salad and grass smells good, licks your face, but hiiiiiiiiii feed me now.",links: [{href: 'https://en.wikipedia.org/wiki/Cat',linkText: 'Cat',},],}]
...would become this Markdown file:
---id: 'cat'categories:
- 'cat'color: 'green'faicon: 'cat'datetime: '2021-01-01 05:00'title: 'Cats are very good'image:
link: 'https://placekitten.com'source: 'https://placekitten.com/200/300'alt: 'A placeholder kitten'caption: 'Kitten!'links:
- href: 'https://en.wikipedia.org/wiki/Cat'linkText: 'Cat'---
The best thing in the universe is a cardboard box. Chirp at birds catasstrophe for meowwww for hiding behind the couch until lured out by a feathery toy for morning beauty routine of licking self sugar, my siamese, stalks me (in a good way), day and night lick the other cats. Pushed the mug off the table shove bum in owner's face like camera lens or tickle my belly at your own peril i will pester for food when you're in the kitchen even if it's salad and grass smells good, licks your face, but hiiiiiiiiii feed me now.
I know this would most likely be a lot of work (Especially creating the tree by reading the date/datetime values of the files) to realize, but I believe it would be a good change as it improves user-experience and makes the software more accessible for less experienced people in the end.
Perhaps, if some markdown parses is used could it even eliminate some stuff like the links thing, by having embedded links used in the body itself.
I hope you think about this idea.
The text was updated successfully, but these errors were encountered:
I feel like the setup right now is... tedious to say the least.
Having to edit a JS file is not only annoying, but also difficult and maybe confusing if you're not having too much knowledge of JS (like I do).
Personally, I feel like it could be more user-intuitive to have the different entries split up into their own Markdown files inside a dedicated folder.
Through that would it allow a more easy to understand setup (Create a new file with content) while still allowing configuration through stuff like the markdown frontmatter.
To give an example, this JS entry...
...would become this Markdown file:
I know this would most likely be a lot of work (Especially creating the tree by reading the date/datetime values of the files) to realize, but I believe it would be a good change as it improves user-experience and makes the software more accessible for less experienced people in the end.
Perhaps, if some markdown parses is used could it even eliminate some stuff like the links thing, by having embedded links used in the body itself.
I hope you think about this idea.
The text was updated successfully, but these errors were encountered: