Hi Tobias
Great work on all the themes. > Thanks :) See, as I said, there are no documentation or guidelines regarding such a effort. So rather than telling me looks are not everything, may be we should discuss what functionality should be part of such endeavours. Do you have any intentions of starting from a more barebones "edition" / > theme? No that pagination ...is it static? ...did you define it by hand? > > would there be an index page for each tag? I will answer both these together. As you can see from the roadmap I laid out here <https://ibnishak.github.io/t-blog/Documentation/Roadmap.html>, category indexes are next in line to be added. Here are the issues I face and how I intend to possibly tackle it. A blog post need only be rendered once. Even if you have a 100 blog-posts, they need not be rendered over and over again, only the changed or modified ones. I have actually set a limit of last 10 changed posts to be rendered when a build command is given. Indexes on the other hand must be rendered continuously. All indexes. I can actually code for an index page to be created as an when the user adds a new tag automatically. But when the blog grows into a 50 something tags, it would mean a great delay in every time user gives a build command. There are two ways it can be taken further from here - One is to filter out all the tags of last 10 modified posts and re-render the corresponding index pages for those tags only. - The other is to let user define if they need an index page for that tag at all. If they do, they create an empty tiddler with a "system tag" and mention the tag to be indexed in the text field. This way the end user has more control. As for the main index pages, I have not yet figured out a way to let the user define how many pages they should have. The problem is, the first page of index is coded as "sort all the blog posts by modification date and show the first 10". The second page becomes "sort all the blog posts by modification date, discard the first 10 and show the next 10". The third will discard the first 20 and so on. The thing is, I do not know a way in the core to increment the "discard" element. The pagination is something that should be taken apart and coded differently. However this would mean index pages must be somehow identifiable from the rest. I have not yet reached a decision as what will separate the index pages from the rest. The "next page" button will show up in all but last and the "last page" button showing up in all but first. Now this part is simple, but before that, the last issue must be tackled first. Sometimes, it also appears that links are not working, e.g. I saw some link > to "TiddlyWiki" ...but it didn't open anything > That comment would have been more useful had you pointed out where is that link. The tag links and author links are not yet defined a target yet. They are left to user to define. They can create a page using blog/misc type and define that target to the modifier link. Say I wanted to create a fancy menu component, a component that > conditionally shows things depending on how a page is tagged, etc... how > would I be doing that? Would that go into that index or blog post template? > I would say if one has enough knowledge of TW5 to create a fancy component, he can probably edit the post template and create a conditional filter to show it depending on the tag of the current post. A blog's gotta work well from a functional perspective No arguments there. But historically neither has a product been appealed to masses by looking ugly. I am trying to bring in visual choices and possibly making it possible to a commoner to use the static page functionality with least minimum knowledge as possible. Even then I would object to categorising it as merely an attempt to look nice. As I said, such a endeavour, if anyone takes it further, would benefit with a set of best practices. Riz -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/2fd4b0a2-b0f1-4e9c-b244-6525ee49ca6f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
