Portofino questions

[NewBee]

Just tried out Portofino 5.2.

I'm really pleased how fast Portofino is vs liferay.

The CRUD is really helpful.

Some questions:

I am trying to edit the welcome page. I'd expect when I click on the gear icon to be able to edit the content, just like when I create other pages. The welcome page seems "special" and un-editable. Am I missing something?

It seems like page types charts, calendars, forms, etc are missing in version 5 vs 4. Are those still being ported from version 4 to 5?

How do I edit the header/footer or do templates? The version 4 of Portofino seemed to have these features.

What is the proper way to style the page css and images? Is there are guidelines document on how to do this properly instead of just updating the source?

When I create a page and add a link, the link opens in a new window. I don't see how to add a link within the site that won't open a new window.

Setting the app name doesn't change the header, it still says "Portofino Application".

I tried RTFM, but it is for version 4, so apologies if I am asking basic question. 

Regards,

Adam

[Alessio Stalla]

Hi, and thanks for trying Portofino out! Let me answer your questions inline below:

On Mon, 1 Mar 2021 at 17:59, NewBee <ara...@assetmfg.com> wrote:

Just tried out Portofino 5.2.

I'm really pleased how fast Portofino is vs liferay.

The CRUD is really helpful.

Some questions:

I am trying to edit the welcome page. I'd expect when I click on the gear icon to be able to edit the content, just like when I create other pages. The welcome page seems "special" and un-editable. Am I missing something?

Indeed, the welcome page is a custom page that predates the re-introduction of text pages, and its HTML content is fixed. There's no good reason for it to be the way it is now that text pages are available – it just never occurred to us that we could change it. I've opened an issue – https://github.com/ManyDesigns/Portofino/issues/437 – you can expect it to be implemented and released soon since version 5.2.1 is coming out in the next few weeks.

 

It seems like page types charts, calendars, forms, etc are missing in version 5 vs 4. Are those still being ported from version 4 to 5?

We haven't ported them. In real-world applications, we saw that people rarely used them. I'd like to redo a more modern calendar page, but I don't know when I'll have the time.

 

How do I edit the header/footer or do templates? The version 4 of Portofino seemed to have these features.

Version 5 has the possibility as well, but it's a little more complicated because of Angular. I'll write a brief guide in the wiki pages on GitHub and ping you when it's done.

 

What is the proper way to style the page css and images? Is there are guidelines document on how to do this properly instead of just updating the source?

The Portofino 5 client is an Angular Material application so the only guidelines that apply are those of Angular Material: https://material.angular.io/guides

 

When I create a page and add a link, the link opens in a new window. I don't see how to add a link within the site that won't open a new window.

Are you talking about a text page? I don't recall doing anything special with links, maybe we should process them somehow.

 

Setting the app name doesn't change the header, it still says "Portofino Application".

Yes, that's a known issue. We never properly addressed it because we expect people to replace the toolbar anyway for branding. Still, I understand it's confusing and it can give the impression of a not-well-polished product, so I'll make sure to fix that for v5.2.1.

 

I tried RTFM, but it is for version 4, so apologies if I am asking basic question. 

Yes, documentation has been the well-known pain point for quite a while. I was planning to record some instructional videos but only managed to do three of them: https://github.com/ManyDesigns/Portofino/wiki/Video-Tutorials. Recently we've got some more feedback about documentation and videos so that gives some motivation to carve some extra time to continue working on them :)

 

Cheers,

Alessio

[NewBee]

Alessio,

Appreciate the response.

I couldn't delete the welcome page so I was kinda stuck.

When I searched for "Welcome to Portofino 5" on the local file system I found it in .js and .map files. It wasn't clear what I should edit. The main-es2015.6eecef5efd41d9c67228.js is 1.7MB which seems quite large to download. Does it need to be that large? It doesn't appear to be sent with gzip. If the size can't be reduced, considering caching a gzipped version to return with the proper browser headers. https://www.viralpatel.net/enable-gzip-compression-in-tomcat/ (Just make sure it is caching properly.)

Looking at the network tools, the request for config.json is getting pulled for all pages, including content just visiting the index page. Is it just caching?

I also saw multiple requests /api/:accessible that while fast seems to be for each page. Some of the requests resulted in 404 requests.

Using the developer tools to look at the site with a mobile browser the "sign in" button was often cut off and I had to scroll to the right. Otherwise, the site seemed to be responsive to mobile.

It would be nice to add bcrypt to the password algorithms, password salt, and being able to set password requirements.

Do you see this tool as a CMS or more of an RAD tool?

For CMS I don't see any versioning. (I found Portofino by looking for a CMS.)

Is the plan for skinning (CSS, images, header, footer) to eventually be editable via upstairs or through editing the file system?

Thank you,
Adam

[Alessio Stalla]

On Wed, 3 Mar 2021 at 18:54, NewBee <ara...@assetmfg.com> wrote:

Alessio,

Appreciate the response.

I couldn't delete the welcome page so I was kinda stuck.

When I searched for "Welcome to Portofino 5" on the local file system I found it in .js and .map files. It wasn't clear what I should edit. The main-es2015.6eecef5efd41d9c67228.js is 1.7MB which seems quite large to download. Does it need to be that large?

It could certainly be optimized, perhaps split into several smaller modules that can be loaded on demand. So far, this hasn't been an issue.

 

It doesn't appear to be sent with gzip. If the size can't be reduced, considering caching a gzipped version to return with the proper browser headers. https://www.viralpatel.net/enable-gzip-compression-in-tomcat/ (Just make sure it is caching properly.)

That's great advice, thanks!

 

Looking at the network tools, the request for config.json is getting pulled for all pages, including content just visiting the index page. Is it just caching?

config.json should be properly cached already.

I also saw multiple requests /api/:accessible that while fast seems to be for each page. Some of the requests resulted in 404 requests.

Yes, they're for each page. They could be optimized so that a page returns information also about all its children. However, this and other optimizations haven't been a priority, because we focused on features and stability.

 

Using the developer tools to look at the site with a mobile browser the "sign in" button was often cut off and I had to scroll to the right. Otherwise, the site seemed to be responsive to mobile.

OK, nice to hear that.

 

It would be nice to add bcrypt to the password algorithms, password salt, and being able to set password requirements.

All of that is possible by writing code in Security.groovy. The wizard for user management is really quite limited.

 

Do you see this tool as a CMS or more of an RAD tool?

For CMS I don't see any versioning. (I found Portofino by looking for a CMS.)

Definitely a RAD tool. Not much of a CMS (versioning, staging, editorial workflow, comments, ...). When Portofino 4 was young we were thinking of making it overlap with a lightweight CMS and wrote some articles about that, but it never really materialized. I do think there's still a mostly unexplored space for a CMS that is based on the file system and Git, and no database (except for indexing), resulting in a semi-static website. And it could certainly be based on Portofino. If I had a couple of other lives, or a lot of money, I would definitely invest in that :)

 

Is the plan for skinning (CSS, images, header, footer) to eventually be editable via upstairs or through editing the file system?

Definitely not upstairs. The preferred way is by creating a new application using the Maven archetype (this is what is used to build the downloadable version), then editing the frontend Angular application (which uses the Portofino library and is itself very small unless you implement complex custom components).

 

Regards,

Alessio

--
You received this message because you are subscribed to the Google Groups "manydesigns-portofino" group.
To unsubscribe from this group and stop receiving emails from it, send an email to manydesigns-port...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/manydesigns-portofino/7e1c192b-d3e0-4aa5-81b6-e2611eb35746n%40googlegroups.com.