nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Custom view for Share document library

unknown-user

Hi,

We would like to create a custom view for the Share document library similar to "Simple" and "Detailed" view. The requirement is to create a grid like layout.

Any inputs/ideas on the files to be modified are appreciated.

Thank You!

Find more posts tagged with

Comments

mitpatoliya

First you need to be aware of the share architecture.
It is based on the surf.
Then you need to learn how to create custom forms in the Alfresco share.
At last you can replace the existing form with your custom forms to customize those views.
Easy said not done

jpfi

Hi,
you won't need/use/customize Alfresco Forms here. But nevertheless it's going to be a hard task because you'll have to rewrite/overwrite Alfresco's YUI Component Alfresco.DocumentList in documentlist.js
Cheers,
Jan

mikeh

We're adding the ability to extend the Document Library with different layout renderers in HEAD right now. Take a look at r35186 for the first part of this work.

Thanks,
Mike

unknown-user

Thank you all for the quick response.

Mike - Do you know when this feature will be released for GA?

Thanks

mikeh

Mike - Do you know when this feature will be released for GA?

No, sorry - I don't have a date for the next Community release.

Mike

rdanner

Hi,

We would like to create a custom view for the Share document library similar to "Simple" and "Detailed" view. The requirement is to create a grid like layout.

Any inputs/ideas on the files to be modified are appreciated.

Thank You!

Do this as a Proof of Concept
in WEB-INF/classes/alfresco/site-data

pages folder create a page object (xml file), point it to a template instance
template-instance folder: create object (xml file), point it to existing or new template (ftl) file
Now in the template you will have regions. The regions point to components. Components can be defined in the page object or more often are individual files (xml files) stored in the components folder. name of each file contains the region and scope information.

Once you like what you have you can package these changes as an AMP. This will allow you to deploy your changes in to a clean copy of Share.

As Mike H. has pointed out, Share's ability to override regions and extend the platform is improving. The idea here is to try and avoid overwriting files that ship with Share which negatively impacts upgrades.