Managing Projects

Projects are the proof section of your portfolio. They show what you have built, what technologies you have used, and how you think through real work.

Nukleio helps you keep project content structured so your portfolio can render project cards, galleries, featured work, or detailed project pages from the same source of truth.

Project Fields

A Nukleio project can include:

• project name
• start date
• end date
• GitHub URL
• demo URL
• programming languages
• frameworks
• technologies
• project description
• project thumbnail

Use as many fields as your portfolio needs. For example, a simple portfolio might only display the name, description, thumbnail, and links. A more detailed portfolio might also show date ranges and technology groups.

Adding a Project

To add a project:

1. Open the projects area  in your dashboard.
2. Choose the option to add a new project.
3. Enter the project name and date range.
4. Add a clear project description.
5. Add GitHub and demo links if available.
6. Select the languages, frameworks, and technologies used.
7. Upload a thumbnail image.
8. Save the project.
9. Check the connected portfolio to confirm the project renders correctly.

Writing Project Descriptions

A good project description should help a visitor understand the value of the project quickly.

Try to answer:

• What does the project do?
• Why did you build it?
• What problem does it solve?
• What technologies were used?
• What was technically interesting or challenging?

Example:

Nukleio is a portfolio content management platform that lets developers manage profile data, projects, files, and API keys from one dashboard. I built it with Next.js and Supabase so connected portfolio sites can fetch current data without hardcoded content updates.

Avoid descriptions that only list technologies. A visitor should understand the project even if they are not familiar with every tool in the stack.

Choosing Technologies

Nukleio separates project metadata into languages, frameworks, and technologies.

Use these categories consistently:

This structure helps portfolio frontends group or filter technical details in a predictable way.

Project Links

Add links when they are useful and safe to share.

Use the GitHub URL for source code and the demo URL for a live version of the project. If a project is private, incomplete, or not meant for public viewing, it is okay to leave one or both links blank.

Before saving links:

• confirm the URL opens correctly
• check that the demo site still works
• make sure private repositories are not linked as if they were public
• avoid linking to outdated demos that no longer represent the project

Project Thumbnails

A project thumbnail helps visitors recognize and compare projects quickly.

Good thumbnails are:

• clear at small sizes
• visually related to the project
• not overly text-heavy
• consistent in aspect ratio when possible
• current enough to match the live project

If your portfolio uses cards, thumbnails often have a major effect on how polished the page feels.

Updating Existing Projects

Update projects whenever your work changes.

Common updates include:

• improving the description
• adding a live demo link
• replacing a thumbnail
• correcting a date range
• adding a new technology
• changing a GitHub URL
• removing stale or unfinished work

After saving, refresh the connected portfolio and check that the layout still looks good with the new content length.

Project Checklist

Before publishing or sharing your portfolio, check that each project has:

• a clear name
• an accurate date range
• a visitor-friendly description
• working links where applicable
• relevant languages, frameworks, and technologies
• a thumbnail that looks good in your portfolio layout