Neocities.org
Thricegreat's Webpage
248,465 views
65 followers
4,292 updates
0 tips
Using the neocities API, you can automatically generate what HTML you need for your index. You may do so by naming your posts in a way that they are naturally sorted in the correct order, request a listing of all your files from the neocities API, then generate HTML for all files in that output that match your naming pattern, that which you then upload back to neocities.org as index.html.
3 likes
Regarding naming scheme, sorting by date has been most practical for me. Naming files YEAR-MM-DD naturally sorts them oldest to newest, and when the output is reversed it is then newest to oldest. For that reversing, I use busybox's `sort -r`.
Given that you seem to dislike writing HTML, I think that running a single command would be a nicer experience than writing out another a tag and a br every time you write something new.
Thanks. But the problem is that I constantly change old posts. And I don't want to change the date.
Have you tried https://github.com/sunainapai/makesite in which you can declare the blog entry’s date?
>>zinportal That's too much. kaa recommended the API, because it is just an URL.
I thought about this again. The main problem is about the data structure. At the surface, I'm using a data structure similar to a blockchain. Instead of a linked list, I use an array though.
A file content may change. But a (file, title) pair will not. It is ordered by date. I only add a pair, and don' t do another operation.
By this, I don't need to consider another operation. I only need to add. And I can easily add by simply writing "(a href=$file)$date $title(/a)(br)".
However, suppose that I start to sort. Then I need to change the data structure. It will have another operation. Like removing. This will make the problem complex.