引導式測驗 · 中等 等級

技術作家人工智慧測驗

測試 AI 輔助文件:使用 Vale 和 CI 進行文檔即程式碼、Diátaxis 內容類型、測試程式碼範例以及編寫用於 AI 檢索的文檔。

相關引導路徑技術作家的人工智慧
問題 1 的 8

Vale linter 在文件即程式碼工作流程中做什麼?

預覽每個問題8 問題

當您參加測驗時,就會出現答案和解釋。

  1. Vale linter 在文件即程式碼工作流程中做什麼?
    • Generates API reference pages from code
    • Hosts the documentation website
    • Checks prose against style-guide rules and gives the same result every time
    • Translates docs into other languages
  2. 什麼最能描述文檔即程式碼?
    • Documentation kept in version control and reviewed and built like code
    • Writing documentation only inside code comments
    • Using AI to write all docs automatically
    • Publishing documentation as PDF only
  3. Diátaxis 框架區分哪四種內容類型?
    • Blogs, emails, slides and videos
    • Tutorials, how-to guides, reference and explanation
    • Drafts, reviews, approvals and archives
    • Beginner, intermediate, advanced and expert
  4. 為什麼人工智慧產生的程式碼範例應該作為測試運行?
    • Tests make pages load faster
    • Search engines require tested code
    • Testing replaces the need for a style guide
    • Models can invent plausible parameters or flags, and tests catch them before readers do
  5. llms.txt 提案是什麼?
    • A suggested file that points language models to a site's key documentation
    • A legal license for AI training
    • A style guide published by Microsoft
    • A required format for all API specs
  6. Which writing practice helps AI assistants that retrieve documentation?
    • Long pages with no headings
    • Frequent references like 'as mentioned above'
    • Self-contained sections with descriptive headings and explicit product names
    • Putting all content in images
  7. How was API reference documentation commonly produced before generative AI?
    • It was always written entirely by hand
    • It was generated from specs or code comments with tools such as Swagger UI, Redoc or Sphinx autodoc
    • It did not exist
    • It was produced by speech recognition
  8. According to the guide, where does a technical writer add the most value alongside AI?
    • Typing faster than the model
    • Avoiding version control
    • Removing all human review
    • Checking accuracy, deciding what users need and structuring information