Consider merging github.com/larowlan/default_content as Drupal 8 solution

+1 here!
And next issue would be - consider ship default content with core 8.x ;)

+1 on this!

+1, it says on the project page that this module is deprecated, maybe it's no longer supported?

According to this comment the default_content maintainer is putting all his efforts into UUID features.

I closed #1869366: Future Plan as duplicate because there's 8k usage for 7.x so "future depends on a way how module namespace would be used and migrate path...

PS: +1 to make @larowlan a active maintainer! So maybe we need just update project page and file the issue?

I've written my own d8 module which both exports nodes to a config entity and imports them back, automatically, if it is enabled during site installation.
This proposed default_content available on git hub seems not to export, and depends on 'hal' module which not on drupal.org.
I would like to post my module here, but the previous maintainer seems to have gone away...

hal is in core and default_content exports just fine, through drush commands or REST requests (it's the same output as that uses).

Ah good. Might be worth somebody picking the best bits from each.
I'm struggling to make the drush export work - what's wrong with this:drush default-content-export node 1 --file src/default_content/welcome.json
maybe you can improve the readme?

Just to confuse things further: https://www.drupal.org/project/default_content

I'm not being precious about this module.
I just needed it once to build an installation profile.
I was given the maintainership,
I integrated a lot of code from the earlier version.
Now it works for me.
Somebody else welcome to take over.

Nobody is criticizing you, don't worry.

We made the decision to keep the name for default_content and therefore chose to release it on https://www.drupal.org/project/default_content.

It would be great if you could start a related projects chapter on the project page and mention that module and what the main difference is, nothing else left to do here.

Now i'm more confused.
There is an 8.x branch of defaultcontent as well as default_content.
They are very similar.
Are you saying we should be using the 8.x branch of default_content instead?

I'm just trying to figure out where the active work is happening.

@larowlan's default_content project *is* https://www.drupal.org/project/default_content.

This is a different project with a completely different architecture/approach.

default_content will very likely continue to be maintained by @larowlan and others, it is the project I am using too. What will happen with this project, I don't know. Might more might not be maintained actively.

This is a different project with a completely different architecture/approach

What?
The README files are 100% identical:
http://cgit.drupalcode.org/defaultcontent/tree/README.md?h=8.x-1.x
http://cgit.drupalcode.org/default_content/tree/README.md?h=8.x-1.x
The directory structure is very similar, down to the file and classnames.
The drush command to export content is the same.
Looks to me like they both started from larowlan's sandbox project and diverged from there.

Not a criticism, just trying to sort out which project is more current and has momentum and support.

Suppose there should be an issue "provide upgrade path from d7 defaultcontent module"

I started the d8 upgrade of defaultcontent myself.
Then I saw a link the github project.
Then I integrate the github with my own code - especially the whole serializing business.
If the github has been copied back to default_content that would explain why both projects are so similar.

This doesn't seem to be resolved. It would be good if a clear resolution between the projects was posted.

@FatherShawn please file new issue if comment #18 is not clear enough