TECHNOLOGY · LIFERAY
A corporate portal has a lot of content and little visibility.
On Liferay much of the valuable material lives behind a login, spread across portlets and separate sites. The work starts by deciding what should be public and how it's served.
Let's talk about your project- +15
- years working visibility for large brands
- +200
- projects with our own data behind them
- 48 h
- to reply, at most
Brands that have trusted Laika
Some of these situations may sound familiar
The useful content sits behind a login
Prices, documentation or help nobody can find from outside.
Each portlet generates its own addresses
Long parameters, states and pages repeating with small variations.
There are several sites inside the same portal
By country, brand or business unit, with overlapping content.
Metadata is filled in by hand, or not at all
It depends on who publishes and which template they use.
Nobody measures what happens to the public content
It gets published because it has to be, with no idea whether anyone finds it.
The scope
We review site and page structure, public versus gated content, portlets, URL generation and metadata, and give publishing rules several teams can follow.
We work on the judgement and the spec: what needs to change on Liferay, in which order and how it gets checked afterwards. Your team or your development partner implements it, and we review that what reaches production is what was agreed.
The areas of work
Four fronts that come up again and again on Liferay projects. Depending on where your project stands, some weigh more than others.
What's public and what isn't
Surface what can attract and protect what should stay inside.
See the detail
- Content inventory by access level
- Criteria on what to open and how far
- Public versions of internal content
- Control of what gets indexed by mistake
Portlets, URLs and states
Clean addresses and correct responses in every state.
See the detail
- Review of URLs generated per portlet
- Parameters, duplication and canonicals
- Response codes and redirects
- Pagination and listings
Sites, languages and overlaps
Give each site a purpose without subtracting from the others.
See the detail
- Map of sites and shared content
- Language and country signals
- Content that must differ
- Merge plan where there's repetition
Publishing and governance
Keep order with several teams publishing.
See the detail
- Templates with generated metadata
- Short publishing guide by role
- Review criteria before publishing
- Measurement of public content
Who does it?
A small team with real hours inside Liferay. MJ leads the strategy and the specialist who reviews your platform is the one who explains it to you.
Why Laika?
Knowing the platform changes the conversation: you stop arguing about whether something is possible and start deciding when it ships.
We've worked on Liferay projects long enough to know where its real limits are and what a second pass at configuration can solve.
We know how to read a portal with many owners
The challenge isn't technical: it's agreeing who publishes what, and with what criteria.
You always talk to whoever decides
There's no management layer between you and the judgement. MJ leads the strategy and the specialist team executes.
If we're not the right fit, we say so
Even if that means there's no project for us, we'd rather say so before signing.
Frequently asked questions
Can you do SEO on a corporate portal?
Yes, starting by deciding which content deserves to be public. That's where most of the margin is.
Do we need the platform team?
Yes, for anything touching URLs and templates. Much of the content work is resolved without them.
Do you work with content in several languages?
Yes, and it's one of the places where portals lose the most visibility.
Tell us about your project
Knowing which version you run, who develops it and what worries you is enough for us to say whether it makes sense to talk.
Shall we talk about your platform?
We look at your project before proposing anything and tell you what can move without fighting the roadmap.
We look at your project before proposing anything. Reply within two working days at most.
Let's talk about your project