#8

those are the API docs and really need a proper relocation elsewhere… haven’t decided yet. @ppqq

#9

[this is good in 20 characters]

1 Like
#10

right. and with re-directs we may have more flexibility.

@speakerdamage: thoughts on where you’d expect them to be?

#11

I guess now I would expect them to live under the new docs - especially to take advantage of search.

looks like @tehn and @dan_derks are going to be updating norns docs now, but figured I’d point out anyway that studies 2-5 need to be redirected: https://monome.org/docs/norns/study-2/

2 Likes
#12

thank you caulen!

for historians + those watching at home, these files had permalinks which referenced /docs/norns/study-X.md, which ended up resolving into docs/docs/norns/study-X.md. removing the preceding /docs from the permalink cleared up the issue!

2 Likes
#13

Yay! Docs look great.

#14

This is such an amazing developpement for resources about monome. It was so tricky sometimes to find the right infos, or get a sense of the entire available documentation to easily dive in out of curiosity, both those things are answered here. I wish I could help more but can only say thanks. But just, to me, this is as fundamental, exciting and crucial to the monome ecosystem than a new release / new hardware.

4 Likes
#15

on github: teletype/docs/intro.md — all the links there are wrong :slight_smile: (this seemed like the relevant place to mention it)

#16

This isn’t a missed link but something that was hidden:

I’m new to norns and was looking for instructions on how to export audio to my laptop from the tape. This is briefly covered in the SFTP guide, but the guide was only mentioned once in the maiden page of the docs and for a different reason than exporting audio, only found my way there through asking. Would definitely be helpful to have this more easily explained/available in the docs as I can image other new users could also struggle to find this info.

1 Like
#17

perfect candidate for discussion, thank you!

would this feel at home with its own entry in https://monome.org/docs/norns/help/? perhaps a section that’s just “getting audio files to/from norns” would work, which would then describe the particular use with references to both webDAV and SFTP as tools toward that goal?

perhaps even a mention in the audio section of the primary documentation would help…

edit follow-up q:
what were your initial assumptions about audio export as a function? that it should live in maiden because there’s an audio section? i’m trying to determine how linear the jump is from “i need to get audio to/from norns from a computer” to “i need to use some sort of file client”, to help structure the docs journey :slight_smile:

1 Like
#18

I definitely though to check maiden first, but wasn’t surprised to be unable to transfer files there since doing so via wifi seemed like a lot to ask. So I did a quick search of the docs looking for instructions to transfer tape files. I then started searching here found history of the now-removed sync function. So then, I searched the docs for both “tape” and “sync” but wasn’t lead to the SFTP guide. I would imagine a brief description for the transfer process and a link for the SFTP guide in the tape section would be sufficient.

Admittedly I did overlook the backup entry in the help section; however, this is framed as a fallback plan when wifi won’t connect and doesn’t mention that it’s the primary way of transferring audio files. I don’t think think there needs to be any major changes, just small context clues in existing places like this would be helpful.

1 Like
#19

100%, great idea + thank you!

quick q: are you using SFTP because you’re on windows? or just preference over webDAV?

2 Likes
#20

I am on windows, yes.

2 Likes
#21

Hey… so I’m searching the docs trying to help someone with an issue and I noticed the menu is a bit crypitc to me (or maybe to a noob).

instead of maiden as a section header, perhaps connect or connecting would be better - and then list maiden, sftp, webdav, ssh, serial as sub items

2 Likes
#22

agreed! the current structure is more linear / less “look here to do this one type of thing”. I like the idea of it mirroring a reference and leaving the linear story to inside of the references. also got yr email – excellent suggestions, thank you! I’ll fold these in this weekend :slight_smile:

2 Likes
#23

Actually having trouble with a user who is out of disk space - I may have him email/message you directly.

#24

how would we feel about about a section on docs for community contributed studies (as a guide for a particular task or custom lib) ?

or is this better off as a topic ?

1 Like
#25

i am totally in support of contributed studies!

if it’s monome-specific, we can definitely find a place to reference it within the context of the docs. but it’s easiest to figure out where it would go once it exists :slight_smile:

so perhaps the goal is not to separate off “contributed studies” but to simply build upon existing studies (ie, new chapters, or improve those that are there)

1 Like
#26

cool !

well in this case it’s this softcut helper library type thing I just finished which needs documentation and an explained demo script to be actually helpful to anyone that would need it

I was kind of thinking of something along the lines of a norns > scripting > community page to keep the basics front and center and then community can be kind of a free-for-all of more advanced specific stuff like this. but idk !

oh maybe further can just turn into a page with links to both internal and external fun helpful things including this

1 Like
#27

I’m super stoked on supercut!

that’s sort of where https://monome.org/docs/norns/app/ is heading – as a jumping off point for folks to learn what the ecosystem is capable of, ideally with enough support from the developer at the hyperlinked landing point. I could see linking your guide to supercut directly in the https://monome.org/docs/norns/app/#sampling--looping section, especially if there’s a companion script that showcases the utilization (that said, I’ll add wrms today! :slight_smile: )

longterm, if there’s a wealth of similar resources, we’ll adapt and adjust the tree to support it. either way, it’d be best to host that info through your own channel and we can continue to iterate – or feel free to submit a PR to include your work!

1 Like