To start off, I must admit that the person who built this project took a picture that has great depth. But don't take a picture like this for a project post, take a picture like this for a seperate need.

---

First of all, it's a horrible idea to take pictures like this and post them in your project because you are showing off your PROJECT, NOT your texture pack! That's like when you are building a bowl of fruit and you add a person holding the fruit to make it better. The fruit bowl itself is really bad, but if you judge it with the person it makes it better. Same goes when you flip it, if you judge a project with no texture pack then it may be pretty bad, but remember, most people use the default texture pack. So when taking pictures, take pictures without your texture pack. That's the whole point of posting a project afterall--to let other people use it! Now that we got that out of the way let's move onto the post itself.

---

Primary Photo and Photo Gallery
Your project photos are one of the most important components of your project page. Photos grab the attention of your fans and viewers and help them understand your project.
Primary Photo Tips:

• One primary project photo is required
  
• Use high resolution photos of at least 1,024 x 768 pixels - the bigger, the better! (But remember 5MB photo is the largest the file size can get!)
  
• Photos must be in png or jpg
  
• The primary photo should be horizontally oriented
  
• Take photos closer up to your project, remember you are displaying the BUILD, not the skies or environment aorund it
  
• Use photos that are vibrant and expressive -- don't edit them very much though, remember -- the build!
  

Photo Gallery Tips:

• Display specific parts of the builds (Example: Kitchen, bedroom, bath, living room)
  
• Remember to make sure your photos resemble a purpose 
  

---

Project Title
Your title is the first thing that people see and will determine whether they will rush to click it and then keep reading about your project or move on to the next one. Make the project title clear, short, and descriptive. Convey what your project is in one phase that answers the following questions:

• Who is your project helping?
  
• How are you benefiting them?
  
• Why should they want to click?
  
• Why do you want to share it with people?
  

Tips:

• Your title should be about 4-8 words (40 characters, including spaces)
  
• Do not use acronyms - they can be difficult to understand
  
• Be consise and descriptive, don't be vague
  
• Use common, simple words that people are searching for online
  
• Lay down a questioning word that says "Oh, that sounds mysterious (legendary, horror.. etc)"
  

Examples of good titles - All of these titles are clear, consise and demonstrate a benefit

• Medieval House with Four Interior Rooms
  
• Small City with 50+ Fully Decorated Houses
  
• Fully Furnished 1 Room Home
  

Examples of bad titles

• House (too vague)
  
• I built this city for my school class, it has at least 1000 houses, 10 apartment buildings, and sustains a huge population of 12,000 people (too long and complicated)
  
• MMTIC--My medieval (too vague and acryonym is unclear)
  

---

Project Summary
The project summary, along with the project title is the second thing most people look at. It often serves as a basis of a decision to keep looking or not. This will appear below your images as well as in most online search results. Your summary should answer the following questions clearly:

• Who is your project helping?
  
• How are you benefiting them?
  
• What are you doing it for?
  
• How are you doing it?
  
• Who are you doing it with? 
  
• What problem are you solving?
  
• (Maybe even add a backstory to your project)
  

Tips: 

• Make sure your summary itself is 100-500 words (the backstory can be more if you decide to add it)
  
• Be concise and descriptive
  
• Avoid the use of acryonyms or jargon
  

---

What is the issue, problem, or challenge?
Use this section to give a more detailed explanation of what the community that you are addressing towards and exactly what the problem or challenge was that made you decide to make it. This section should answer the following questions:

• What challenges are you addressing?
  
• How does this problem impact the community?
  
• Did you make this project for fun & just sharing with the community?
  

Tips:

• Must be 200 words or less
  
• Use a statistic if you can find one
  
• Use simple terms to help people understand the problem, situation, or challenge
  

---

How will this solve the problem?
In this section, explain the activities the project will undertake in order to reach the expected outcomes or goals.
Tips:

• Activities section must be 200 words or less
  
• Write clearly and simply so that everyone can understand what you are trying to portray. For example: We build a small spawn that can help anyone who isn't great at building spawns and just needs a quick starter.
  
• Tie your goals and activities to your outcomes
  

---

Remember to thank your viewers
Once you make it to the end of your project description and story and all the information you have added, you should thank your viewers. Tell them how grateful you are for them and reading to the end. But remember not to beg for anything like diamonds, subscribers, or favorites -- nobody likes beggers.

That being said, I have to thank you guys so much, especially if you have made it this far. I must say, 60% of people leave halfway through. So thank YOU so much for reading. If you liked it let me know, I haven't tried a tutorial before and I think it went really well. Thanks again, this community is great and makes the things that people make happen!