nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to analyze a Project

robot

Hi,
We have received a requirement from the client.
Now my question is how do we decide that there will be this much DCTs, categories and datatypes.
Is there any analyzing tools or it is just your knowledge and experience which helps.
Please give your valuable feedback.

Find more posts tagged with

Comments

kummi

What requirements have you received in the first place ?

To decide the number of templates you have to analyze the web pages , their layouts most importantly how common / different they are from one another.

Rick Poulin

It's pretty much all experience.. Generally, you probably don't want a datatype so specific that it will only capture one page, and you don't want to make it so generic that the whole site fits into a single datatype (yes, there are exceptions). Usually, you want to weigh the tradeoff between form complexity/usability and having content littered in so many different types that it can't be found. You do so by combining similar page templates into a single one with options (radio buttons and such), and if your datatype starts to look like an audio receiver, then you've gone too far.

robot

It's pretty much all experience.. Generally, you probably don't want a datatype so specific that it will only capture one page, and you don't want to make it so generic that the whole site fits into a single datatype (yes, there are exceptions). Usually, you want to weigh the tradeoff between form complexity/usability and having content littered in so many different types that it can't be found. You do so by combining similar page templates into a single one with options (radio buttons and such), and if your datatype starts to look like an audio receiver, then you've gone too far.

Thanks rpoulin for elaborating and helping....

Binettoid

Rick is right, experience is vital here. Autonomy themselves will answer your questions with more questions. Some of it is more or less common sense, such as componentizing your page layouts into reusable modules, but other questions require expert insight. One of the biggest factors would be how you are to approach your TeamSite development (components or templates) and what your transformation engine and web server is to be, which may in turn depend on the functional requirements. PM me if you want to continue this conversation.