# Feedback on my Technical Document page **URL:** \ **Category:** I Built This\ **Created:** [April 30, 2019, 8:00am UTC](https://forum.freecodecamp.org/t/feedback-on-my-technical-document-page/274464 "2019-04-30T08:00:17Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![AlexOros](https://sea3.discourse-cdn.com/freecodecamp/user_avatar/forum.freecodecamp.org/alexoros/32/114826_2.png) [@AlexOros](https://forum.freecodecamp.org/u/AlexOros)\ **Post date:** [April 30, 2019, 8:00am UTC](https://forum.freecodecamp.org/t/feedback-on-my-technical-document-page/274464/1 "2019-04-30T08:00:17Z")
Hello, I would appreciate some feedback/critique on my [Technical Document Page](https://codepen.io/Alex_OR/pen/vMvPrv?editors=0010) ---
**Author:** ![brandon\_wallace](https://sea3.discourse-cdn.com/freecodecamp/user_avatar/forum.freecodecamp.org/brandon_wallace/32/198757_2.png) [@brandon\_wallace](https://forum.freecodecamp.org/u/brandon_wallace)\ **Post date:** [April 30, 2019, 11:25am UTC](https://forum.freecodecamp.org/t/feedback-on-my-technical-document-page/274464/2 "2019-04-30T11:25:25Z")
@AlexOros The styling is excellent, the layout need adjusting in my opinion. 1. I belive the menu should go to the top of the page like in the example project. 2. The huge space to the right of the menu is not necessary. I hope that my Techical Documentation page will look as good as yours. ---
**Author:** ![Roma](https://sea3.discourse-cdn.com/freecodecamp/user_avatar/forum.freecodecamp.org/roma/32/112899_2.png) [@Roma](https://forum.freecodecamp.org/u/Roma)\ **Post date:** [April 30, 2019, 12:38pm UTC](https://forum.freecodecamp.org/t/feedback-on-my-technical-document-page/274464/3 "2019-04-30T12:38:53Z")
It’s looking good @AlexOros. I would suggest; - running your code through an HTML validator. You have many times where you’ve used the same `id` more than once. codepen provides you with a validator. Click ont the arrow in the upper right and then click on ‘Analyze’. - On smaller screens, consider possibly making your Nav a hamburger menu and fixing it to the to top. ---
**Author:** ![AlexOros](https://sea3.discourse-cdn.com/freecodecamp/user_avatar/forum.freecodecamp.org/alexoros/32/114826_2.png) [@AlexOros](https://forum.freecodecamp.org/u/AlexOros)\ **Post date:** [April 30, 2019, 1:20pm UTC](https://forum.freecodecamp.org/t/feedback-on-my-technical-document-page/274464/4 "2019-04-30T13:20:40Z")
Thank you for the review @Roma , I didn’t know about codepen’s HTML analyzer it’s awesome. The hamburger menu did pass my mind but I decided against it. ---
**Author:** ![AlexOros](https://sea3.discourse-cdn.com/freecodecamp/user_avatar/forum.freecodecamp.org/alexoros/32/114826_2.png) [@AlexOros](https://forum.freecodecamp.org/u/AlexOros)\ **Post date:** [April 30, 2019, 1:27pm UTC](https://forum.freecodecamp.org/t/feedback-on-my-technical-document-page/274464/5 "2019-04-30T13:27:58Z")
Hey @brandon_wallace, about your points: - The menu going at the top. When you go on mobile the menu remains on top, for larger screens I made it sticky to the left, is this what you meant about the menu going to the top? - For the spacing the right of the navbar I took your suggestion and modified the spacing between it and the main content. P.S Thank you for the review ---
**Author:** ![DenizOrsel](https://avatars.discourse-cdn.com/v4/letter/d/977dab/32.png) [@DenizOrsel](https://forum.freecodecamp.org/u/DenizOrsel)\ **Post date:** [April 30, 2019, 2:58pm UTC](https://forum.freecodecamp.org/t/feedback-on-my-technical-document-page/274464/6 "2019-04-30T14:58:27Z")
@AlexOros Things to look for; 1. Menu border is touching letters when screen is scrolled. 2. Menu shifts a bit up as scrolled. It can stay where it is. 3. Go to top link arrow can initiate a faster elevation to top of the page. I like the style. ---
**Author:** ![ConnerOw1115](https://sea3.discourse-cdn.com/freecodecamp/user_avatar/forum.freecodecamp.org/connerow1115/32/326955_2.png) [@ConnerOw1115](https://forum.freecodecamp.org/u/ConnerOw1115)\ **Post date:** [April 30, 2019, 5:39pm UTC](https://forum.freecodecamp.org/t/feedback-on-my-technical-document-page/274464/7 "2019-04-30T17:39:52Z")
Wow! such an amazing tech doc page for JS!! the styles are so cool, but one suggestion: maybe keep all of the links fixed to the side of the tutorial so when I want to skip to different parts, I can. kinda like this: [https://codepen.io/Glaurung/pen/eXVwZP](https://codepen.io/Glaurung/pen/eXVwZP) ---
**Author:** ![brandon\_wallace](https://sea3.discourse-cdn.com/freecodecamp/user_avatar/forum.freecodecamp.org/brandon_wallace/32/198757_2.png) [@brandon\_wallace](https://forum.freecodecamp.org/u/brandon_wallace)\ **Post date:** [May 1, 2019, 1:32am UTC](https://forum.freecodecamp.org/t/feedback-on-my-technical-document-page/274464/8 "2019-05-01T01:32:15Z")
@AlexOros The words “Javasript - Arrays” are at the top of the page. I was suggesting that the menu should touch the top of the browser and “Javascript - Arrays” should be next to the menu on the right. Just a suggestion… Great job on your project. By the way, what is prism.css? ---
**Author:** ![AlexOros](https://sea3.discourse-cdn.com/freecodecamp/user_avatar/forum.freecodecamp.org/alexoros/32/114826_2.png) [@AlexOros](https://forum.freecodecamp.org/u/AlexOros)\ **Post date:** [May 4, 2019, 4:05pm UTC](https://forum.freecodecamp.org/t/feedback-on-my-technical-document-page/274464/9 "2019-05-04T16:05:31Z")
Hey @brandon_wallace hmm I was thinking that Javascript - arrays is something like the main title, a header and then comes the nav. Ah well it’s a matter of taste, oh and `prism.css` is a lightweight, extensible syntax highlighter for the `code` tag’s. Thanks for the kind words ---
**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:** [February 6, 2021, 1:37pm UTC](https://forum.freecodecamp.org/t/feedback-on-my-technical-document-page/274464/10 "2021-02-06T13:37:29Z")
Closed on February 6, 2021, 1:37pm UTC