1 00:00:00,820 --> 00:00:03,590 All right, so you've searched the Treehouse Community and 2 00:00:03,590 --> 00:00:05,010 you're still feeling stuck. 3 00:00:06,120 --> 00:00:08,340 Maybe it's a problem with your code. 4 00:00:08,340 --> 00:00:11,009 Or maybe you're having trouble grasping a design or 5 00:00:11,009 --> 00:00:15,555 development concept introduced in a Treehouse video. Whatever the 6 00:00:15,555 --> 00:00:19,834 problem, posting a question is a great way to get unstuck provided 7 00:00:19,834 --> 00:00:22,260 you give the Community enough information. 8 00:00:23,650 --> 00:00:27,190 Use the question title to guide the conversation. 9 00:00:27,190 --> 00:00:31,845 You don't need a long title, but something like "my code isn't working" 10 00:00:31,845 --> 00:00:34,250 doesn't really hint at the nature of the problem. 11 00:00:35,300 --> 00:00:39,820 Try your best to describe your issue. "End tag ul seen, but there 12 00:00:39,820 --> 00:00:43,402 were open elements" lets the Community know you're having 13 00:00:43,402 --> 00:00:48,840 an issue with HTML elements and references a specific error message. 14 00:00:50,530 --> 00:00:55,432 When posting the question, be as detailed as possible about the 15 00:00:55,432 --> 00:00:58,830 concept you don't understand or the coding error you're encountering. 16 00:00:59,870 --> 00:01:02,942 If you've attempted to solve the problem already and 17 00:01:02,942 --> 00:01:07,300 were unsuccessful, it's worth summarizing those attempts 18 00:01:07,300 --> 00:01:12,026 in your post. And if you're stuck on a particular code challenge, video, 19 00:01:12,026 --> 00:01:15,032 or Treehouse project, it's worth mentioning the name of the 20 00:01:15,032 --> 00:01:17,900 challenge you're having trouble getting past. 21 00:01:19,670 --> 00:01:23,130 Let's try composing a question for the Treehouse Community. 22 00:01:24,310 --> 00:01:29,158 Hello, I'm struggling to understand an error found in my workspace for 23 00:01:29,158 --> 00:01:32,360 the Welcome to HTML and CSS video. 24 00:01:32,360 --> 00:01:36,479 When I validate my HTML, I receive an error message stating, 25 00:01:36,479 --> 00:01:40,480 End tag ul seen, but there were open elements. 26 00:01:40,480 --> 00:01:41,860 But I'm not sure what that means. 27 00:01:43,360 --> 00:01:45,740 That's not enough information yet. 28 00:01:45,740 --> 00:01:49,670 So let's include our HTML code where the problem occurs. 29 00:01:50,680 --> 00:01:53,888 You might remember from the previous video that Jason's code 30 00:01:53,888 --> 00:01:56,860 sample had special formatting. 31 00:01:56,860 --> 00:02:01,893 We can format our text similarly using what's called markdown. 32 00:02:01,893 --> 00:02:03,941 If you're a development student, 33 00:02:03,941 --> 00:02:07,480 you'll learn more about markdown in future courses, although I've 34 00:02:07,480 --> 00:02:11,510 included a few resources in the Teacher's Notes beneath this video. 35 00:02:12,850 --> 00:02:17,195 For now, it's enough to know that three backticks (that's the key next 36 00:02:17,195 --> 00:02:20,000 to the number 1 on your keyboard) 37 00:02:20,000 --> 00:02:25,450 above and below your code sample will format your code so reviewers can read. 38 00:02:36,528 --> 00:02:40,550 The second set of backticks turn code formatting off. 39 00:02:40,550 --> 00:02:44,580 So if I have more to say I can continue writing beneath my code snippet. 40 00:02:45,900 --> 00:02:48,062 I mentioned in an earlier video, 41 00:02:48,062 --> 00:02:52,786 the optional possibility of pasting in a link to my workspace snapshot. 42 00:02:52,786 --> 00:02:54,600 So I'll do that now. 43 00:03:12,474 --> 00:03:16,878 A link to a workspace snapshot can be particularly helpful when your code 44 00:03:16,878 --> 00:03:21,165 involves multiple files communicating with each other. 45 00:03:21,165 --> 00:03:26,315 But pasting the snapshot isn't enough. Your goal here is to provide the 46 00:03:26,315 --> 00:03:29,255 Community with enough information to help them find 47 00:03:29,255 --> 00:03:31,030 your issue and offer advice. 48 00:03:32,650 --> 00:03:36,330 And now I'll conclude my post with a polite message. 49 00:03:36,330 --> 00:03:42,330 Thanks so much for your help. That looks pretty good, 50 00:03:42,330 --> 00:03:46,630 but I should make sure my code formatting looks okay. 51 00:03:46,630 --> 00:03:50,120 So I'll press the Preview icon in the lower right corner. 52 00:03:51,200 --> 00:03:55,920 That eyeball icon is pretty subtle and might be hard to find. 53 00:03:55,920 --> 00:03:59,770 But when I click, I see what my post will look like to the Community. 54 00:04:01,000 --> 00:04:04,702 If I'm not satisfied, I can press the icon again, 55 00:04:04,702 --> 00:04:09,020 which is now a pencil indicating I can make edits to my post. 56 00:04:10,890 --> 00:04:14,706 If you're posting this question underneath a particular video, 57 00:04:14,706 --> 00:04:19,840 the name of that video appears automatically underneath your question. 58 00:04:19,840 --> 00:04:24,720 This question will appear with all the other questions students have 59 00:04:24,720 --> 00:04:27,360 asked about the Welcome to HTML and CSS video. 60 00:04:28,790 --> 00:04:33,184 However, if you're posting a general question within the Community, 61 00:04:33,184 --> 00:04:36,437 you'll want to select a category for your question. 62 00:04:36,437 --> 00:04:41,721 Is it HTML? JavaScript? A design question? 63 00:04:41,721 --> 00:04:45,701 Choosing the best match will direct your question to the Treehouse 64 00:04:45,701 --> 00:04:48,340 users who are most likely to have an answer. 65 00:04:50,510 --> 00:04:54,493 As long as you leave the "Email me when someone replies to this 66 00:04:54,493 --> 00:04:58,275 discussion" option checked, you will receive an email 67 00:04:58,275 --> 00:05:02,320 notification when someone responds to your post. 68 00:05:02,320 --> 00:05:07,051 In addition, the bell icon in the upper right hand corner of the main 69 00:05:07,051 --> 00:05:11,450 Treehouse navigation will notify you when someone responds.