# Build a Technical Documentation Page:technical information

**URL:** <https://forum.freecodecamp.org/t/build-a-technical-documentation-page-technical-information/249140>\
**Category:** General\
**Created:** [January 3, 2019, 7:48pm UTC](https://forum.freecodecamp.org/t/build-a-technical-documentation-page-technical-information/249140 "2019-01-03T19:48:14Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![yonichanowitz](https://sea3.discourse-cdn.com/freecodecamp/user_avatar/forum.freecodecamp.org/yonichanowitz/32/79509_2.png) [@yonichanowitz](https://forum.freecodecamp.org/u/yonichanowitz)\
**Post date:** [January 3, 2019, 7:48pm UTC](https://forum.freecodecamp.org/t/build-a-technical-documentation-page-technical-information/249140/1 "2019-01-03T19:48:14Z")

</div>

does the technical information have to actually be working useful information? or can i just fill it with nonsense?

**Your browser information:**

User Agent is: `Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.75 Safari/537.36`.

**Link to the challenge:**  
[https://learn.freecodecamp.org/responsive-web-design/responsive-web-design-projects/build-a-technical-documentation-page](https://learn.freecodecamp.org/responsive-web-design/responsive-web-design-projects/build-a-technical-documentation-page)

---

<div class="post-metadata">

**Author:** ![ArielLeslie](https://sea3.discourse-cdn.com/freecodecamp/user_avatar/forum.freecodecamp.org/arielleslie/32/264841_2.png) [@ArielLeslie](https://forum.freecodecamp.org/u/ArielLeslie)\
**Post date:** [January 3, 2019, 8:23pm UTC](https://forum.freecodecamp.org/t/build-a-technical-documentation-page-technical-information/249140/2 "2019-01-03T20:23:42Z")

</div>

Considering that these projects make up a portfolio of sorts, I wouldn’t recommend making their contents be nonsense.

---

<div class="post-metadata">

**Author:** ![kevinSmith](https://sea3.discourse-cdn.com/freecodecamp/user_avatar/forum.freecodecamp.org/kevinsmith/32/72934_2.png) [@kevinSmith](https://forum.freecodecamp.org/u/kevinSmith)\
**Post date:** [January 3, 2019, 8:31pm UTC](https://forum.freecodecamp.org/t/build-a-technical-documentation-page-technical-information/249140/3 "2019-01-03T20:31:47Z")

</div>

Maybe it wasn’t the best thing, but I made a technical document on how to use pizza. I wouldn’t advice lorem ipsum, but it may not need to be coding related. I never intended that for my portfolio though. If it was, I probably would have done it on a technical subject.

---

<div class="post-metadata">

**Author:** ![yonichanowitz](https://sea3.discourse-cdn.com/freecodecamp/user_avatar/forum.freecodecamp.org/yonichanowitz/32/79509_2.png) [@yonichanowitz](https://forum.freecodecamp.org/u/yonichanowitz)\
**Post date:** [January 3, 2019, 8:43pm UTC](https://forum.freecodecamp.org/t/build-a-technical-documentation-page-technical-information/249140/4 "2019-01-03T20:43:36Z")

</div>

what WOULD you recommend? everything i think of i either don’t actually know about, or sounds stupid

---

<div class="post-metadata">

**Author:** ![ArielLeslie](https://sea3.discourse-cdn.com/freecodecamp/user_avatar/forum.freecodecamp.org/arielleslie/32/264841_2.png) [@ArielLeslie](https://forum.freecodecamp.org/u/ArielLeslie)\
**Post date:** [January 3, 2019, 8:54pm UTC](https://forum.freecodecamp.org/t/build-a-technical-documentation-page-technical-information/249140/5 "2019-01-03T20:54:03Z")

</div>

Sounds like a good reason to do a bit of research on something relevant to the programming skills you’re trying to build. Why not do technical documentation on something JavaScript related that you’ve learned so far, but could benefit from understanding better?

---

<div class="post-metadata">

**Author:** ![kevinSmith](https://sea3.discourse-cdn.com/freecodecamp/user_avatar/forum.freecodecamp.org/kevinsmith/32/72934_2.png) [@kevinSmith](https://forum.freecodecamp.org/u/kevinSmith)\
**Post date:** [January 3, 2019, 9:36pm UTC](https://forum.freecodecamp.org/t/build-a-technical-documentation-page-technical-information/249140/6 "2019-01-03T21:36:27Z")

</div>

You could narrow it down to something more specific, like flexbox or ES6. Or even more specific than that.

---

<div class="post-metadata">

**Author:** ![yonichanowitz](https://sea3.discourse-cdn.com/freecodecamp/user_avatar/forum.freecodecamp.org/yonichanowitz/32/79509_2.png) [@yonichanowitz](https://forum.freecodecamp.org/u/yonichanowitz)\
**Post date:** [January 3, 2019, 10:14pm UTC](https://forum.freecodecamp.org/t/build-a-technical-documentation-page-technical-information/249140/7 "2019-01-03T22:14:51Z")

</div>

in short: everything in the docs

---

<div class="post-metadata">

**Author:** ![ILM](https://sea3.discourse-cdn.com/freecodecamp/user_avatar/forum.freecodecamp.org/ilm/32/363239_2.png) [@ILM](https://forum.freecodecamp.org/u/ILM)\
**Post date:** [January 16, 2021, 6:03pm UTC](https://forum.freecodecamp.org/t/build-a-technical-documentation-page-technical-information/249140/8 "2021-01-16T18:03:04Z")

</div>


