Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

For borrowing ideas #12

Open
alexjj opened this issue Nov 28, 2021 · 2 comments
Open

For borrowing ideas #12

alexjj opened this issue Nov 28, 2021 · 2 comments

Comments

@alexjj
Copy link

alexjj commented Nov 28, 2021

Firstly, very nice theme and well put together. First time I’ve seen one that has a dedicated section for daily journal entries. I think that’s a great differentiator and something 99% of blog themes ignore. I’ve been playing around with journal.txt and if that can be integrated into a blog. I have it working and it’s nice just typing into a single txt, committing it and having Github actions build the posts and github pages host it. However, journaltxt doesn’t have many configuration options.

I noticed you talk about integration with Obsidian and I’d also found this theme. Likely you may have too but there could be some good stuff in for helping enjoyment-work along.

@brennanbrown
Copy link
Owner

Thank you for the feedback @alexjj ! That's a really cool project and I really appreciate you sharing that! I'm going to try it out myself.

It's a very interesting idea, and I'd have to think for awhile for a way to implement a "monofile" in Jekyll like that. You could absolutely do something like that manually, but it would all be displayed on a single page, since Jekyll generates a page for each file.

I'm not entirely sure if this could be overridden, and instead have a sort of "separator character" within the file be the determinant for the page generation.

I also worry about how it would affect performance. I have an actual Jekyll blog here: https://github.com/brennanbrown/journalbar/tree/master/_posts As you can see, it's a lot of posts! Having around 33,000 words in a single text file be parsed from a single file could be slow. And if you're using a text-editor instead of the command line it'd get a little slow on performance editing as well.

I'm definitely not against the idea though, and I apologize but I haven't been as active as I should have in the development of this project!

@alexjj
Copy link
Author

alexjj commented Nov 28, 2021

The app only generates entries for content in the journal.txt file, so you can split it up by year or month if performance becomes an issue. All the previous entries won’t be touched. I don’t like how journal.txt names the journal entries but something that can be managed.

I’m not 100% sure about it but I would like to minimise the friction to writing. Perhaps that can come from using obsidian or loqseq etc. but then you’re reliant on them. I’m drawn to a simple text file as then I can use multiple programs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants