Skip to content
Snippets Groups Projects
  1. Nov 30, 2020
  2. Nov 18, 2020
  3. Oct 17, 2020
  4. Oct 08, 2020
    • totten's avatar
      cli-cv.md - Rewrite as standalone page · 7b08a62a
      totten authored
      General themes/changes:
      
      * Rewrite as a standalone page. This was previously content in the D8 page.
      * Include the `curl ... cv.phar ...` command.
      * Move discussion of the `core:install` options and common problems into collapsed admonitions.
      * The "next level" docs for `cv core:install` are in the Dev Guide. Add links.
      * Add a section for "Configure the site".
      * Add a "Limitations" section.
      7b08a62a
  5. Oct 07, 2020
  6. Oct 05, 2020
  7. Oct 04, 2020
  8. Oct 01, 2020
  9. Sep 22, 2020
    • totten's avatar
      67af6769
    • totten's avatar
      Extract sub-section "Addenda" · 84fc5dc0
      totten authored
      OK, so you go through a bunch of steps and come to these instructions:
      
      > There should now be a CiviCRM link in your Drupal menu.  Click that link and
      > the CiviCRM Menu, Shortcuts, Search and New Individual Blocks should appear.
      > You can now explore CiviCRM end-user features and begin configuring CiviCRM
      > for your site/organization needs.
      
      This should be the end of the installation guide. But, if you skim the TOC,
      it keeps on going!
      
      I *think* what's going on here is that people wanted to add some sections
      which are sort of independent of the main flow of installation.
      
      These probably should be moved/referenced in some other way, but I don't
      really want to think too hard.  This commit just mitigates the confusion
      a bit by setting the subsequent sections (re:MySQL encryption and troubleshooting)
      under the heading "Addenda".
      84fc5dc0
    • totten's avatar
      9261edac
    • totten's avatar
      Simplify summary heading · 4ac7b897
      totten authored
      When the first heading of the document says...
      
      > "Scope of this guide and alternative installation methods"
      
      It breaks my English parser, and I start to cry. Just a little. On the inside.
      4ac7b897
    • totten's avatar
      Normalize special headings in WordPress page · 6a23c9dd
      totten authored
      1. Use sentence-case.
      
      2. There will have been less of the future-past-perfect.
      
      3. Conjugate actively.
      6a23c9dd
    • totten's avatar
      Normalize heading "Run the installer" (D8/D9) · 5f583bdd
      totten authored
      5f583bdd
    • totten's avatar
      Normalize heading "Run the installer" (BD/D7/J/WP) · 5c770b7a
      totten authored
      1. Use sentence-case per style-guide (all files)
      2. Don't need to explain every detail in the title (WP file)
      5c770b7a
    • totten's avatar
      Normalize heading "Review the checklist" · a4325874
      totten authored
      1. Title is more specific/wordy than it needs to be.
      
      2. Capitalizing the page title ("Configuration Checklist") is correct,
         but (as a reader skimming) it *looks* wrong because it doesn't match
         the norm and it lacks anything (quotes/italics/bold) to set it aside.
      
      Just use a plain noun instead of a proper noun.
      a4325874
    • totten's avatar
      Normalize heading "Troubleshooting" · c8669c47
      totten authored
      1. Resources in redundant.
      2. The other section headings have active verb-phrase. This is a little closer.
      3. The dash in "Trouble-shooting" is inconsistent. It's not wrong per se, but
         it's a little unusual, and it should be consistent with the title of
         liked page.
      c8669c47
    • totten's avatar
      Normalize heading "Synchronize the users" · df809452
      totten authored
      1. Use sentence-case
      
      2. Don't be so wordy.  The paragraph explains this stuff - you don't need
      to put the whole explanation into the TOC.
      df809452
    • totten's avatar
      d080c163
    • totten's avatar
      Normalize headings re: downloading code and translations · 455045cd
      totten authored
      Before:
      
      * Each CMS chapter uses slightly different headings and anchors
        for the same conceptual steps.
      * Several of them try to distinguish when you do/do-not need translations,
        but they're arbitrarily different.
      
      After:
      
      * Each CMS chapter uses the same headings and anchors.
      * If there was a different anchor before, then that anchor is still valid (but it is no
        longer visible or primary).
      * It still tries to distinguish when you do/do-not need translations, but
        the language is simpler and more consistent.
      455045cd
    • totten's avatar
      45583ad5
    • Seamus Lee's avatar
      Add install docs for drupal 9 now that the demo site shows it works · e52b9064
      Seamus Lee authored and totten's avatar totten committed
      e52b9064
    • totten's avatar
      requirements.md - Add a "Summary" section · 5b60a49f
      totten authored
      The list of requirements is hard to take in at a glance. This adds a section that
      you can read at a glance. It's obviously not as thorough as the main requirements,
      so it's only presented as a summary-recommendation.
      5b60a49f
    • totten's avatar
      Normalize line-endings · 1b28b587
      totten authored
      This repo currently has 16 markdown files, of which 8 have `CR` endings and
      8 have `CR-LF` endings.  For comparison, the dev-docs and sysadmin-guide
      have strictly `CR` endings.
      1b28b587
  10. Sep 18, 2020
  11. Sep 15, 2020
  12. Sep 13, 2020
  13. Aug 31, 2020
  14. Aug 11, 2020
Loading