Feature Request: Custom Sections (Flexible Resume Blocks)

[arun-kumar-24]

The current templates make resume building fast, but they are rigid. To make the system future-proof, we need to give users absolute flexibility so they can format and express their experiences in a far better way.

I propose introducing a Custom Template feature:

• Users will be able to add a blank section and define its structure.
• Formatting, layout, and contents will be fully customizable.
• The section will be stored in JSON (as the site already uses JSON for storing and fetching data).
• This ensures seamless integration with the current model.

How It Works:

• Frontend flexibility: Users create and format custom sections (titles, layout, items, bullet style, alignment, etc.).
• Backend integration: Store user-defined sections directly as JSON, same as existing templates.
• Rendering: Resume templates read from JSON and render the custom section alongside predefined ones.

Why This Matters:

• Keeps template-based speed while allowing true personalization.
• Makes resumes adaptable to diverse use cases (research CVs, design portfolios, non-standard formats).
• Ensures long-term scalability without hardcoding new categories.

this example helps in creating a two-way section to fill the resume efficiently for skills and certifications.

[NiranjanKumar001]

Thanks for the detailed proposal! I like the idea of giving users full flexibility.

I’d like to suggest a few enhancements based on the current implementation:

Users should be able to add new sections easily.

Sections should be renameable to reflect their content better.

Sections should also be deletable if no longer needed.

Allow nested sections so users can organize related items (like skills, certifications, or projects) efficiently.

With these changes, we can maintain the speed of template-based resume building while giving users full control and customization over their resumes. @arun-kumar-24 . also as this is pretty complex to handle with existing structure also make sure to work on it properly.

[arun-kumar-24]

Yeah, agreed. This will definitely help avoid scalability issues later. I’ll go ahead and start working on it.

[arun-kumar-24]

@NiranjanKumar001
I’m planning to introduce a new mode called FlexiBlox, where every part of the resume is treated as a “blok” (modular component).
Since many people are actively working on templates right now, I don’t want to disrupt the current flow. So instead of replacing templates directly, I’ll create this as a separate mode first.

This way, we can experiment with the full flexibility model in isolation, and later decide how much of it to merge into the default experience. Over time, we can gradually introduce flexibility into templates without breaking existing work.

[NiranjanKumar001]

@NiranjanKumar001
I’m planning to introduce a new mode called FlexiBlox, where every part of the resume is treated as a “blok” (modular component).
Since many people are actively working on templates right now, I don’t want to disrupt the current flow. So instead of replacing templates directly, I’ll create this as a separate mode first.

This way, we can experiment with the full flexibility model in isolation, and later decide how much of it to merge into the default experience. Over time, we can gradually introduce flexibility into templates without breaking existing work.

Ok, You can proceed.