Tutorial #1: Let's make a new pages block
Now let's make a block for new pages.
To add views, you modify one of the default views.
These instructions are for 4.7
administer -- views
go down to default views
look at the row called tracker, click "add"
click on "Provide Page" to turn it off
click on block to expand the menu
click "Provide Block" to put an x in the box
Leave it on "List View"
Put "New Pages" in for title
Put in "10" for "Nodes per block"
Click on "More" to put an x in the block
Now we will pick the fields.
The default view for tracker comes with 5 fields.
We only want the title field, so we'll put the other 4 fields in the trashcan.
Click the trashcan icon on the row for node type "Type"
Do the same for "Author," "Replies," and "Last Post"
Now for the one field remaining called "Title," erase the word "Title" from the box called "Label" so the word does not appear 10 times in your block.
Click Save.
Go to administer -- blocks.
Look under the section for disabled blocks.
Find one called "New Pages"
Click the box to enable it
Give it a weight of -10 by clicking on the down arrow next to the number
(The -10 means it will be at the very top)
Leave it on "left sidebar"
Click on "Save Blocks"
Congratulations. You should now have a new block called "New Pages" on the left side of your website.

Comments

cel4145’s picture

cel4145 commented

Was there some reason you didn't want to submit this page directly to the handbook? If so, it helps everyone else if you explain why the documentation was submitted here (so no one has to ask and then you have to respond anyway). Know that drupal.org site members can submit pages directly. The easy way to do it is to visit the page that you would choose as the parent and then select the "Add child page" option.

drupalec-1’s picture

drupalec-1 commented

Thank you for asking.

http://drupal.org/node/339 says
Rough drafts of new pages or edited pages which are not production ready--i.e., need feedback and/or additional development--should first be submitted as an issue to the Documentation project.

It seemed like the two tutorials may not be correctly formatted, or otherwise need to be edited. For example, they refer to the "New Pages Block" on this website, which means the drupalecommerce.com website. Had thought the preference is for pages to be submitted as issue first.

drupalec-1’s picture

drupalec-1 commented

Also, this is written in a different style and more informal way than the rest of the handbook pages.

cel4145’s picture

cel4145 commented

Not at all. Pages can be posted directly. If you want assistance with a draft, then this can be a convenient venue. Also, until the collab book permissions are reset for 4.7, users can only edit pages they create (this should hopefully be reworked soon on drupal.org). So if you are trying to edit an existing page that someone else wrote, you would need to post the text here and then one of the moderators can post it.

Meanwhile, what questions do you have about formatting? The handbook pages are generally formatted in HTML, but as you see from looking at the different pages in the handbook, nothing too complex. The only pages which have very extensive guidelines are the top page for each module in the Drupal modules and features section (and the contrib section of that) as they are used to create the help text in Drupal.

drupalec-1’s picture

drupalec-1 commented

Thank you. Do you want these 2 submitted directly as child pages to the views module then?

cel4145’s picture

cel4145 commented

That seems like a good spot :)

drupalec-1’s picture

drupalec-1 commented

Done. They are at 59157, 59158, 59159. They seem to be invisible right now, but perhaps they have to be approved to be visible. Please feel free to edit as you see fit.
:)

cel4145’s picture

cel4145 commented

Right. And they should be formatted in HTML when using lists. Sorry, I didn't get to it until now. If you can use HTML to format your handbook pages, they can be approved more quickly.

I also modified the pages so as to include the description about the tutorial with the tutorial instead of on the tutorial intro page. Generally, a best practice for documentation writing is to include a short description of what a tutorial is about at the top of the tutorial itself.

drupalec-1’s picture

drupalec-1 commented

cel4145,
thank you. One thing that is confusing is that 59159 does not show up as a child page of 59157, even though the parent of 59159 is 59157. It does not seem to be linked to the other 2, even though the parent is set correctly.

cel4145’s picture

cel4145 commented
Status: Active » Fixed

Sorry. I must have not have unmoderated that one after formatting.

drupalec-1’s picture

drupalec-1 commented

Thank you.

cel4145’s picture

cel4145 commented
Status: Fixed » Closed (fixed)

finished, so marking closed.