documentation VS docsify

The new docs are at https://docs.iota.org and the one comparable to the old one you linked would be probably this one: https://wallet-lib.docs.iota.org/docs/libraries/nodejs/examples

I recently graduated in Economics & Management and started working in one of the big 3 (Bain, BCG, McKinsey) few weeks ago as Strategic Consultant. Although I am passionate about technology, I have no technical background in this area. Since 2016 I have followed the evolution of cryptocurrencies and more particularly of IOTA following a discussion with a friend. I feel that my company is not exploring enough the potential of blockchain or, in this case, tangle. We (in Belgium) are always too late compared to other countries. Being a junior associate, I would like to specialize myself in the solutions that this new technology can bring. Unfortunately, I don't know where to start. My company is working on different projects in different industries: digitalization, smart cities, automotive supplychain, ... They also work a lot with EU Institutions. The potential is enormous. Do you think that https://docs.iota.org/ would be a good start for me to go deeper into understanding the tangle and its possible applications?

I’m not sure if this is fully updated, but you can find some info here: https://docs.iota.org/

Which criteria does IOTA not fulfill? Its number 25 by marketcap at $4,230,220,945, has extensive documentation, and I'm not too positive about the API being based on BitPay Insight but surely it could be accomplished.

documentation, learning material: https://github.com/iotaledger/documentation https://github.com/iotaledger https://iotone.academy/ https://tanglebay.org/guides/hornet-vps-fullnode/ https://youtu.be/vb2biHV-be4

Docsify is frequently updated; the latest release was on June 24, 2023, and the most recent update was on December 17, 2023. It is MIT-licensed and has an active Discord community.

okay new plan, does anyone know how to do this docsify on github? i obviously am a noob on github and recently on reddit. I'd like to help where i can but my knowlegde seems to be my handycap. i could provide you a trash-mail, if you need one, but i need a PO (product owner) to manage the git... i have no clue about this yet (pages and functions and stuff)

The tools to author it aren't that important, frankly. Ask your audience what they're most comfortable using and try to meet them there.

If the stakeholders are technical, you have more options. If they aren't, I hope you like Google Docs or Word, because if you give them anything other than that or a PDF, they'll probably complain. At worst, yeah, write it in a long Markdown text file and use tools like pandoc to transform that into other formats as needed.

If you do need a website and you're not generating enterprise-scale amounts of content (and it sounds like you're not) try things that let you avoid needing build steps and infrastructure if at all possible, so you can iterate and deploy changes with as little friction as you can.

Tools like Docsify[1] can take a pile of Markdown files and serve a site out of them, client- or server-side, without a static build step. Depending on the org, you can get away with GitHub's default rendering of Markdown in a repo. Most static site builds for stuff your scale are overengineered instances of premature optimization.

Past those initial hurdles, the format and tools challenges are all in maintenance. How can you:

- most easily keep the content up to date

- delegate updates as the staff grows or changes

- proactively distribute updates ASAP to the people who'd most benefit from receiving them

That's going to depend a lot more on who'll contribute updates, what their technical proficiency's like, and how they prefer to communicate. It might be a shared git repo and RSS or Slack notifications if they're comfortable with those things, and it might be a Google Doc and email if they're like most non-technical stakeholders.

1: https://docsify.js.org

Big fan of https://docsify.js.org since theres no need to compile your static site. A small amount of js just renders markdown.

If you are searching for examples of an arbitrary Jellyfin support site, visit https://travisflix.com/help/#/support (or help.travisflix.com which redirects to the /help/ URI of the TLD) to take a look at what I have done with docsify on Github Pages.

*Leantime - Competitor to OP? Updated recently, uses Docsify, no demo :(

There are a lot of open-source projects that can help businesses to save time and money. For example, we created a Free Admin panel a few months ago https://github.com/altence/lightence-admin That's an example of free documentation generator https://github.com/docsifyjs/docsify There are a lot more examples. And I want to find an idea of some similar generic solutions that can help various types of businesses