#📜-doccer
1 messages · Page 1 of 1 (latest)
so poggie
wtf is this
documentation writing
its a very extended joke
jetbrains writerside being their IDE for.. writing documentation
i think im very funny
i just wanted a place to organise it properly
no members ?
bug
hello writerside users, here's the drill
all docs are hosted on vencord.dev and are currently on the feat/docs branch.
all documentation content is put in src/content/docs, written in markdown (take a look at the existing stuff for how to format)
documentation categories can be made by making a small json file in src/content/docCategories if you need, but try to use the existing ones if possible (ask if you aren't sure if something fits!)
open a PR (making sure the base is feat/docs) with your contributions (when merged, this will be different)
we should properly plan it first
plan what the different categories and topics will be
ye that's why i want people to ask about it
cuz it opens up for discussion

time to write docs for.. contributing to docs!
yeah i do :p
i have an issue where /plugins isnt working/isnt being built by astro
is this something to worry about or
nop
alright :3
@wide scroll
hi
cuz it was for just the docwriters
and we have so little people here it didnt really need mod
i thought i’d had a lot more free time than i actually do aha, coming up on my first lot of exams
i will be glad to help but feel free to remove me if im too inactive :)
dw
activity isnt a mandatory thing
you can write whenever and however much you want
no matter how little the contribution i value it a ton
has anyone done docs for native plugins
not yet, they're brand new
vencord/vencord.dev
when we get a couple of good pages down i'll write a work in progress notice and publish it to the main site
ty
should this be moved to wiki
jetbrains writerside
real?
erm
these are some great docs
horror splash
okay so
soon I will create all the markdown files i think will be necessary
if anyone wants to contribute, just pick a section and pr 🙏🏻
but please only if you really know what you're talking about
and if you want anything specific covered, just lemme know
deployment is at https://docs.vencord.dev/
The cutest documentation!
(it's still very WIP for now)
css
why did we go with docusarus
it's not bad but I'm not fond of it and I feel there's better options
what
because there's no point infinitely bikeshedding
it's easy to switch, just need to get started and just do it
okay we switching to starlight
jetbrains writerside
makes sense
I was up to helping with anything vitepress related
search works out of the box
no hamburger menu on mobile?
does it not have
i was gonna ask why you weren't using starlight earlier given you use astro everywhere else
theres one top right..
@jagged kraken 
this might be useful https://github.com/HiDeoo/starlight-typedoc
I saw!!
CANT WAIT FOR THE TRANSLATION FUNCTION TO GET DOCUMENTED
/**
* Translates a key. Soft-fails and returns the key if it is not valid.
* @param key The key to translate.
* @param variables The variables to interpolate into the resultant string. If dealing with plurals, `count` must be set.
* @returns A translated string.
*/
theres a starlight plugin for localization
mmm yummy

nvm it was just a vscode extension
useless
why would we localise docs
all programmers should be good at english
no point localising developer docs
i wanna localise the mod but a certain somebody wishes to pack me into an archive literally invented by the devil
(i still dont know what we're packing into them)
vencord files & translations
which files

the ones in the data dir?
wait no
uh
the
vencord.js and whatnot
vencord.asar/
vencord/
renderer.js
renderer.js.map
main.js
main.js.map
preload.js
preload.js.map
vendor/
monaco/
...
other-dependency/
explode.js
locales/
en.json
de.json
I See
so the bit that gets injected will just be a loader
and it'll read the files from the archive
hey thats exactly how my client mod was gonna work ages ago!
anyway about the docs
i don't particularly like the default theme but i'm unsure yet which theme to use for the docs site. i don't think we should use the same theme as the vencord.dev site
you can easily create themes here, maybe someone wants to come up with smth and propose it: https://starlight.astro.build/guides/css-and-tailwind/#theming
accent 343 0.27 gray 0 0.02
i cooked trust
/* Dark mode colors. */
:root {
--sl-color-accent-low: #4b134f;
--sl-color-accent: #dd34ff;
--sl-color-accent-high: #d5add0;
--sl-color-white: #e4c5e6;
--sl-color-gray-1: #dccae5;
--sl-color-gray-2: #c2b2c9;
--sl-color-gray-3: #6b6271;
--sl-color-gray-4: #48404b;
--sl-color-gray-5: #403944;
--sl-color-gray-6: #2a272c;
--sl-color-black: #181619;
}
/* Light mode colors. */
:root[data-theme='light'] {
--sl-color-accent-low: #ffc7ee;
--sl-color-accent: #906186;
--sl-color-accent-high: #721875;
--sl-color-white: #17181c;
--sl-color-gray-1: #24272f;
--sl-color-gray-2: #353841;
--sl-color-gray-3: #545861;
--sl-color-gray-4: #888b96;
--sl-color-gray-5: #c0c2c7;
--sl-color-gray-6: #eceef2;
--sl-color-gray-7: #eae3ea;
--sl-color-black: #ebebeb;
}```
I tried
thats also nice
idk which one is better
we will simply provide 3 million theme options

does anyone have any idea what to put on the homepage? where there's currently the placeholder cards https://docs.vencord.dev
possibly have cards that act like a brief summary on what the documentation is gonna cover regarding developing for and with vencord
then the introduction would have more detailed information on that, possibly
just as repeatable bullet points as not everyone reads the cards on the front page
im gonna write creating plugins
i already wrote most of it
oh ok
i'll base these docs off of that then
yeah you can look into shiki dual themes
docer
doccer cmpose
writerside
How do you do that
Cool
saving the planet by using starlight docs ✨
lmao what
propaganda
not the doccers man
pandoc where
just wait like 4 months until they add as much shit as docusaurus
they alr have comparable features
i love how ios sucks ass
github don't work on webkit
vencor docs don't work on webkit
half the sites fkn break on webshit
so much for doing more than discord/media watching on ipad
my brother in shig
praise
Tim cook logic
garbage
it’s mainly due to low versions, you’re just always stuck with old software (including webkit)
not sure how apple makes their browsers so obsolete and unusable when it comes to 2-3 year old updates
I still want an iPad again
and an ipod touch (and nano) 7th gen
and an ipod nano 6th gen (it's like a watch)
they didnt put mediawiki because they knew they would get beaten
(probably not)
wikis are a different thing
yeah
the only similarities are that they display information (optionally done collaboratively)
they should update that table 
the comparison table doesn't really matter or atleast, make sense, as majority of starlight users have used astro before and will definitely bundle in their own tools, thus increasing that
my new favorite saying
yes
Pretty much the title, it's just a small clarification I felt was needed.
this is just wrong. you always put them in src and build... dist is the folder where output artifacts are created by building
??????
in.. dist?
this is just wrong. you always put them in src and
pnpm build... dist is the folder where output artifacts are created by building
Really? For me it only started to work when I placed it to the dist folder.
sounds like unintended behaviour
i don't think this wording is very good. it doesn't make it clear that simply creating an empty folder can already cause the issue
b1ddaf1 Better clarify empty files in plugin folder - Vendicated
@gaunt kestrel you can put “Closes #pr-number” in the commit message to automatically close it
yes but only if you have perms to close
what?
as soon as the commit gets into master it gets closed afaik, doesn’t matter what perms the user has
fear
updated submission.md to say something, better than leaving https://docs.vencord.dev/plugins/submission/ with nothing
https://docs.vencord.dev/installing/custom-plugins/#adding-your-plugin
the word "index.ts" is repeated twice, where one of them should say "index.tsx"
- [Pre-Flight](/plugins/submission/#pre-flight)
Vencord provides plugins to modify the Discord Client to your liking. If you want to create your own plugin head to [Plugin Development](/installing/)
Vencord provides plugins to modify the Discord Client to your liking. If you want to create your own plugins, head to [Plugin Development](/installing/)
However, if your PR gets denied, don't worry. Vencords Maintainers give comments on approval/denial, so you can always fix any issues. Unless your plugin is in violation of rules.
Now to the `component`. You can either build a component directly in it or import it from another file. In this guide we will create the component in another file and import it later on.
This should always be preferred over the Settings API if possible, as localstorage has very strict size restrictions and blocks the event loop. Make sure your keys are unique (tip: prefix them with your plugin name) and please clean up no longer needed entries.
Command in docs is incorrect, replaced with buildWeb and watch buildWeb
Simply add the `--watch` flag, for example `pnpm buildWeb --watch`!
This pull request adds a correction to build Vencord as an extension for the web!
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
why?
because you didn't read the prs, that's why
Made it a draft cause it's still messy/unfinished
😔
https://docs.vencord.dev/installing/custom-plugins/#adding-your-plugin the word "index.ts" is repeated twice, where one of them should say "index.tsx"
Could do a better description perhaps?
"text editor of trust" sounds weird, can be "text editor of choice"
Should have link to installing docker compose: https://docs.docker.com/compose/install/
did a review, hope thats ok
it should say docker compose but w/e
because shiggy belongs in everyone's source code
is there anything for explaining how patches work planned
like the nerd stuff behind it or just how to write patches
how to write them
by the nerd stuff, im assuming you mean how they work
yeah how they actually modify stuff
i would love for something like that too
i still haven't managed to write a successful patch
This page is empty: https://docs.vencord.dev/plugins/submission/
What are the plans for this?
There used to be documentation on this on the repo but it was (re)moved:
https://github.com/Vendicated/Vencord/blob/0d5e2d0696da494aee2126b4cadbca7e07066b89/CONTRIBUTING.md#contributing-a-plugin
https://github.com/Vendicated/Vencord/blob/0d5e2d0696da494aee2126b4cadbca7e07066b89/docs/2_PLUGINS.md#making-your-patch
This PR adds a comprehensive guide to the Vencord documentation, detailing how users can submit plugins for official inclusion. The guide includes:
- Steps to fork and clone the Vencord repository.
- Instructions on adding a plugin to the
src/pluginsdirectory. - How to commit changes and create a pull request.
- An overview of the review process and how to respond to feedback.
- Information about licensing and crediting plugin authors.
This guide aims to streamline the plugin sub...
Ok, i fixed it on the PR i made
inbuilt plugins do not need installation instructions
we dont need installing
base branch should be dev, if it isnt then maintainers will switch it to dev anyway
plugins are first merged into dev
would probably make more sense to have this link to the discord
it doesn't make sense to list these (other than the readme, but that should probably be a seperate point) files, as these would already have been created before this
The ChatGPT Large Language Model
Done, resolved everything in last commit!
Done, resolved everything in last commit!
Done, resolved everything in last commit!
Done, resolved everything in last commit!
Done, resolved everything in last commit!
Done, resolved everything in last commit!
Done, resolved everything in last commit! tysm for your time
😭
please dont use chatgpt for docs 😭
did you literally pipe our comments into chatgpt and tell it to fix it
bro
thanks for trying to help out, but this is
- not really what I intended for this page
- incorrect in multiple aspects
I used it for fix it fast, as i dont had time rn, if want something better i can do it but first i should have more time to make it correct and dont use AI for corrections
It’s literally just you export your functions inside of native then copy the native definition from another plugin and call your functions
As i told, i made a fast doc about submission yesterday, i took some time on my break time and made this rewrite, and not used AI for fix things, hope it helps :b
Aditionally, i added an update section, i can delete it if wanted


I made it fast and obv it got cancelled, i made a new one more slow and better: https://github.com/Vencord/Docs/pull/13
i just had a huge look at it
This is too oversimplified; There are a decent amount of people who have decided to install userplugins before getting started. Change this to branch into a "if you've installed userplugins set the remote and upstream branches" and an "if not clone the fork".
There should probably be an "unless absolutely necessary" clause here
Suggest users to attach images in GitHub issue comments. There's an issue thread for it
Overly verbose? Maybe instruct users to learn git branching earlier
Fixed, i dont know what i wrote on there, i was a little sleepy 😅
Everything fixed, tysm for your comments and notes @Sqaaakoi @Sqaaakoi :b
?remindme 7pm .
Alright @quartz oracle, in 7 hours, 7 minutes and 2 seconds: …
@quartz oracle, <t:1725839578:R>: …
notepad++ always on top 🔥
the docs should really specify installation for userplugins that are from a git repository
instead of just being in the pinned https://canary.discord.com/channels/1015060230222131221/1257038407503446176
Notepad is a built in code editor atp
Small typo:
"... or a folder containing an index.ts or index.ts file."
where it's referred to index.ts twice
I mean, I understand if something’s got a lot of PR(s) not being able to search every single one for something that already does that but there’s like four active ones its not that difficult to search
this sounds like a "trivial fix PR was never looked at"
or just someone desperate for that Contri that they do a one line change so they say that “They contributed to Vencord”

changed line 44 to say "index.ts or index.tsx" file. instead of "index.ts or index.ts"
this is like the 4th pr like this
time for me to make the 5th
can someone just accept one of the PRs
ngl new doccer so bad because of how unmaintained it is
<---- does not want to fix it knowing that if I do the PR will most-likely sit for 3 months

docs are literally just markdown files yet nothing is done
we need docs that are more like a wiki
there is the "client mod wiki"
but idk if thats the right place to do it all
docs: ghost ping vee five times in plugin-dev

i never did elaborate on what i mean by this
when I say "more like a wiki" i mean easily editable, having to PR documentation kinda sucks
the "quick edit and it's done" approach is very nice
also user pages on wikis could be a good place for niche guides that might not be fully accepted by the community
the problem is that good documentation needs to be reviewed for accuracy
we don't have thousands of nerds watching every change looking for errors or vandalism
definitely not
just make pr
we don't need low effort drive-by contributions
we need people with experience making plugins writing the docs that actually matter
most topics need no docs
since most things should be fairly self explanatory if u just read
instead, we need to cover specific topics like
- how to find modules efficiently
- how webpack finds work
- how to write patches
- how to run native code with native.ts file
we had docs for patches which where never transferred over
yea, but tbh they werent that good
true, but they were better than nothing
why though
Move packages that are only required during development from dependencies to devDependencies.
four forks for a single line change
This PR should either be merged or closed IMO.
The docs just have an empty page, something was seemingly meant to go there.
This PR should either be merged or closed IMO. The docs just have an empty page, something was seemingly meant to go there.
I agree, if no one accept this PR, i will close it.
This PR should either be merged or closed IMO.
Thats how... pull requests work
like just wait for reviews, damn
am i stupid or are the docs surprisingly empty
its because theres not much that can be reasonably documented
most of the work is in figuring out discords code, which we can't document
and cause no one wrote docs 
ive been wanting to write docs for some time
but i never get around to doing it :blbocatcozy:
Did he js make the exact same PR as the one he closed?
They got tired of waiting
Ic
it literally does requires nothing for you to keep a PR open other than to keep the fork


I Find it frustrating that right on the front you say
This documentation will cover topics like:
... all the available plugin APIs
yet there is not a glimpse of API documentation.
docs aren't finished, just look through existing plugin code
Bcs there is no 3 party plugins channel anymore. I figure it out that it dosent need to be in instation and also in plugin setup does the same.
is this a good idea
idk
i will vibe code your death @gaunt kestrel
The "Change Vencord Location" option is now concealed inside of the "Vesktop Developer Options" menu, so this updates the docs to guide people to the right location.
docker
i thought this was a channel for docker at first
bros wanna be discord userdoccers 😭 😂✌️
userdockers
podman >>>
I thought this channel was for docker
Holy confusing channel names, I thought #🪅-progaming was for gaming
Not that I care but it’s funny 😂
please merge i beg you
main repo pr backlog rot has reached even docs
if anything it should be on all pages
ok added just for the first 3 pages though, cus imo any more and it starts looking unnecessary/you already need vc cloned
Merge
happy 2 months
Vencord docs never getting finished btw
Might as well delete this channel and the repo
u could work on it instead of being annoying
Alright @summer hazel, in 18 hours, 4 minutes and 27 seconds: …
@summer hazel, <t:1776054333:R>: …
@summer hazel get to work
okay.
if you give me a list of things to do ill do them
@gaunt kestrel @gaunt kestrel
@gaunt kestrel
im hungry
i wanna write something about natives tbh
i'm always the one yelling at equicord plugin devs to properly do native
get to it then mate
do rn
do rn (with ping)
the page that should tell you how to submit plugins is basically empty, that still needs to be done, and the last change was 2 years ago so people might've forgotten that still needs to be done
src/content/docs/plugins/submission.md
isnt the current plugin submission "guide" just
look at other "new plugin" prs





