diff --git a/README.md b/README.md index e77ad7c6..dd0234c5 100644 --- a/README.md +++ b/README.md @@ -194,12 +194,10 @@ You can view the .out file to see what the output of a test is in either case. # Further Help -+ [Additional hints](./HINTS.md) + [Documentation][documentation] + [OpenRAM Slack Workspace][Slack] + [OpenRAM Users Group][user-group] ([subscribe here][user-group-subscribe]) + [OpenRAM Developers Group][dev-group] ([subscribe here][dev-group-subscribe]) -+ @mrg@fostodon.org # License @@ -223,9 +221,9 @@ If I forgot to add you, please let me know! [Github issues]: https://github.com/VLSIDA/OpenRAM/issues [Github pull request]: https://github.com/VLSIDA/OpenRAM/pulls -[Github project]: https://github.com/VLSIDA/OpenRAM +[Github project]: https://github.com/VLSIDA/OpenRAM -[documentation]: https://docs.google.com/presentation/d/10InGB33N51I6oBHnqpU7_w9DXlx-qe9zdrlco2Yc5co/edit?usp=sharing +[documentation]: documentation/docs/source/index.md [dev-group]: mailto:openram-dev-group@ucsc.edu [user-group]: mailto:openram-user-group@ucsc.edu [dev-group-subscribe]: mailto:openram-dev-group+subscribe@ucsc.edu diff --git a/HINTS.md b/docs/source/FAQ.md similarity index 99% rename from HINTS.md rename to docs/source/FAQ.md index 6f29c16b..2040ca61 100644 --- a/HINTS.md +++ b/docs/source/FAQ.md @@ -1,3 +1,5 @@ +### [Go Back](./index.md#directory) + # Debugging When OpenRAM runs, it puts files in a temporary directory that is diff --git a/docs/source/index.md b/docs/source/index.md index 295bc665..4bfb1d9f 100644 --- a/docs/source/index.md +++ b/docs/source/index.md @@ -24,6 +24,7 @@ These pages provide the documentation of OpenRAM. You can use the links below to 16. [Routing](./routing.md#go-back) 17. [Characterization](./characterization.md#go-back) 18. [Results](./results.md#go-back) +19. [FAQ](./FAQ.md#go-back) @@ -101,4 +102,4 @@ These pages provide the documentation of OpenRAM. You can use the links below to * Verification wrapper scripts * Uses a wrapper interface with DRC and LVS tools that allow flexibility * DRC and LVS can be performed at all levels of the design hierarchy to enhance bug tracking. - * DRC and LVS can be disabled completely for improved run-time or if licenses are not available. \ No newline at end of file + * DRC and LVS can be disabled completely for improved run-time or if licenses are not available.