Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Problem/Motivation
INSTALL.txt should be converted to Markdown, to match README.md. Also, they could probably do with a little make-over before going to beta. This issue is based on changes proposed in #2751397: Fix coding style to meet Drupal standards.
Proposed resolution
Convert INSTALL.txt to Markdown (and rename to INSTALL.md), review content of both files.
Remaining tasks
- Patch
- Review
- Commit
User interface changes
None.
API changes
None.
Data model changes
None.
Comment | File | Size | Author |
---|---|---|---|
#8 | interdiff_5-8.txt | 11.84 KB | philltran |
#8 | stage_file_proxy-cleanup_doc_files-2909440-8.patch | 7.4 KB | philltran |
#5 | stage_file_proxy-cleanup_doc_files-2909440-5-d8.patch | 9.66 KB | eelkeblok |
Comments
Comment #2
eelkeblokComment #3
eelkeblokThese are the changes as proposed by 'mfernea' and 'Pavan B S' in #2751397: Fix coding style to meet Drupal standards. Please credit them when commiting.
Here are my review points for these changes.
I agree with the conversion from H1 to H2. However, I feel upper case in markdown is not really needed (specifically because it doesn't look as nice when converted to HTML) and I prefer underline style headings for h1 and h2 because it does a better job of emphasising the heading when reading source.
If we are going to change this, I would suggest to introduce a single heading "Configuration", with subheadings for each of the configuration values. Specify whether the configuration is optional per sub-heading. That way, it is also possible to write a few words about configuring through the admin interface (this installation guide seems to be largely based on the installation procedure from the very first versions of SFP for D6/D7; the fact it is even possible is completely ignored).
Like I said, I'm personally no great fan of the hash syntax. Therefore I wouldn't say this is a necessary change (same for the other changes of the same nature).
I was going to say this is an issue (although it might have been an existing one), because the Markdown preview tool I'm using starts a new list from point 2. I've tried a few online ones (including John Gruber's original web dingus) and it seems to go fine there. Still,apparently it is an issue with certain parsers, so I'll see if I can get it to behave better.
Comment #4
eelkeblokRight. And the patch...
Comment #5
eelkeblokHere's two patches that implement my proposed changes. The second one takes things a step further, it integrates both files into README.md, since there was some redundant information in both and it doesn't seem really necessary to have two separate files.
Comment #6
eelkeblokComment #7
alonaoneill CreditAttribution: alonaoneill at Hook 42 commentedPatch has extra spaces that needs to be removed:
Extra spaces should be removed
Comment #8
philltran CreditAttribution: philltran commentedHere is a patch to update INSTALL.md. Looks like the README.md has been updated since patch #5. Since the README.md references INSTALL.md I went with keeping the two files separate versus merging INSTALL.md into README.md.
@alonaoneill I am not sure if I understood all of the extra spaces you pointed out. Please review and see if I missed something. Thanks.
Comment #10
philltran CreditAttribution: philltran commentedFailed automated tests... because there are none. Tagging this back as needs review.
Comment #13
gregglesAdding credit for folks.
Comment #15
gregglesI fixed the whitespace issues before committing/pushing.
Thanks everyone for your help with this!