Write content-create.txt

Great, thanks!

Before I can add this to the project, I need attributions/copyright information.

Also, several sections of this text file are empty. They either need to have something in them, which could be a "to do", or they need to be removed.

See
https://userguide-drupal.redesign.devdrupal.org/guidelines/guidelines.ht...
https://userguide-drupal.redesign.devdrupal.org/guidelines/formatting.html (section on "topic incomplete").

Thanks!

I would recommend at this early stage using @todo in all cases instead of removing sections. That way, future writers/editors won't need to (or need to remember to) re-add them.

Also, the "follow on" section should be for "if you want to learn more about this topic, check out..." type content, rather than the next set set of step-by-step instructions. Most of what's there now can be moved into the main section.

Good point on the "follow-on" section.

Regarding the @todo, it isn't too hard to add a section back, so really I would only put in @todo if you have something specific like "@todo Make a link to the ... section" (and ... hasn't been scoped out yet). But either way. ;)

We decided to use separate issues for each phase of writing/editing.

Hi @Pixiekiss, are you still working on this issue?

If so, on this other issue #2513514-13: Write content-edit.txt (comment #13, the attached file) there is a bunch of information that I think belongs in this topic.

Also, we have updated our guidelines on how to document how to fill out a form:

a) Make a screen shot
b) Make a table of values to fill in. See http://www.methods.co.nz/asciidoc/userguide.html#_tables

(See section 2.3.4 on https://userguide-drupal.redesign.devdrupal.org/guidelines/good-writing.... )

Hi! Are you still working on this? Hopefully yes -- if not, please comment here and let us know we need to find someone else. And if you are, do you know when you might finish writing this topic?

By the way... there have been quite a few updates to our processes since the sprint where you took this on. For one thing, we have a more concise guide to contributing (with links to specific instructions) on the project page:
https://www.drupal.org/project/user_guide

Also, the templates and some guidelines have changed, especially in the area of screen shots and images.

And we've finally made a complete outline for the guide! See
https://userguide-drupal.redesign.devdrupal.org/d8guide/en/index.html
to find your topic, along with its new template. We also put more notes about what each topic should cover in the tracking spreadsheet; see
https://docs.google.com/spreadsheets/d/1ov0FyJhKrJe7PYvohzV5UrrLyRaVCy2A...
for that.

Thanks!

Hi Agi! We still need to know whether you plan to continue working on this? You have disabled your drupal.org contact form, so I am unable to contact you by email... Please respond here. Thanks!

At this point, unless Agi responds, this issue is apparently open for someone else to work on.

Please attribute the original user as a writer, and start with the content that was attached above. Thanks!

Note: As of July 27, the "DripDocs" team is planning to work on this issue, so for anyone else, unless you have *really* strong desire to do it, if this date is not too far in the past, you might pick another topic. Thanks!

Adding checklist to summary

@lolk: Are you still planning to work on this topic? If so, do you have a time frame? If not, please unassign the issue so someone else can work on it. Thanks!

@jennifer: in progress, hoping to submit end of next week. grtz

Gonna give this a try.

Attributing

Attached a new version of the topic

Hi Boris,

thank you for taking this over.

As for the prerequisites, I have a suggestion, because I am putting this in " Configuring Content Translation" as well (and see if it can stay or is elsewhere explained and to be referred to). As an end user, once one gets through the idea of a "node", the next is the confusion on different uses of the word "content".

"The understanding that Content Types are a collection of Fields related to each other by an informational context, in which case the word Content is meant from a site architecture viewpoint as a general unit that is used to fill a framework. The understanding that these Fields have their own content, in which case the word content is meant as input or chosen value of a parameter. A Content Item is a one-time, unique piece of a certain Content Type. The https://www.drupal.org/documentation/modules/field-ui [“Drupal Community documentation on working with content types and fields“] quotes a simple metaphore on telephone contacts that helps settle this terminology. See further in <
>."

@Jennifer, what do you think of this?

We don't want to repeat information in multiple topics. We already have an explanation of entities, content types, etc. in the planning-data-types topic... which has been written. Can you see if you think it needs additional information?

https://userguide-drupal.redesign.devdrupal.org/d8guide/en/planning-data...

If you think that topic needs additional information, then please file an issue in the User Guide project and explain what it needs:
https://www.drupal.org/node/add/project-issue/user_guide

One thing: we definitely don't want to use the word "node" anywhere, except as the name of the "Node module". The Drupal UI doesn't use it, and that was done because it was confusing to people.

I'll review this topic latest iteration in a separate comment.

Some thoughts on this topic in its latest iteration -- first off, I think it's mostly great, thanks! A few things to address:

a) Prerequisite knowledge... I don't think we really need to refer to the planning-data-types topic as suggested above -- that is more information than is needed. But we do need to know about content-paths.

b) Goal: I think this is misleading. Just adding an alias for the home page does not designated it as the home page. The goal here is to create the content item, and the steps do not make it into the home page for the site.

c) Site prerequisites: Maybe just say you installed with a profile that includes a Basic Page content type? The content types stuff comes later in the Guide.

d) To save having a separate Guidelines Edit phase, you could fix the navigation mentions so that they follow our navigation guidelines:

https://userguide-drupal.redesign.devdrupal.org/guidelines/text-conventi...

Or you can leave this for later... but the first 3 steps could be combined into one navigation step following this guideline.

e) When creating the Home page, the body should be:

---
Welcome to City Market - your neighborhood farmers market!

Open: Sundays, 9 AM to 2 PM, April to September

Location: Parking lot of Trust Bank, 1st & Union, downtown
---

The subsequent lines are missing from the Steps.

@batigolix or @lolk, does one of you want to make the few/small requested changes and finish this off? Thanks!

On it

Fixed the points mentioned in #24

Thanks! Looks perfect now. Added to the guide source; will get it up on the site shortly.