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

Create a content adapter (content from /data; content from sql) #4485

Open
bep opened this Issue Mar 9, 2018 · 3 comments

Comments

Projects
None yet
3 participants
@bep
Member

bep commented Mar 9, 2018

I was pretty sure we had an issue for this, but I cannot find it.

  • It would be good as part of this to create a better abstraction for the "page source".
  • It should be possible to merge /data with matches in /content (to provide long text markdown etc.)

A cool prototype for this would be a product catalogue, see:

https://mrjoe.uk/product-page-template-sketch/

@bep bep added the Enhancement label Mar 9, 2018

@bep bep added this to the v0.39 milestone Mar 9, 2018

@kaushalmodi

This comment has been minimized.

Member

kaushalmodi commented Mar 9, 2018

This: #140

@bep bep changed the title from Create pages from /data to Create a content adapter (content from /data; content from sql) Mar 12, 2018

@bep

This comment has been minimized.

Member

bep commented Mar 12, 2018

I have updated the title to hint at a more general design.

If we make today's "reading files from /content" a Filesystem Content Adapter, then we can add:

  • Adapter for /data
  • Adapter for SQL databases

If we also manage to abstract away the change notifications from the files, we could have similar live reload functionality for databases via polling.

Note that since we still want this to be fully static, we have to create some kind of intermediate file representations, so this can still be built by Netlify etc. without access to the database.

I'm not sure what the scope of this particular issue will be.

@bep bep modified the milestones: v0.39, v0.40 Apr 9, 2018

@bep bep modified the milestones: v0.40, v0.41 Apr 20, 2018

@bep bep modified the milestones: v0.41, v0.42 May 4, 2018

@bep bep modified the milestones: v0.42, v0.43 Jun 5, 2018

@bep bep modified the milestones: v0.43, v0.44 Jun 30, 2018

@bep bep modified the milestones: v0.44, v0.45, v0.46 Jul 10, 2018

@bep bep modified the milestones: v0.46, v0.47, v0.48 Aug 3, 2018

@bep bep modified the milestones: v0.48, v0.49 Aug 22, 2018

@bep bep modified the milestones: v0.49, v0.50 Sep 13, 2018

@bep bep modified the milestones: v0.50, v0.51 Oct 6, 2018

@bep bep modified the milestones: v0.51, v0.53 Nov 8, 2018

@anagrius

This comment has been minimized.

anagrius commented Nov 19, 2018

This would make Hugo so much easier to use for documentation pages and any page that has a very large number of pages. +1

@bep bep modified the milestones: v0.53, v0.54 Dec 6, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment