4 ms·

With better support mobile devices (including eReaders and whatever comes after them), we hope it'll be less of an issue as time goes on. Right now, we simply

With better support mobile devices (including eReaders and whatever comes after them), we hope it'll be less of an issue as time goes on. Right now, we simply export the Markdown to flat text (breadth-first). But we will be adding PDF export options, for exporting the whole document, or one column. That way, you can still end up with a traditional document at the end, if you want. Any other ideas?

6d0debc071 13y ago
Have the breadth as a summary page perhaps? Like when you open a book and it's effectively the list of chapters. Then have the 2l tiers as your chapters and the 3l tiers as the subheadings in those chapters? Don't know whether that's what you're doing at the moment :)
marcamillion 13y ago
I think you may be overthinking it. If you just created a document with each hierarchy organized properly, I think you should be fine. E.g. you create say 3 heading sizes in Word. 24px, 20px, 16px. Then for the main point, i.e. the content in the left-most column, you put those under a heading that is under the 24px - then any sub content from the 2nd column would go under a 20px heading that is under the first 24px heading and so on. So there is a chronological order of the content. I think that's all you need. Proper placement of the content under the right headings, make the headings different sizes and you make sure it flows like the author intended (which I think you can ensure by using the order they setup on your site). That's just my $0.02.
- adriano_f 13y ago
  I love overthinking things! It's true that if every card had a title, then import and export while maintaining the tree structure would be easy. But as it stands, if you have the following cards: A A.1 A.2 B this approach wouldn't be able to maintain the structure if the cards didn't have titles (it would just list all these as A, A.1, A.2, B). It's for this reason alone that we've considered making titles required for at least the first card in a group. Or am I overthinking again... ?
  - marcamillion 13y ago
    You could enforce it like that - i.e. require all cards to have titles. But I don't think you NEED to. I would assume that the way you know the order of the cards, is that you have some unique ID on the flow of the cards, no? E.g. You know that A is first, then A.1, then A.2, then B. So all you do is when you are exporting to PDF, you put the sections/cards in that order. I think that should suffice, or am I missing something?

6d0debc071 13y ago

Have the breadth as a summary page perhaps? Like when you open a book and it's effectively the list of chapters. Then have the 2l tiers as your chapters and the 3l tiers as the subheadings in those chapters? Don't know whether that's what you're doing at the moment :)

marcamillion 13y ago

I think you may be overthinking it. If you just created a document with each hierarchy organized properly, I think you should be fine. E.g. you create say 3 heading sizes in Word. 24px, 20px, 16px. Then for the main point, i.e. the content in the left-most column, you put those under a heading that is under the 24px - then any sub content from the 2nd column would go under a 20px heading that is under the first 24px heading and so on. So there is a chronological order of the content. I think that's all you need. Proper placement of the content under the right headings, make the headings different sizes and you make sure it flows like the author intended (which I think you can ensure by using the order they setup on your site). That's just my $0.02.

adriano_f 13y ago
I love overthinking things! It's true that if every card had a title, then import and export while maintaining the tree structure would be easy. But as it stands, if you have the following cards: A A.1 A.2 B this approach wouldn't be able to maintain the structure if the cards didn't have titles (it would just list all these as A, A.1, A.2, B). It's for this reason alone that we've considered making titles required for at least the first card in a group. Or am I overthinking again... ?
- marcamillion 13y ago
  You could enforce it like that - i.e. require all cards to have titles. But I don't think you NEED to. I would assume that the way you know the order of the cards, is that you have some unique ID on the flow of the cards, no? E.g. You know that A is first, then A.1, then A.2, then B. So all you do is when you are exporting to PDF, you put the sections/cards in that order. I think that should suffice, or am I missing something?