Skip to content
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

Docs? #95

Open
LuisThe0ne opened this issue Jun 19, 2022 · 9 comments
Open

Docs? #95

LuisThe0ne opened this issue Jun 19, 2022 · 9 comments

Comments

@LuisThe0ne
Copy link
Contributor

LuisThe0ne commented Jun 19, 2022

Hello,

I noticed that this project hasn't really got a documentation, so I wanted to ask if Docs are needed (@openshwprojects)?
I would really like to create them, because I want to be part of the project. (I would suggest to use Mkdocs, like tasmota does I think)

Regard,
Luis

@btsimonh
Copy link
Collaborator

Hi Luis,
a good place to start would be to populate the Wiki here.
I really hate the TAS docs build process, but we could always migrate the pages & words if required later.
The wiki should be publicly editable - and then it also means that you could create placeholders and ask for help to populate them?
br,
Simon

@TommySharpNZ
Copy link

Yeah I can't even figure out where to get BKwriter 1.6 so docs for us amateurs would be great!!! I'll happily help by contributing to them once I learn a bit more...

@openshwprojects
Copy link
Owner

@TommySharpNZ well, to be honest, there was a link to OpenBK7231T repo in the readme under bkWriter mention, and in that repo (in the same level) there is a bkWriter.zip, soo.... but as said in the other issue, now I added a direct link to repo, and it most likely won't get easier than that now.

@LuisThe0ne
Copy link
Contributor Author

LuisThe0ne commented Jul 3, 2022

Hi Luis, a good place to start would be to populate the Wiki here. I really hate the TAS docs build process, but we could always migrate the pages & words if required later. The wiki should be publicly editable - and then it also means that you could create placeholders and ask for help to populate them? br, Simon

I think to pobulate the Wiki would be a ggreat Idea, so @openshwprojects I would be nice if you could make the wiki editable for everyone. (https://docs.github.com/en/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis), this is the only way because github does not support wiki pull requests. A seperate wiki repository would also be a good idea because of the pull request and issue capabilitys. As a third option i would suggest a simple wiki directory with all the markdown files and links between those files.

@openshwprojects
Copy link
Owner

Hey, what's the state of this?
Wiki is already editable, I made the change the few days ago or so.

@LuisThe0ne
Copy link
Contributor Author

Sorry, did not notice the change I am currently on holiday with my family, but when I am back at home an I got access to my pc I am going to look into creating or starting the creation of a wiki.

@LuisThe0ne
Copy link
Contributor Author

The Wiki is now populated with I think most of the Information needed. :)

@jekader
Copy link

jekader commented Feb 21, 2023

Nice work on the documentation! I propose also shortening README.md and moving the rest of its current content to the /docs directory. The wiki is nice, but having docs in the repo is a good thing, too.

If you're fine with that I can prepare a PR doing this.

@LuisThe0ne
Copy link
Contributor Author

Sounds like a great idea!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants