You can't manage or track epics like you have described in a meaningful way. In addition, user stories that lack context and a clearly-defined value consumer aren't generally useful for project management, or even as conversational placeholders for business communication.
There will be a homepage with some information and the latest projects for the client.
This isn't even an epic. In addition to not following INVEST criteria, an epic this big doesn't even convey useful information about the themes and stories that might be packaged under it.
How could you turn this into one user story?
The short answer is:
- You can't.
- Even if you could, you shouldn't.
User stories should be much more granular than what you've described in your original post. When stories are small enough, and have clearly defined tasks associated with them, then it becomes possible to track the stories through your swimlanes or status columns.
But if this is only one card how can we track this on the board so we can tell if the designer currently designing it or if someone is developing it?
If the stories are decomposed into tasks, then the story can get passed from function to function in a clearly-definend way. However, this is not an agile approach. Rather than separating design from development, user stories should represent a vertical slice of value through both functions and the team members should work on them collectively and collaboratively.
Your kanban board will then reflect the state of each story, or its location in your process pipeline, rather than who is working on what. While those types of details can be attached to user stories, doing so is often a "project smell" that the team is still following a waterfall-based, upfront-design process.
There is a lot of information out on the web and in books about how to create meaningful user stories, and how to manage and track them. Answers here cannot provide a canonical list of resources that a practitioner should know, but you can certainly start with some classics like:
- User Stories Applied: For Agile Software Development by Mike Cohn.
- Agile Estimating and Planning by Mike Cohn.
- User Story Mapping: Discover the Whole Story, Build the Right Product by Jeff Patton.
- Kanban: Successful Evolutionary Change for Your Technology Business by David J. Anderson.
Please don't expect answers on a Q&A site to substitute for baseline knowledge of user stories. Truly understanding user stories, how to apply them, and how to manage them within your project management process is a complex topic.