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

scalability of 'One post per Org subtree' #428

Closed
gour opened this issue Mar 3, 2021 · 2 comments
Closed

scalability of 'One post per Org subtree' #428

gour opened this issue Mar 3, 2021 · 2 comments

Comments

@gour
Copy link

gour commented Mar 3, 2021

Hello,

I'm about to convert one non-profit site containing few hundred posts containing images to Hugo and wonder how does "One post per Org subtree" scale, iow. do you still recommend it over 'One post per Org file' ?

Sincerely,
Gour

@kaushalmodi
Copy link
Owner

Hello,

I don't have experience with that number of posts. I still use that approach for my internal work blog and it works well, but I have around 50 posts at the moment.

Note that you don't have to strictly pick one of subtree-based or file-based approaches; you can mix both. Example: One Org file containing all the posts for one section or topic of posts, and you may have, say, a dozen sections.

@gour
Copy link
Author

gour commented Mar 3, 2021

I don't have experience with that number of posts. I still use that approach for my internal work blog and it works well, but I have around 50 posts at the moment.

OK.

Note that you don't have to strictly pick one of subtree-based or file-based approaches; you can mix both. Example: One Org file containing all the posts for one section or topic of posts, and you may have, say, a dozen sections.

Yes, that's good idea...maybe I'll try to use one-subtree-per-category and see how it goes. :-)

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