Closed MattIPv4 closed 6 years ago
Other than raising ls.terminal.ink out from the grave, I don't have a good way of getting Jekyll to do this. I could get Node.js to split the files, but it diverges from the "Use Jekyll only" philosophy...
But at this point, I might as well.
Node is an option, as discussed in Discord, it might be possible to populate the api/bots directory with the bot json files during the build process which would allow the whole Jekyll only mantra to stay.
Might also use Discord_Fork as a way to add projects, for a real backend that does everything
I'm currently attempting to attack this using Jekyll itself, by using Ruby plugins
im kinda retarded at jekyll's ruby tho, so please excuse the crud
I've got some output!
{
"draft": false,
"categories": [
],
"layout": "item",
"type": "bots",
"lang": "en",
"primary_key": "client_id",
"client_id": "134133271750639616",
"application_id": "170237838334492682",
"pagename": "blargbot",
"description": "A multipurpose discord bot - Moderation and Fun!",
"avatar": "https://cdn.discordapp.com/avatars/134133271750639616/1a7e28c9bf7a69475b7928226ca70a40.png",
"link": "https://invite.blargbot.xyz",
"prefix": "b!",
"title": "134133271750639616",
"slug": "134133271750639616",
"ext": ".md",
"tags": [
],
"excerpt": "<iframe src=\"https://blargbot.xyz/\" class=\"ls-iframe\">\n<!--\nThis data was imported from ls.terminal.ink\n-->\n</iframe>\n",
"permalink": "/bots/134133271750639616/"
}
Looks pretty sweet.
Is there any reason that the invite is called link
and not invite
?
It's an agnostic term which applies to both bots and servers
Invite would also work for both 🤔 and is probably more descriptive
It's also the term that's already in all .yml
files
Ah okay fair enough then. Other than that, looks absolutely great.
It would be nice if there was an endpoint similar to api/bots/all.json but for each individual bot. Eg. api/bots/:id.json
Thanks.