-
Notifications
You must be signed in to change notification settings - Fork 87
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 restructure #1419
Docs restructure #1419
Conversation
Transactions CostsSizes and execution budgets for Hydra protocol transactions. Note that unlisted parameters are currently using
Script summary
Cost of Init Transaction
Cost of Commit TransactionThis is using ada-only outputs for better comparability.
Cost of CollectCom Transaction
Cost of Close Transaction
Cost of Contest Transaction
Cost of Abort TransactionSome variation because of random mixture of still initial and already committed outputs.
Cost of FanOut TransactionInvolves spending head output and burning head tokens. Uses ada-only UTxO for better comparability.
End-To-End Benchmark ResultsThis page is intended to collect the latest end-to-end benchmarks results produced by Hydra's Continuous Integration system from the latest Please take those results with a grain of salt as they are currently produced from very limited cloud VMs and not controlled hardware. Instead of focusing on the absolute results, the emphasis should be on relative results, eg. how the timings for a scenario evolve as the code changes. Generated at 2024-05-08 18:01:55.137530697 UTC Baseline Scenario
Baseline Scenario
|
9a88c10
to
b238fd1
Compare
This contains many dummy links while we draft this out.
See README and CHANGELOG for rationale
Also remove --profile from docker compose demo setup.
This is very high level and rather introductory material.
One of them being called getting-started will ensure these old URLs still work natively (it was the main link on the landing page).
This is severely outdated and while we should have a how-to / similar guide going forward, we can't keep this one.
Most of the terms should be explained now in the configuration page and links to upstream are also broken now. If there is a need, more targeted explainers or guides are preferred. For example like the [EUTxO crash course](https://aiken-lang.org/fundamentals/eutxo).
While working on the how-to instructions I stumbled over #1421 |
4e5eb82
to
c09e423
Compare
This simplifies the link checking
We have still some quite unreleated topics which are in need of a new home. Keep them accessible throught the navbar and links to it intact.
The client side redirects will not work for deep links though.
Updates the structure of our documentation page.
📚 Drops internationalization (thats why there are so many files changed)
📚 Removed some severely outdated pages
📚 Grouped user manual into some general info, tutorials, docs + how-tos and reference material. This uses a hand-rolled
sidebars.js
config to allow for the sectioning.📚 Re-interpreted the demos as "getting started" tutorial. Using this also as the very prominently deep-linked
/docs/getting-started
page. So we have now one tutorial that runs on a local devnet usinghydra-tui
, and one more involved that uses a public testnet and the API directly.--profile
on the docker compose setup.📚 Cleaned up the installation and quickstart pages into
installation
andconfiguration
pages. The latter is intended to hold various documentation ofhydra-node
options and concepts.📚 Converted some documentation as "how-to" which besides the tutorial serve as "recipes" on how to do one or the other thing.
📚 There are still some legacy "core concepts" articles which are in need for a new home (maybe on https://cardano-scaling.org?). Specifically the API behavior should be part of the api reference, but this is a good follow-up.
Main entry point of the user manual:
And developer documentation (still a bit of a catch-all area):