Developer Productivity

[tidyui]

We want to take some time and focus on features that will improve developer productivity during projects. We need input from all of you creating awesome solutions with Piranha with what would increase your productivity the most!

Features

• Add templated user types for handling different user groups
• Multiple block section (Multiple block sections #1598)
• Batch operations for Media in the manager (Move & delete multiple media files in the manager #1174) v8.3
• Abstract classes in list regions (Support abstract classes and interfaces in list regions #1113) (Not supported by current data model)
• Allow for IdentityUser class to be replaced (Customize Users #822)
• Add support for reusable blocks (Add functionality for Reusable Blocks #290) v8.4 (Implemented with generic content)
• Specify child types to a page (Define which PageType can have which child PageTypes with attributes #231)
• Add template options for faster project creation v8.3

Infrastructure

• Add SourceLink (Add SourceLink #1153) v8.3

Docs

• Improve overall documentation
• Add tutorial (custom data)

[nhaberl]

Fully fledged developer docs :)
In form of text but also maybe some webinars / videos.

[goranhell]

Your planned new IList with abstract or interface classes would be great for me

[tidyui]

@nhaberl As we think everything is self-explanatory and that the code is obvious you have to be more specific for things to improve 🤪 Please add issues at the piranha.core.docs repo and we’ll do our best to make it available!

[j2ba]

SourceLink for the Nuget packages. It would be nice to quickly start a project with the Nuget packages in a clean environment (VM for example) and still be able to debug, step into Piranha.Core when needed.

[mikaellindemann]

How about a guide/tutorial on how to make editors with custom data - e.g. having an Employee library (could be an archive with posts representing employee data such that it is itself editable from the manager) and selecting one such employee from a custom field in an unrelated page.

This might not be the intended way of accomplishing the case in Piranha, but then maybe there should be a page comparing Piranha against other CMS's content structure and how to rethink the problem to fit it to Piranha.

(Maybe this should have been created on the docs repo)

[tidyui]

Btw @j2ba As we release version 8.2 xml-comments will be included in the nuget-packages enabling inline docs when programming.

[121GWJolt]

Personally I think the one thing that would be cool is if we can add extra roles to the doc or add our own IdentityUser classes. That would greatly help with several things I'm doing and currently there aren't any particular things the default user class requires other than using GUIDs instead of strings (as best as I can tell at least). I think it'd be possible to do this.

If not, maybe do it in reverse. Add a way to add custom roles to the role list, and a way to inherit from Piranha's IdentityUser to reuse it in a separate context (I've done this myself in cases where necessary).

ISecurity is great but being able to make use of the user and role pages without having to fork the library could be really helpful.

[psandgren]

One feature that would improve QoL for both developers and editors would be to be able to limit child pagetypes. This would help to minimize user errors and help clean up code to handle the extra cases.
#231

[nhaberl]

@121GWJolt I totally agree, it would be great to handle backend and frontend users differntly.
Umbraco has a similar concept, where backend users are just named USERS and frontend users named MEMBERS.

Would love to see that in Piranha.
It would be also great if those would be different Identity contexts, so as a developer would benefit of managing frontendbusers by the full fetured asp.net identity stack rather than mixing it up with backend users.

[tidyui]

@nhaberl @121GWJolt We've discussed this in the past, and if we want different types of users, the optimal solution would be to leverage the templated content system already available and allow for the creation of different User Types that could be imported just like Page Types and Post Types. Then you could use Fields and Regions to specify whatever data or collection data you'd want for a type of user.

[tidyui]

@121GWJolt Roles can just be added through the manager interface, custom claims can be added easily in the application startup, see:

https://piranhacms.org/docs/architecture/authentication

[121GWJolt]

Hmmmm, I think the templating system for users could work like that! So long as the template could inherit from IdentityUser I think it'd satisfy most use cases.

OOOO I didn't realize the roles feature was added. I'll have to start using that, thank you!