Anti-Cheat is a mod that has been accepted by Feng Lee as one of the usable mods. The real mod can be found here. These walls keep out strange man-eating creatures called Titans. One day, the wall is broken and Titans flood into the outer area of the country. In AoTTG, you get the option of creating your own character or choosing to play as one of the main ones. The game has a cute, chibi style to the characters and Titans. Areas in the game include the forest, Trost, and atop the wall where you face the horror of the Colossal Titan.
The tallest in the series, the Colossal Titan is feet tall and provides a challenging fight for players that have learned to control their 3-D Maneuver Gear. Players can choose to control fan-favorites, such as Erin.
His unique ability will turn him into a Titan just like in the anime. Levi, Petra, and Mikasa all have their signature moves where they spin ferociously, cutting through other Titans.
You play AoTTG in your browser, but there are versions available for download on alternative websites allowing you to play offline. We mentioned the libraries and their versions earlier. If necessary, technologies, launch, and hardware requirements can be merged together. But if we split it into two subsections, it's worth to focus here specifically on launching a project.
When we have a website or application, it can concerned setting up a local environment, a link to GitHub pages or deployed application on Heroku. Do we need input data? If so, in what format? Table of contents comes in handy in case of extensive documentation. It can work as a simple list with the links to headings. GitHub automatically adds id to headings according to the content inside a tag spaces will become a sign '-'. It enables to create a simple table of contents, e.
A technical documentation doesn't need to be pretty but legible and understandable. The illustrations aren't necessary - nevertheless, they can aesthetical value to our project. You can show an application's logo, diagrams, schemes, exemplary screenshot. Maybe an illustrated manual is something you want? Create a file in your repository, and add an image there. Use a file path to display it using:! I keep my schema. To display it in my documentation, I will use a code:.
There's no always use in describing the scope of functionalities. For a website-visiting card or a simple application of to-do type, the list of functionalities is an excess of form. On the other hand, a seemingly simple project such as to-do list can be extended with many interesting options we can be proud of: users register, recording and classifying the tasks according to date, adding commentaries to the tasks or data export to the files.
In case of reusable code or your own library, providing a manual how to use our project might be necessary. It can work as a fragment of code:. It's worth to add a project status - especially if the project is still being developed. If it's our library, let's mention planned changes, direction of development or to emphasize we're done with its development.
Should we add information when our project was based on a tutorial or we got inspired with a given task? Yes, sure. I don't get the doubts in that matter. There's nothing embarassing in the fact that we learn from various sources and we document our progress.
We complete many tutorials, choose learning material. A thoughless copying without providing changes in it - and without learning at all - mostly doesn't happen. Maybe we use an old tutorial - for example, we write an application with Rails 3 tutorial. From scratch, in accordance with Rails 5 version, using new framework mechanisms. Certainly, it's worth mentioning here. When we solve the sets of exercises, it's worth adding where others can find their description.
If we will want to come back to these sources, the link will come up easily. Information on the author, contact, www and social media links, a type of license under which the code is made available or the information on how to contribute to a project - these are only the examples of what can be added to your project.
The suggestions above are mine. The most importaint point is just legibility. A thorough documentation make your repository shine in front of the recruiters and other programmers.
Take a look at the following examples:. I doubt the code is just for you. In Polish or in English? Make sure the file always includes the following elements: Titles and internal titles Introduction - the project's aim Technologies Launch Consider also using additional elements such as: Table of contents Illustrations Scope of functionalities Examples of use Project status Sources Other information That's a lot!
There's not so much to say about my project! There is - but you're not aware of that already. Titles and internal titles A title should explain clearly what we have here, and it's usually a project's name - a H1 heading prefaced with. Technologies Let's write down the languages we used, the libraries and its versions. For example: Bootstrap 3 or 4 AngularJS 1.
Launch How to run a project? Table of contents Table of contents comes in handy in case of extensive documentation. To display it in my documentation, I will use a code: Scope of functionalities There's no always use in describing the scope of functionalities. Examples of use In case of reusable code or your own library, providing a manual how to use our project might be necessary.
It can work as a fragment of code: which will be displayed as: The project status It's worth to add a project status - especially if the project is still being developed. Sources Should we add information when our project was based on a tutorial or we got inspired with a given task? If our code was based on somebody else's code, we should add such information.
Other information Information on the author, contact, www and social media links, a type of license under which the code is made available or the information on how to contribute to a project - these are only the examples of what can be added to your project. Take a look at the following examples: Node-chat — a simple description, screenshot of the application, examples of use WebApp — a splendid example of description provided for a landing page type of website and application using API.
0コメント