Writing Blog Posts
The following questions will help you review this chapter for the essential topics for better learning success.
First, answer the questions on paper. Before you look up an answer, take some time to answer the question yourself. If you find it challenging to find the correct answers, refer to the previous sections.
Clicking the link on the question number will open a new page (tab) in your web browser and point you to the answer. This page helps to navigate to the questions by a table of content (TOC). Go for the question number or the chapter title.
|If you finished the questions section, you could close the browser windows (tabs) opened for answers or questions and continue on this page for the next section.|
A lot you’ve learned, time to summarize what is in behind. The last chapter Summarize! should help on that. Summarize! offer some handy sections to remember what was presented, giving an outlook what could be done next. This section provides an overview on all chapters this tutorial and finally useful links to read more.
See all sections below:
Recap — What has been done, what’s explored in current section
Whats Next — Find to go further, what’s planned next
All Chapters — The full chain, all chapters
Further Reading — List of helpful links to get more
Again, a chapter full of hard stuff, You learned, a website managed a J1 is a project. Creating J1 projects is done by the CLI j1, part of the Ruby GEM j1-template.
You have compared some folders on the source and destination of a J1 project. Jekyll is a tricky thing, as you’ve seen for a closer look what the engine is doing. Document types and classes in the sense of the builder engine are important to know to understand the different behavior outputting a web to a destination.
J1 is a GEM-based template. Nice, but this has consequences! It should be much more understandable, not in all details, what the reasons are why some resources of a web can be found on the destination but not available with the project on a source-level.
J1 projects managed by a NodeJS project manager. The preferred manager tool is yarn. The manager tool yarn is used for all project-related tasks like setting up, running, or rebuilding a web. Find a summary of the tools and tasks in the table below.
| || |
Creating a J1 project is done by the CLI j1, provided by the (Ruby) GEM j1-template. The task
| || |
For managing a J1 project, the (NodeJS) project manager yarn is used. Make an initial scaffold for a project a usable website, a project has to be initialized first.
| || |
Running a website out of a J1 project, the project manager yarn is started by the task
| || |
If making changes to the global configuration, a website needs to be re-created. To rebuild a website from scratch, the (NodeJS) project manager yarn is called for the task
Well done, folks! You managed to create a J1 project and run your first web.
Take some time to relax, save energy for the next!
The following chapters focus on content creation, explain how to write posts and pages using J1. These sections discuss the writing and the use of the markup language Asciidoc for your content.
Make your website real!
Continue on next section to create pages on your own: Writing Articles!
Find here an overview on all chapters this tutorial.
Find from here some interesting links to additional sources of information for further reading. It’s not needed to go for all the pages, but the links will give some more background provided by other people, what they do, and what other experts have on their minds.