Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use separate member files #13

Closed
stp-ip opened this issue Oct 23, 2017 · 0 comments · Fixed by #25
Closed

Use separate member files #13

stp-ip opened this issue Oct 23, 2017 · 0 comments · Fixed by #25
Milestone

Comments

@stp-ip
Copy link
Member

stp-ip commented Oct 23, 2017

Is this a BUG REPORT or FEATURE REQUEST?:
feature

What happened:
Currently all member data is stored in one file.

What you expected to happen:
Possibility to split up each member into their own file.

How to reproduce it (as minimally and precisely as possible):
Try adding members as their own file.

Anything else we need to know?:
Some ideas on structure.
Maybe the easiest is to reuse the fragment file name as sub path.
So when a fragment is called 1-hero.md the sub path for any fragment specifics is 1-hero/

For simple pages this could be simple as:

content/index.md
content/1-hero.md
content/1-hero/some-image.jpg
content/2-team.md
content/2-team/1-gopher.md

For more complex scenarios:

content/index.md
content/1-team.md
content/1-team/1-gopher.md
content/2-advisors.md
content/2-advisors/1-tiny-gopher.md
@stp-ip stp-ip added this to the 0.9.0 milestone Oct 24, 2017
@stp-ip stp-ip modified the milestones: 0.9.0, v0.10.0 Dec 8, 2017
@stp-ip stp-ip changed the title Optionally use member files Use separate member files Jan 27, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging a pull request may close this issue.

1 participant