Which of the following statements are true about importing? Select every one that is true.

Select every option that is true, then check.

• Some libraries are not built into standard Python distributions and must be installed separately.
  Correct. Third-party libraries like Drafter are not part of the standard library; they come from a separate repository such as PyPI and must be installed before they can be imported.
• Imported functions cannot be called in user-defined functions.
  Not quite. The reading's calculate_area example calls the imported floor function right inside a function you define. Imported functions work like any other function.
• Imported variables cannot be read in user-defined functions.
  Not quite. The same calculate_area example reads the imported pi variable from inside a function you define.
• You must always test imported functions using assert_equals to make sure they work correctly.
  Not quite. Standard-library and well-established third-party functions are already tested by their maintainers; you don't need to re-verify them yourself before using them.
• Importing functions is pointless, because you can always just implement the function yourself instead.
  Not quite. The reading's whole point is the opposite: importing greatly increases the capabilities available to you without having to reimplement things like random number generation yourself.

Which of the following Drafter functions or components shown in the reading can be used to create or style page content? Select every one that is.

Select every option that comes from Drafter and shapes what a page shows, then check.

• bold
  Correct. bold styles its text argument, as in the reading's "Bolder Text" section.
• italic
  Correct. italic is one of the styling functions introduced in "Composing Functions".
• change_color
  Correct. change_color changes the color of its text argument, also from "Composing Functions".
• Page
  Correct. Page creates the web page with the specified content; every route in the reading returns one.
• Div
  Correct. Div is a component that arranges its children in a line, used in "Multiple Lines of Content".
• randint
  Not quite. randint comes from the standard library's random module, from earlier in this same reading; it has nothing to do with Drafter or page content.
• floor
  Not quite. floor comes from the math module, used earlier in this reading to compute an area; it does not create or style page content.

Which of the following function calls use Drafter functions in ways demonstrated in the reading? Select every one that is.

Select every call that matches how the reading actually uses that function, then check.

• bold("Hello")
  Correct. bold takes a single piece of text to style, exactly as in "Bolder Text".
• italic("Hello")
  Correct. italic also takes a single piece of text, as used in "Multiple Lines of Content".
• change_color("Hello", "blue")
  Correct. change_color takes the text first and the color second, matching "Composing Functions".
• Div(italic("This"), " is ", bold("exciting!"))
  Correct. This is the exact call from "Multiple Lines of Content".
• bold("Hello", "blue")
  Not quite. In the reading, bold is only ever called with a single argument; a color is not part of how it's demonstrated.
• change_color("blue")
  Not quite. The reading always calls change_color with both the text and the color; a single argument doesn't match that.

from drafter import *

@route
def index() -> Page:
    return Page(bold("Welcome!"))

start_server()

Select one answer, then check.

• True
  Correct. This is exactly the "Bolder Text" example: a route decorated with @route that returns a Page wrapping bold("Welcome!").
• False
  Not quite. This follows the exact pattern from the reading: a @route function returning Page(bold(...)), with start_server() called at the end.

from drafter import *

@route
def index() -> Page:
    bold("Welcome!")
    return Page("Welcome!")

start_server()

Select one answer, then check.

• The bold function only works inside a Div component.
  Not quite. "Bolder Text" passes bold(...) straight to Page, with no Div involved.
• The result of bold("Welcome!") is ignored instead of being passed to Page.
  Correct. Calling bold("Welcome!") on its own line does nothing with its result; the return statement builds its own, separate, unstyled string to hand to Page.
• A Page cannot contain a string directly.
  Not quite. "Simple Drafter Site" returns Page("Welcome to my Drafter site!") with a plain string, so this works fine.
• The @route decorator must appear below the function definition.
  Not quite. Every example places @route above the def line, exactly as it is here.
• start_server() must be called before the route is defined.
  Not quite. Every example calls start_server() last, after the route is defined, just like here.

According to the simplest Drafter example in the reading, which of the following are required for that minimum program? Select every one that is required.

Select every option the simplest example actually contains, then check.

• The from drafter import * line
  Correct. Even the simplest example, "Drafter Example", starts by importing the module.
• One call to start_server()
  Correct. "Drafter Example" is only two lines: the import, and a call to start_server().
• A function decorated with @route
  Not quite. The simplest example has no route at all; routes only appear starting with "Simple Drafter Site", which customizes the default page.
• One call to Page
  Not quite. Page only shows up once a route is defined; the simplest example has neither.
• One call to Div
  Not quite. Div only appears once content has multiple parts to arrange, much later than the simplest example.
• At least one assert_equal test
  Not quite. Tests are optional and only appear in "Drafter Tests", well past the simplest example.