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

Restructure and extend documentation #371

Open
msiemens opened this issue Feb 5, 2021 · 4 comments
Open

Restructure and extend documentation #371

msiemens opened this issue Feb 5, 2021 · 4 comments
Assignees

Comments

@msiemens
Copy link
Owner

msiemens commented Feb 5, 2021

This is a note to myself to rework, restructure and extend the documentation based on the principles layed out in https://documentation.divio.com/introduction/ (and https://v3.vuejs.org/guide/contributing/writing-guide.html for that matter).

I considering adding a how-to section in the process. If anyone has ideas about what topics would be useful for short how-to guides/articles, feel free to comment on this issue 🙃

@eugene-eeo
Copy link
Contributor

probably writing extensions, with a little description of the internals (how to extend the code?).

@vincentdavis
Copy link

It's been awhile since I worked with TinyDB and I was looking up how to use db.upsert.

>>> db.upsert({'name': 'John', 'logged-in': True}, User.name == 'John')

This is confusing because User.name is defined near the top of the page, I was thinking to myself, is User a table or another database? There are several places with this type of issue. It makes the otherwise awesome documentation a little difficult to use as a reference because the examples are not complete.

I would be happy to help with documentation or short how to guides or examples.
I am currently working to import data from Excel files doing a lot of db.upsert and field transformations. I could do some examples like this.

Point me in a direction and I can help some.
Thanks for TinyDB!

@msiemens
Copy link
Owner Author

msiemens commented Mar 9, 2021

This is confusing because User.name is defined near the top of the page, I was thinking to myself, is User a table or another database?

That's a good point. Basically the current documentation assumes that it is read from top to bottom. Instead we should split it into more subpages that have self-contained examples.

I would be happy to help with documentation or short how to guides or examples.

That's great! 🙂 I think we should have an examples section that contains commonly used operations. If you like you could contribute your experience from working with TinyDB about what examples would be most helpful. I'm still not sure how to organize this best. Maybe I'll start a pull request where we could have discussions about these matters. Or maybe start collecting examples in the GitHub project wiki. What do you think?

@msiemens
Copy link
Owner Author

Note to self: document using upsert with Documents

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

No branches or pull requests

3 participants