This repository was archived by the owner on Nov 21, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 7
Add list of content to the homepage #64
Merged
The head ref may contain hidden characters: "homepage-lazy\u2014teaser"
Merged
Changes from 42 commits
Commits
Show all changes
56 commits
Select commit
Hold shift + click to select a range
2be2d28
Add homepage
thewilkybarkid 2350dfc
Not there anymore
thewilkybarkid 75b044d
Update existing tests
thewilkybarkid ab67c94
Use specific exception
thewilkybarkid 17a3b37
Merge branch 'master' into homepage
thewilkybarkid 2a92d14
Merge fixes
thewilkybarkid ace03ab
Set HTML title using translations
thewilkybarkid 3f35854
Add homepage to integration tests
thewilkybarkid 087a021
Fix and test title
thewilkybarkid 24045d5
Merge branch 'master' into homepage
thewilkybarkid 7222c0c
Extract PageEvent
thewilkybarkid 4ebe45f
Merge branch 'master' into homepage
thewilkybarkid 9b8a204
Missed some cases
thewilkybarkid 572d5c3
Merge branch 'master' into homepage
thewilkybarkid 737ff95
Return type
thewilkybarkid 9880898
Tweak configuration
thewilkybarkid 1bc13dc
Improve name
thewilkybarkid f125fbb
Changes
thewilkybarkid 9c244af
Merge branch 'master' into homepage-lazy
thewilkybarkid 06b0ce8
Merge branch 'master' of github.com:libero/browser into thewilkybarki…
nlisgo e658709
Introduce pattern library teaser templates
nlisgo ee06b3f
Introduce teaser pattern
nlisgo 95516a4
Note to set route to content
nlisgo d8a1bb2
Adjust arguments handled
nlisgo 84a4228
Use teaser-list template
nlisgo 029a201
cs
nlisgo 91d628b
Update vendor-extra/LiberoPageBundle/src/EventListener/BuildView/Item…
thewilkybarkid 137582f
Add in paths
thewilkybarkid d65a080
Merge branch 'master' into homepage-lazy—teaser
thewilkybarkid abba688
Make canHandleTemplate parameter optional
nlisgo ef374e7
Get teaser list working
nlisgo 8844a0e
Merge branch 'homepage-lazy—teaser-new' of github.com:nlisgo/libero-b…
nlisgo 8bbaabc
Re-introduce lazy view
nlisgo 1a0c5fa
cs
nlisgo b67c520
cs
nlisgo 2666132
Pass only front for teaser listeners in JatsContentBundle
nlisgo 942b30e
Add tests for FrontArticleTitleTeaserListener
nlisgo 57280e9
Add tests for ItemTeaserListener
nlisgo b8bb328
Merge branch 'master' into homepage-lazy—teaser
thewilkybarkid 6fa6615
Update homepage test and support Libero content
thewilkybarkid abd30d3
Fix list and add test
thewilkybarkid 922cf53
Add tests
thewilkybarkid 30d382d
Update config
thewilkybarkid f3b6e6c
Tidy
thewilkybarkid 7c2310e
Not needed here
thewilkybarkid 0cdb625
Add title
thewilkybarkid b7ee7af
Merge branch 'master' into homepage-lazy—teaser
thewilkybarkid 5868bdb
Set levels
thewilkybarkid 39edf12
Put in grid and fix levels
thewilkybarkid 61e5820
Set empty text
thewilkybarkid 10177c5
Update
thewilkybarkid 3bb1391
Update
thewilkybarkid 56ec635
Fix terminology
thewilkybarkid c3d74a4
Simplify
thewilkybarkid 63f41a0
Split into three
thewilkybarkid 9605f3e
Missing assertion
thewilkybarkid File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -5,6 +5,7 @@ | |
| <meta> | ||
|
|
||
| <id>post1</id> | ||
| <service>blog-articles</service> | ||
|
|
||
| </meta> | ||
|
|
||
|
|
||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -5,6 +5,7 @@ | |
| <meta> | ||
|
|
||
| <id>article1</id> | ||
| <service>scholarly-articles</service> | ||
|
|
||
| </meta> | ||
|
|
||
|
|
||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,153 @@ | ||
| <?xml version="1.0" encoding="UTF-8"?> | ||
|
|
||
| <item xmlns="http://libero.pub" xmlns:jats="http://jats.nlm.nih.gov"> | ||
|
|
||
| <meta> | ||
|
|
||
| <id>article2</id> | ||
| <service>scholarly-articles</service> | ||
|
|
||
| </meta> | ||
|
|
||
| <jats:article> | ||
|
|
||
| <jats:front> | ||
|
|
||
| <jats:article-meta> | ||
|
|
||
| <jats:title-group> | ||
|
|
||
| <jats:article-title> | ||
| Article 2 y'all | ||
| </jats:article-title> | ||
|
|
||
| </jats:title-group> | ||
|
|
||
| <jats:article-categories> | ||
| <jats:subj-group subj-group-type="heading"> | ||
| <jats:subject>Evolutionary Biology</jats:subject> | ||
| </jats:subj-group> | ||
| </jats:article-categories> | ||
|
|
||
| <jats:kwd-group kwd-group-type="author-keywords"> | ||
| <jats:kwd>XML</jats:kwd> | ||
| <jats:kwd>Housestyle</jats:kwd> | ||
| <jats:kwd>eLife</jats:kwd> | ||
| <jats:kwd><jats:italic>formatting</jats:italic></jats:kwd> | ||
| </jats:kwd-group> | ||
|
|
||
| <jats:kwd-group kwd-group-type="research-organism"> | ||
| <jats:title>Research organism</jats:title> | ||
| <jats:kwd>Human</jats:kwd> | ||
| <jats:kwd>Machine</jats:kwd> | ||
| </jats:kwd-group> | ||
|
|
||
| </jats:article-meta> | ||
|
|
||
| </jats:front> | ||
|
|
||
| <jats:body> | ||
|
|
||
| <jats:sec> | ||
|
|
||
| <jats:title>Introduction</jats:title> | ||
|
|
||
| <jats:p>Fossil hominins were first recognized in the Dinaledi Chamber in the Rising Star cave system in | ||
| October 2013. During a relatively short excavation, our team recovered an extensive collection of | ||
| 1550 hominin specimens, representing nearly every element of the skeleton multiple times (Figure | ||
| 1), including many complete elements and morphologically informative fragments, some in | ||
| articulation, as well as smaller fragments many of which could be refit into more complete | ||
| elements. The collection is a morphologically homogeneous sample that can be attributed to no | ||
| previously-known hominin species. Here we describe this new species, <jats:italic>Homo | ||
| naledi</jats:italic>. We have not defined <jats:italic>H. naledi</jats:italic> narrowly based on a | ||
| single jaw or skull because the entire body of material has informed our understanding of its | ||
| biology. | ||
| </jats:p> | ||
|
|
||
| <jats:p>Order Primates LINNAEUS 1758</jats:p> | ||
|
|
||
| <jats:p>Suborder Anthropoidea MIVART 1864</jats:p> | ||
|
|
||
| <jats:p>Superfamily Hominoidea GRAY 1825</jats:p> | ||
|
|
||
| <jats:p>Family Hominidae GRAY 1825</jats:p> | ||
|
|
||
| <jats:p>Tribe Hominini GRAY 1825</jats:p> | ||
|
|
||
| <jats:p>Genus <jats:italic>Homo</jats:italic> LINNAEUS 1758</jats:p> | ||
|
|
||
| <jats:p><jats:italic>Homo naledi</jats:italic> sp. nov. | ||
| urn:lsid:zoobank.org:pub:00D1E81A-6E08-4A01-BD98-79A2CEAE2411 | ||
| </jats:p> | ||
|
|
||
| <jats:sec> | ||
|
|
||
| <jats:title>Etymology</jats:title> | ||
|
|
||
| <jats:p>The word <jats:italic>naledi</jats:italic> means ‘star’ in the Sotho language and refers to | ||
| the Dinaledi Chamber's location within the Rising Star cave system. | ||
| </jats:p> | ||
|
|
||
| </jats:sec> | ||
|
|
||
| <jats:sec> | ||
|
|
||
| <jats:title>Locality</jats:title> | ||
|
|
||
| <jats:p>The Dinaledi chamber is located approximately 30 meters underground, within the Rising Star | ||
| cave system at about 26°1′13′′ S; 27°42′43′′ E. The system lies within the Malmani dolomites, | ||
| approximately 800 meters southwest of the well-known site of Swartkrans in the Cradle of | ||
| Humankind World Heritage Site, Gauteng Province, South Africa. | ||
| </jats:p> | ||
|
|
||
| </jats:sec> | ||
|
|
||
| <jats:sec> | ||
|
|
||
| <jats:title>Horizon and associations</jats:title> | ||
|
|
||
| <jats:p>The present sample of skeletal material from the Dinaledi Chamber was recovered during two | ||
| field expeditions, in November 2013 and March 2014. | ||
| </jats:p> | ||
|
|
||
| <jats:p>Six specimens from an ex situ context can be identified as bird bones, and few fragmentary | ||
| rodent remains have been recovered within the excavation area. Neither of these faunal | ||
| constituents can presently be associated with the hominin fossil collection (Dirks et al., | ||
| 2015). | ||
| </jats:p> | ||
|
|
||
| <jats:p>Aside from these limited faunal materials, the Dinaledi collection is entirely composed of | ||
| hominin skeletal and dental remains. The collection so far comprises 1550 fossil hominin | ||
| specimens, this number includes 1413 bone specimens and 137 isolated dental specimens; an | ||
| additional 53 teeth are present in mandibular or maxillary bone specimens. Aside from the | ||
| fragmentary rodent teeth, all dental crowns (n = 179) are hominin, recovered both from surface | ||
| collection and excavation. Likewise, aside from the few bird elements, all morphologically | ||
| informative bone specimens are clearly hominin. In all cases where elements are repeated in the | ||
| sample, they are morphologically homogeneous, with variation consistent with body size and sex | ||
| differences within a single population. These remains represent a minimum of 15 hominin | ||
| individuals, as indicated by the repetition and presence of deciduous and adult dental | ||
| elements. | ||
| </jats:p> | ||
|
|
||
| <jats:p>The geological age of the fossils is not yet known. Excavations have thus far recovered | ||
| hominin material from Unit 2 and Unit 3 in the chamber (Dirks et al., 2015). Surface-collected | ||
| hominin material from the present top of Unit 3, which includes material derived from both Unit | ||
| 2 and Unit 3, represents a minority of the assemblage, and is morphologically indistinguishable | ||
| from material excavated from in situ within Unit 3. In addition to general morphological | ||
| homogeneity including cranial shape, distinctive morphological configurations of all the | ||
| recovered first metacarpals, femora, molars, lower premolars and lower canines, are identical | ||
| in both surface-collected and excavated specimens (see Figure 14 later in the text). These | ||
| include traits not found in any other hominin species yet described. These considerations | ||
| strongly indicate that this material represents a single species, and not a commingled | ||
| assemblage. | ||
| </jats:p> | ||
|
|
||
| </jats:sec> | ||
|
|
||
| </jats:sec> | ||
|
|
||
| </jats:body> | ||
|
|
||
| </jats:article> | ||
|
|
||
| </item> |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Been thinking about how to power the list on the homepage. eLife uses its search service, which is where our initial direction has been here. But that has been a bit problematic as it's not then easy for us to turn off search if needed (it'd be good to have a circuit breaker there). For Libero though, this needs to be a list of items. As it stands, the content API and search API lists are the same so can be interchanged (
scholarly-articlesis actually the name of a content service). Search will be expanded to allow filtering by type etc. If we are able to keep the basic definition of how lists work the same, then it's possible to use other things here (eg could be a dedicated list). Means the config here would be a path, as opposed to the name of a service. (To use a search service, would be the path include any query string parameters, which as it stands has to be configured somewhere else.)/cc @giorgiosironi
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done in 30d382d. There's already a mismatch in the dervied paths (a search service would be just
/{service-name}, whereas as content API is/{service-name}/items).