Synopsis
The purpose of this module is to export Drupal 8 nodes in the form of Markdown files. The principal objective behind this module to facilitate the JAMStack based architecture where decoupling of Drupal (from its presentation layer) is required.
This module can generate markdown files in both online and offline(via drush command) mode and these files will be stored under files directory.
Requirements
Markdownify is a packagist repo, which helps to convert html to markdown
Recommended modules
NA
Roadmap
* D8 module should have the Markdownify as composer based package
* BitBucket API to integrate
* All field types to match, reference fields are yet to be done
Known problems
Reference fields are not converting
Pledges
Cheerful that the project will be ready in Drupal 8 and will be helpful to developers working in JAMstack
Credits
* Ramit Mitra actually published the project with all todos completed
* Samajit Das started the project with an idea behind JAMstack
Project link
https://www.drupal.org/project/markdown_exporter
Git instructions
git clone --branch 8.x-1.x https://git.drupalcode.org/project/markdown_exporter.git
PAReview checklist
* 7.x: https://pareview.sh/pareview/https-git.drupal.org-project-markdown_expor...
* 8.x: https://pareview.sh/pareview/https-git.drupal.org-project-markdown_expor...
Comments
Comment #2
vernitComment #3
vernitThere are lots of issue occurs while PAReview. Please resolve all of them. Thanks in advance.
Comment #4
vernitComment #5
avpadernoA review should not simply report there are issues to fix, but also give a short description of what those issues are.
Comment #6
avpadernoOn the project used for this application, there are 14 commits done from ramit.mitra and 7 done from aniruddhab (for the 8.x-1.x branch).
Since the purpose of these applications is verifying what the user who applies understands about writing secure code that correctly uses the Drupal APIs and follows the Drupal coding standards, we cannot review code written from more users to understand what a single user understands of writing Drupal code.
If you want to become a vetted user who can opt into security coverage for the maintained projects, you need to apply using a project/branch where you committed most of the code, if not all.
Comment #7
aniruddhab commentedHi @kiamlaluno,
The branch 8.x-1.x is a branch where I only have committed. So please check commit on a single branch and let me know issues are getting.
Thanks,
Aniruddha
Comment #8
aniruddhab commentedHi @Vernit,
I am working on the PAReview issues.
Thanks,
Aniruddha
Comment #9
avpadernoComment #10
avpadernoActually, for the 8.x-1.x branch there are commits from other users too, for example in markdown_exporter.drush.inc. We cannot review a project for which it is necessary to check every commit to understand exactly which user has done each change.
If the purpose of these applications were to check the code quality, we would not care of which user changed the code. The purpose of these applications is instead understanding what the user who applies understands on writing secure code that follows the Drupal coding standards, and correctly uses the Drupal APIs, which means we do care of which user wrote the code.
Comment #11
aniruddhab commentedHi @Vernit,
Check the PAReview list once: https://pareview.sh/pareview/https-git.drupal.org-project-markdown_expor...
Thanks,
Aniruddha
Comment #12
aniruddhab commentedHi @kiamlaluno,
The file has been removed. I guess the branch is clean now, you need to review once.
Thanks,
Aniruddha
Comment #13
aniruddhab commentedComment #14
aniruddhab commentedComment #15
batkorhi
Where drush commands? :-)
Please correct construct method in
https://git.drupalcode.org/project/markdown_exporter/blob/8.x-1.x/src/Fo...
must
Use Json:decode instead
json_decodeComment #16
aniruddhab commentedIssue #15 has been updated, please check
Comment #17
ankush_03Hi aniruddhab,
Remove commented code from routing file
# markdown_exporter.github_auth_modal:
# path: '/admin/config/development/markdown_export/github-authentication/modal-open'
# defaults:
# _form: 'Drupal\markdown_exporter\Form\GitHubAuthModal'
# _title: 'GitHub Authentication'
# requirements:
# _permission: 'administer site configuration'
Service file :
services:
# markdown_exporter.entity_schema_subscriber:
# class: Drupal\markdown_exporter\EventSubscriber\MarkdownExporterEntitySchemaSubscriber
# arguments: ['@entity.manager']
# tags:
# - { name: 'event_subscriber' }
# core_file_system:
# class: Drupal\core\File\FileSystemInterface
# Drupal\core\File\FileSystemInterface: '@core_file_system'
Comment #18
avpadernoPlease remember to change status when the project has been fixed as per reviews.
Comment #19
aniruddhab commentedankushgautam76@gmail.com, commented code has been removed, please check
Comment #20
aniruddhab commentedupon all such changes, I am wondering, when all those issues will be fixed, and project actually goes live....
Comment #21
shaktikThere are some coding standards issues to be fixed in the README.md file.
Comment #22
avpadernoComment #23
aniruddhab commentedComment #24
aniruddhab commentedIssues reported in this process, are fixed by RC
Comment #25
aniruddhab commentedComment #26
aniruddhab commentedComment #27
avpadernoComment #28
klausiAlthough the module will probably not run on Drupal 8 because it might have some fatal errors (because variable_get() dores not exist) I don't see security issues.
Thanks for your contribution, Aniruddha!
I updated your account so you can opt into security advisory coverage now.
Here are some recommended readings to help with excellent maintainership:
You can find lots more contributors chatting on Slack or IRC in #drupal-contribute. So, come hang out and stay involved!
Thanks, also, for your patience with the review process. Anyone is welcome to participate in the review process. Please consider reviewing other projects that are pending review. I encourage you to learn more about that process and join the group of reviewers.
Thanks to the dedicated reviewer(s) as well.
Comment #30
aniruddhab commentedComment #31
aniruddhab commentedCan anyone please help me to reopen the issue, I am one of the maintainer, still can not change the status.
Comment #32
klausiYou have the git vetted user role, so everything should be ready for you to opt into security coverage in your project. Can you set the option when you edit your project at https://www.drupal.org/node/3055800/edit ?
Comment #33
aniruddhab commentedhi klausi, first of all many thanks. I can see the opt in option in edit page. Also I have joined in to the group of reviewers.
However the issues you mentioned in #28, I am working on along with Drupal 9 compatibility with Drupal-checker.
Comment #34
klausiNice, then I think we can close this again.