Enable adding new pages to the site #494
Labels
enhancement
New feature or request
Comments
|
Interesting idea, what kind of pages are you looking to add? |
|
@boyney123 Not sure what @huima is looking for, however from my perspective this feature will help to customize Catalog as per business need e.g. we can have subdomains and have linkage between domain, subdomain and events. |
|
+1 I had read the customize landing page part of the docs and assumed that adding entries to /pages would do exactly this. For my use case, I was adding a custom page for documenting conventions for creating events. I also think it lends itself to being a good place to centralize various documentation of the "meta" of the EDA. Ie, not the artifacts (domains,services,events) but design approaches/recommendations, naming conventions, roadmap goals, etc. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Have you read the Contributing Guidelines on issues?
Description
Eventhough you can add links to other sites by adding links to header or footer, it could make sense to enable the possibility to add new pages to the nextjs site by copying for example pages directory from project directory to the .eventcatalog directory in eventcatalog/bin/eventcatalog.js script.
Adding:
fs.copySync(path.join(projectDIR, 'pages'), path.join(eventCatalogLibDir, 'pages'));
To each of the commands could be enough?
Motivation
This would enable users to define new pages in the project directory - or even overwrite some functionality of Event Catalog pages if -- for some strange reason -- they would need to do something like that.
The text was updated successfully, but these errors were encountered: