-
-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Outline will be converted to project boards based off sections we agree to #60
base: main
Are you sure you want to change the base?
Conversation
Also, this will NOT use their chapter style. This was only formatted in this manner because they intended for this to be made into a book. While we could possibly do the same at some point, it's unnecessary imo. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Formatting errors and needed symbols.
Co-authored-by: softcode <[email protected]>
Co-authored-by: softcode <[email protected]>
Co-authored-by: softcode <[email protected]>
Co-authored-by: softcode <[email protected]>
@pulsar-edit/core @pulsar-edit/backend I could use your advice on this as well. I know there are sections we can straight up remove or depreciate in some way and leave in the past. If you could provide your help on this one, we would be most appreciative. |
@pulsar-edit/documentation I've updated this a bit. But still needs organization. I imagine this will take a bit to organize and get fixed, feel free to use the suggestion button when reviewing the code. I'd recommend even possibly forking this and doing a pr into it. |
Bumping as the intention with this was to reorganize and make easier the layout of the documentation in such a way we might have creative names formatted such as "Section name here: section short description". Now that things are getting a bit more interest, esp with all the coverage in open source outlets, we need to make sure to finalize this finally. Especially making note of stuff that is missing documentation and making sure to properly cover it. Especially adding images and making sure we can get all of it translated eventually. Any help and ideas on this matter would be greatly appreciated! Especially since I wanted this to be a collaborative effort from the get go and that's still the intent. |
This is a straight copy of the outline as seen before. However, I'd like us to collaborate on this one and reorganize as this will be the outline for our sections to make things easier for people coming to the project. As well, I will be or have added changes to #29 and need help updating that one as well.