Are there any particular difference between blueprint and wireframe?
I did some researches and found that blueprint is style wireframes!
User Experience Stack Exchange is a question and answer site for user experience researchers and experts. It only takes a minute to sign up.Sign up to join this community
UX terms are evolving, as I currently understand it
blueprint is a design guidelines or style guide that must apply to all UI's in a system. It will have actual proportions for padding, icons, layout specified. It would be a pattern for the accurate construction of all UI's in the system. Google Material Design 'red-line' specification
wireframe abstracts the functionality away from visual design concerns. It deliberately does not resemble final UI. It does not have proportions done accurately. May not even show all elements a blueprint would define as required. It is also done for a specific interaction in a system.
Worth also considering other terms in this context:
low fidelity mock-up uses colours and elements that look a little like the final UI, but the fit & finish is inaccurate. It does not apply the rules from the blueprint. It is done for a specific interaction in a system.
high fidelity mock-up exact image of what final UI will look like. Applies all of the blueprint rules to a specific UI (which may have been specified by a wireframe). It is done for a specific interaction in a system.
blueprint doesn't mean any specific in UX, AFAIK. It could refer to a particular visual style for a wireframe. It could actually refer to a wireframe itself.
It just occurred to me that perhaps you are thinking of blueprint.css It's a bit dated and isn't as popular as it once was but was used quite a bit a few years ago.